netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Philip Craig <philipc@snapgear.com>
Cc: Stephen Hemminger <shemminger@osdl.org>, netdev@vger.kernel.org
Subject: Re: [RFC] gre: transparent ethernet bridging
Date: Thu, 3 Aug 2006 09:33:07 +0200	[thread overview]
Message-ID: <20060803073307.GA29775@xi.wantstofly.org> (raw)
In-Reply-To: <44D15265.4090905@snapgear.com>

On Thu, Aug 03, 2006 at 11:33:25AM +1000, Philip Craig wrote:

> >>> All it does is encapsulate the full ethernet header in a gre packet,
> >>> rather than only layer 3.  That is, currently gre uses ARPHRD_IPGRE,
> >>> but bridging requires ARPHRD_ETHER.
> >>
> >> I am not against making the bridge code smarter to handle other
> >> encapsulation.
> > 
> > What if you want to run ethernet directly over a GRE tunnel, without
> > using bridging?
> 
> But on the other hand, this method allows you to send both ethernet
> and non-ethernet traffic over the same GRE tunnel.  Is that useful?
> Actually, this feature is what makes the handling of the LLC_SAP_BSPAN
> packets simple.
> 
> The patch to bridging is a lot cleaner than the patch to GRE, and it
> also sidesteps the userspace configuration issues, so I don't want to
> go back to modifying the GRE device.

So now you _need_ bridging in the middle to send ethernet traffic over
a GRE tunnel?  Ugh.

If you really want to send ethernet and non-ethernet traffic over the
same tunnel, can't you make multiple devices?

If GRE generally transmits BPDUs without ethernet header, the handling
for that ought to be in GRE, IMHO.


cheers,
Lennert

  reply	other threads:[~2006-08-03  7:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 10:06 [RFC] gre: transparent ethernet bridging Philip Craig
2006-07-31 16:14 ` Stephen Hemminger
2006-08-01  1:15   ` Philip Craig
2006-08-01  5:08     ` Stephen Hemminger
2006-08-01  9:29       ` Philip Craig
2006-08-02  6:17         ` Philip Craig
2006-08-02 17:23           ` Stephen Hemminger
2006-08-03  1:08             ` Philip Craig
2006-08-02  7:42       ` Lennert Buytenhek
2006-08-03  1:33         ` Philip Craig
2006-08-03  7:33           ` Lennert Buytenhek [this message]
2006-08-03  9:14             ` Philip Craig
2006-08-03 19:40               ` Lennert Buytenhek
2006-08-04  1:00                 ` Philip Craig
2006-08-04  8:02                   ` Lennert Buytenhek
2006-08-07  1:55                     ` Philip Craig
2006-08-10 13:09                       ` Lennert Buytenhek

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=20060803073307.GA29775@xi.wantstofly.org \
    --to=buytenh@wantstofly.org \
    --cc=netdev@vger.kernel.org \
    --cc=philipc@snapgear.com \
    --cc=shemminger@osdl.org \
    /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).