netdev - Re: [RFC PATCH net] vxlan: fix incorrect RCO bit in VXLAN header

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:	Mon, 7 Dec 2015 11:48:30 +0100
From:	Jiri Benc <jbenc@...hat.com>
To:	Tom Herbert <tom@...bertland.com>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	Thomas Graf <tgraf@...g.ch>
Subject: Re: [RFC PATCH net] vxlan: fix incorrect RCO bit in VXLAN header

<On Fri, 4 Dec 2015 09:13:28 -0800, Tom Herbert wrote:
> That's awesome! One favor, can you make sure VXLAN-GPE works with IPv6
> from the start. :-)

Absolutely. I've not spent so much effort adding IPv6 counterparts to
various vxlan stuff to submit vxlan-gpe for IPv4 only :-)

> Also, I'll need to spin an I-D for RCO in VXLAN-GPE. Do you see any
> reason to use a different bit for it?

As for the flags, VXLAN-GBP, VXLAN-GPE and VXLAN-RCO are compatible
with each other. It's not possible to use GBP and GPE together because
the group policy id and the next protocol field are overlapping but
it's possible to distinguish whether it's GBP or GPE based on the
flags.

There should be no problem using GPE and RCO together (at least now,
when this patch is applied). It needs to be explicitly configured as
such when creating the interface, though.

 Jiri

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