netdev - Re: [RFT] vxlan: listen on multiple ports

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 May 2013 23:20:58 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Cong Wang <amwang@...hat.com>
Cc:	David Stevens <dlstevens@...ibm.com>, netdev@...r.kernel.org,
	netdev-owner@...r.kernel.org
Subject: Re: [RFT] vxlan: listen on multiple ports

On Thu, 16 May 2013 10:51:13 +0800
Cong Wang <amwang@...hat.com> wrote:

> On Wed, 2013-05-15 at 14:37 -0700, Stephen Hemminger wrote:
> > The earlier change to introduce per-vxlan UDP port configuration did only
> > half the necessary work. It added per vxlan destination for sending, but
> > overlooked the handling of multiple ports for incoming, which means it
> > is broken.
> > 
> > This patch changes the listening port management to handle multiple
> > incoming UDP ports. The earlier per-namespace structure is now a hash
> > list per namespace.
> > 
> > It is also now possible to define the same virtual network id
> > but with different UDP port values.
> > 
> 
> Besides fixing the default port issue, what other benefits does it have?
> This seems overkill.
> 
> It looks like you make one socket per port, after my IPv6 patches, we
> would have two sockets per port...
> 
> 

The destination port option is broken now. It only sets the port
for outgoing packets, it does not change port used for incoming packets.
This change is to address that. Sorry, it shouldn't be a big
impact for IPv6.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html