From: barmar@alum.mit.edu   
      
   In article <1355024@news1.IPSWITCHS.CMM>,   
    ddl@danlan.*com (Dan Lanciani) wrote:   
      
   > In article ,   
   > barmar@alum.mit.edu (Barry Margolin) writes:   
   >   
   > | I'm not sure how this scenario is possible.  Putty should get an   
   > | EADDRINUSE error when it tries to bind the socket.  SO_REUSEADDR   
   > | shouldn't override this case (it allows you to bind a socket while there   
   > | are established sockets using the port, but it shouldn't allow you to   
   > | bind a socket while there's a listening socket).   
   >   
   > SO_REUSEPORT, however, will allow totally duplicate bindings on   
   > "modern" systems.  One of the early rounds of multicast enhancements   
   > for the BSD stack changed the semantics of tcb matching (and thus of   
   > SO_REUSEADDR) to allow for totally duplicate bindings.  This broke   
   > things.  IIRC, SO_REUSEPORT showed up as the alternative with slightly   
   > different semantics from the "modern" version.  There was so much   
   > confusion that some applications may just use both in hopes of getting   
   > the least restrictive behavior.   
      
   I was under the impression that SO_REUSEPORT was only applicable to UDP,   
   and maybe just multicast.  There's no such thing as multicast TCP,   
   AFAIK, so which should TCB matching have to consider this case?   
      
   --   
   Barry Margolin, barmar@alum.mit.edu   
   Arlington, MA   
   *** PLEASE don't copy me on replies, I'll read them in the group ***   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)