netdev - Re: [Bridge] bridging with gre tunnel

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, 14 Jul 2008 14:15:14 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Herbert Xu <herbert@...dor.apana.org.au>
CC:	Philip Craig <philipc@...pgear.com>, netdev@...r.kernel.org,
	bridge@...ts.linux-foundation.org, timo.teras@....fi
Subject: Re: [Bridge] bridging with gre tunnel

Herbert Xu wrote:
> Philip Craig <philipc@...pgear.com> wrote:
>> Actually, this change doesn't really belong in GRE either, because
>> that forces you to choose between ethernet encapsulation and not.
>> It could be a new device that sits on top of GRE and simply does
>> ethernet encapsulation then passes it to the raw GRE device.
>> That's a lot of infrastructure for something so simple though,
>> and I don't think people will want to use both devices at once.
> 
> What's the problem with using Ethernet encapsulation on such a
> GRE device? If you're referring to the fact that user-space uses
> the encapsulation type to determine whether a device is a tunnel,
> then we should fix those tools instead.
> 
> Rather than trying to resuscitate the ioctl interface, please
> create a new extensible netlink interface and make ip(8) use it
> where available.


Or use rtnl_link, which was created for this purpose :)
--
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