netdev - Re: 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]

Message-ID: <487AFF82.4090707@iki.fi>
Date:	Mon, 14 Jul 2008 10:25:54 +0300
From:	Timo Teräs <timo.teras@....fi>
To:	Philip Craig <philipc@...pgear.com>
CC:	bridge@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: bridging with gre tunnel

Philip Craig wrote:
> Timo Teräs wrote:
>> Is there newer/better patches to achieve this? Any thoughts about
>> doing bridging with gre tunnels?
> 
> Here's a patch I did against 2.6.17.
> 
> I didn't submit this to mainline though because the userspace ABI
> is ugly.  The basic problem is that the struct used for the ioctl
> isn't extensible.  The only way I can think of to fix it properly
> is to add configuration of gre using netlink, but I never got around
> to doing that.  

There is an essential difference in this patch compared to the one
I referred to. This patch adds a new way to create GRE devices which
results in ethernet style device whereas the older patch modifies
transmit and receive paths to detect packets coming from bridging
code and does not need userland changes at all.

I kind of like the fact that userland tools work as-is and that
I don't need any special flags for the GRE tunnel creation. However
your patch does look way cleaner.

Any comments on what the solution to merged in should look like?

- Timo

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