From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Philip Craig <philipc@snapgear.com>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
timo.teras@iki.fi
Subject: Re: [Bridge] bridging with gre tunnel
Date: Mon, 14 Jul 2008 14:15:14 +0200 [thread overview]
Message-ID: <487B4352.6040408@trash.net> (raw)
In-Reply-To: <E1KIMV2-0007Na-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Philip Craig <philipc@snapgear.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 :)
next prev parent reply other threads:[~2008-07-14 12:16 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
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 ` Patrick McHardy [this message]
2008-07-14 12:20 ` [Bridge] " 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=487B4352.6040408@trash.net \
--to=kaber@trash.net \
--cc=bridge@lists.linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--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 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).