netdev - RE: RFC - VXLAN port range facility

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:	Mon, 3 Jun 2013 09:21:31 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Stephen Hemminger" <stephen@...workplumber.org>,
	"David Stevens" <dlstevens@...ibm.com>
Cc:	<netdev@...r.kernel.org>, <netdev-owner@...r.kernel.org>
Subject: RE: RFC - VXLAN port range facility

> I am wondering if this is just a theoretical problem, or does it occur
> in real life. My simple tests are not causing ICMP to be delivered to
> UDP application (over the VXLAN) but it maybe because of the compare scoring
> in ICMP, or because of use of multicast versus unicast destinations.

Perhaps modify the routing of received ICMP error messages
so that ones referring to the VXLAN destination port get
routed to VXLAN rather than the socket bound to the source
port (this could be made generic).

Some one seems to have invented a protocol that abuses the
normal port number rules.

	David



--
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