Using SO_REUSEADDR – What happens to previously open socket?

by

A socket is considered closed when the program that was using it dies. That much is handled by the OS, and the OS will refuse to accept any further communication from the dead conversation. However, if the socket was closed unexpectedly, the computer on the other end might not know that the conversation is over, and may still be attempting to communicate.

That is why there is, designed into the TCP spec, a waiting period before that same port number can be reused. Because in theory, however unlikely, it may be possible for a packet from the old conversation to arrive with the appropriate IP address, port numbers, and sequence numbers such that the receiving server mistakenly inserts it into the wrong TCP stream by accident.

The SO_REUSEADDR option overrides that behavior, allowing you to reuse the port immediately. Effectively, you’re saying: “I understand the risks and would like to use the port anyway.”

More Related Contents:

  1. Differences between fork and exec
  2. How to get the current directory in a C program?
  3. How to capture Control+D signal?
  4. In C how do you redirect stdin/stdout/stderr to files when making an execvp() or similar call?
  5. Color text in terminal applications in UNIX [duplicate]
  6. What does the brk() system call do?
  7. Re-opening stdout and stdin file descriptors after closing them
  8. Turn a simple socket into an SSL socket
  9. Getting absolute path of a file
  10. What are .a and .so files?
  11. Are there any platforms where using structure copy on an fd_set (for select() or pselect()) causes problems?
  12. How can I convert a file pointer ( FILE* fp ) to a file descriptor (int fd)?
  13. After forking, are global variables shared?
  14. How to find the socket connection state in C?
  15. how to convert datetime to unix timestamp in c?
  16. Detecting 64bit compile in C
  17. Is it necessary to reset the fd_set between select system call?
  18. Socketpair() in C/Unix
  19. Understanding concurrent file writes from multiple processes
  20. fd leak, custom Shell
  21. Writing to stdin and reading from stdout (UNIX/LINUX/C Programming)
  22. *nix select and exceptfds/errorfds semantics
  23. Questions about putenv() and setenv()
  24. What do pty and tty mean?
  25. What can cause a “Resource temporarily unavailable” on sock send() command
  26. Executing a shared library on Unix
  27. How can I flush unread data from a tty input queue on a UNIX system?
  28. Unix O_CREAT flag without mode specified
  29. ungetc: number of bytes of pushback
  30. What’s the difference between “C system calls” and “C library routines”?

Leave a Comment