netdev - Re: UDP packets arriving on wrong sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180803152014.GA5188@canndrew.org>
Date:   Fri, 3 Aug 2018 11:20:14 -0400
From:   Andrew Cann <shum@...ndrew.org>
To:     netdev@...r.kernel.org
Subject: Re: UDP packets arriving on wrong sockets

On Fri, Aug 03, 2018 at 10:20:06AM -0400, Willem de Bruijn wrote:
> On Fri, Aug 3, 2018 at 12:20 AM Andrew Cann <shum@...ndrew.org> wrote:
> >
> > On Thu, Aug 02, 2018 at 11:21:41AM -0400, Willem de Bruijn wrote:
> > > You have two sockets bound to the same address and port? Is this using
> > > SO_REUSEPORT?
> >
> > Yes, this is using SO_REUSEPORT.
> 
> Then this is working as intended.
> 
> Without SO_REUSEPORT it would not be possible to bind two sockets to
> the same address and port. See documentation, e.g., at
> https://lwn.net/Articles/542629/

The man page for connect clearly states that a connected UDP socket should only
receive datagrams from the address that it is connected to. This isn't the
behaviour I'm seeing. That's the issue.


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)