netdev - Re: [PATCH net] 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] [day] [month] [year] [list]

Date:	Fri, 17 May 2013 21:05:17 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	David Stevens <dlstevens@...ibm.com>
Cc:	David Miller <davem@...emloft.net>, netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net] vxlan: listen on multiple ports

On Fri, 17 May 2013 23:59:03 -0400
David Stevens <dlstevens@...ibm.com> wrote:

> Stephen Hemminger <stephen@...workplumber.org> wrote on 05/17/2013 
> 11:05:16 PM:
> 
> > then the original commit to add NDA_PORT should be reverted from 3.10
> > no point in continuing the half baked idea
> 
> I don't think these are linked at all. While being able to specify
> multiple listen ports, I agree, is a good idea, being able to specify
> alternate remote ports is needed because you can already change the
> one per-host port.
> 
> With only one listen port per host, if they are different on two hosts,
> NDA_PORT in the fdb table is the only way those two hosts can use VXLAN
> with each other at all.
> 
> It has nothing to do with how many listen ports there are, but just that
> the listen port can be different on different hosts.
> 
>                                                                 +-DLS
> 

It does mean that you are creating an asymmetric routing setup.
The other end of the tunnel still has to send back to default vxlan port.
There is no mechanism to add additional ports.
--
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