From: "Timo Teräs" <timo.teras@iki.fi>
To: Philip Craig <philipc@snapgear.com>
Cc: bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: bridging with gre tunnel
Date: Mon, 14 Jul 2008 10:25:54 +0300 [thread overview]
Message-ID: <487AFF82.4090707@iki.fi> (raw)
In-Reply-To: <487AA0CD.9090600@snapgear.com>
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
next prev parent reply other threads:[~2008-07-14 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 6:30 bridging with gre tunnel Timo Teräs
2008-07-11 19:07 ` [Bridge] " Stephen Hemminger
2008-07-14 0:41 ` Philip Craig
2008-07-14 7:25 ` Timo Teräs [this message]
2008-07-14 8:44 ` Philip Craig
2008-07-14 9:13 ` James Chapman
2008-07-14 9:44 ` Timo Teräs
2008-07-14 11:45 ` Herbert Xu
2008-07-14 12:15 ` [Bridge] " Patrick McHardy
2008-07-14 12:20 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=487AFF82.4090707@iki.fi \
--to=timo.teras@iki.fi \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=philipc@snapgear.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).