From: James Chapman <jchapman@katalix.com>
To: Philip Craig <philipc@snapgear.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"Timo Teräs" <timo.teras@iki.fi>
Subject: Re: [Bridge] bridging with gre tunnel
Date: Mon, 14 Jul 2008 10:13:49 +0100 [thread overview]
Message-ID: <487B18CD.5020502@katalix.com> (raw)
In-Reply-To: <487B11D9.7090800@snapgear.com>
Philip Craig wrote:
> Timo Teräs wrote:
> I posted a cleaner version that's similar to what the old patch
> did, see http://marc.info/?l=linux-netdev&m=115449948503549&w=2
>
> But I don't think that is the right approach:
> - it forces you to use bridging if you only want ethernet over GRE
> - the change fundamentally has nothing to do with bridging
I agree.
> 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.
This would be my preferred approach. There are other drivers that use a
netdev to do some encap/decap processing on packets which are then
passed on to another driver, e.g. macvlan, and it works well.
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
WARNING: multiple messages have this Message-ID (diff)
From: James Chapman <jchapman@katalix.com>
To: Philip Craig <philipc@snapgear.com>
Cc: "Timo Teräs" <timo.teras@iki.fi>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: bridging with gre tunnel
Date: Mon, 14 Jul 2008 10:13:49 +0100 [thread overview]
Message-ID: <487B18CD.5020502@katalix.com> (raw)
In-Reply-To: <487B11D9.7090800@snapgear.com>
Philip Craig wrote:
> Timo Teräs wrote:
> I posted a cleaner version that's similar to what the old patch
> did, see http://marc.info/?l=linux-netdev&m=115449948503549&w=2
>
> But I don't think that is the right approach:
> - it forces you to use bridging if you only want ethernet over GRE
> - the change fundamentally has nothing to do with bridging
I agree.
> 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.
This would be my preferred approach. There are other drivers that use a
netdev to do some encap/decap processing on packets which are then
passed on to another driver, e.g. macvlan, and it works well.
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
next prev parent reply other threads:[~2008-07-14 9:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 6:30 [Bridge] bridging with gre tunnel Timo Teräs
2008-07-11 6:30 ` Timo Teräs
2008-07-11 19:07 ` [Bridge] " Stephen Hemminger
2008-07-11 19:07 ` Stephen Hemminger
2008-07-14 0:41 ` Philip Craig
2008-07-14 0:41 ` Philip Craig
2008-07-14 7:25 ` [Bridge] " Timo Teräs
2008-07-14 7:25 ` Timo Teräs
2008-07-14 8:44 ` [Bridge] " Philip Craig
2008-07-14 8:44 ` Philip Craig
2008-07-14 9:13 ` James Chapman [this message]
2008-07-14 9:13 ` James Chapman
2008-07-14 9:44 ` [Bridge] " Timo Teräs
2008-07-14 9:44 ` Timo Teräs
2008-07-14 11:45 ` [Bridge] " Herbert Xu
2008-07-14 11:45 ` Herbert Xu
2008-07-14 12:15 ` [Bridge] " Patrick McHardy
2008-07-14 12:15 ` Patrick McHardy
2008-07-14 12:20 ` Herbert Xu
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=487B18CD.5020502@katalix.com \
--to=jchapman@katalix.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=philipc@snapgear.com \
--cc=timo.teras@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.