Re: SO_REUSEPORT on unicast UDP sockets

2001-09-08 Thread Vladimir A. Jakovenko
On Fri, Sep 07, 2001 at 12:00:50PM -0700, Terry Lambert wrote: >"Vladimir A. Jakovenko" wrote: >> Terry, I clearly understand all your explanations. Yes, we are living in >> real life and there is a lot of programms with bad design. >> >> But all what I want is possibility to receive UDP packets

Re: SO_REUSEPORT on unicast UDP sockets

2001-09-07 Thread Terry Lambert
"Vladimir A. Jakovenko" wrote: > Terry, I clearly understand all your explanations. Yes, we are living in > real life and there is a lot of programms with bad design. > > But all what I want is possibility to receive UDP packets with > corresponding dst IP and port by more than one process on a s

Re: SO_REUSEPORT on unicast UDP sockets

2001-09-07 Thread Vladimir A. Jakovenko
On Mon, Sep 03, 2001 at 11:48:02PM -0700, Terry Lambert wrote: >"Vladimir A. Jakovenko" wrote: >> >> Hello! >> >> According to UNPv1 SO_REUSEPORT on UDP sockets can be used to bind more than >> one socket to the same port (even with same source ip address). But quick >> look on /sys/netinet/u

Re: SO_REUSEPORT on unicast UDP sockets

2001-09-05 Thread Terry Lambert
Mike Silbersack wrote: > > Similarly, there are a number of bugs in the TCP sockets as > > well; specifically, there's a problem with all sockets being > > treated as being in the same collision domain, when doing > > automatic port assignment. This limits you to 65535 oubound > > TCP connections

Re: SO_REUSEPORT on unicast UDP sockets

2001-09-04 Thread Mike Silbersack
On Mon, 3 Sep 2001, Terry Lambert wrote: > Similarly, there are a number of bugs in the TCP sockets as > well; specifically, there's a problem with all sockets being > treated as being in the same collision domain, when doing > automatic port assignment. This limits you to 65535 oubound > TCP c

Re: SO_REUSEPORT on unicast UDP sockets

2001-09-03 Thread Terry Lambert
"Vladimir A. Jakovenko" wrote: > > Hello! > > According to UNPv1 SO_REUSEPORT on UDP sockets can be used to bind more than > one socket to the same port (even with same source ip address). But quick > look on /sys/netinet/udp_usrreq.c function udp_input() shows that this will > work as expec

SO_REUSEPORT on unicast UDP sockets

2001-09-01 Thread Vladimir A. Jakovenko
Hello! According to UNPv1 SO_REUSEPORT on UDP sockets can be used to bind more than one socket to the same port (even with same source ip address). But quick look on /sys/netinet/udp_usrreq.c function udp_input() shows that this will work as expected (data stream duplicate) only on multicast/