netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Ben Greear <greearb@candelatech.com>,
	netdev@oss.sgi.com, shemminger@osdl.org,
	shollenbeck@verisign.com
Subject: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling
Date: Thu, 13 Jan 2005 00:43:44 +0100	[thread overview]
Message-ID: <20050112234344.GM26856@postel.suug.ch> (raw)
In-Reply-To: <20050112231615.GF14280@xi.wantstofly.org>

* Lennert Buytenhek <20050112231615.GF14280@xi.wantstofly.org> 2005-01-13 00:16
> On Wed, Jan 12, 2005 at 03:11:40PM -0800, Ben Greear wrote:
> 
> > >>Also, could you add an ioctl that allowed one to query whether or not
> > >>a particular device is an etherip device?  I had always wished I had added
> > >>this earlier to the VLAN code :)
> > >
> > >Hmmm.  Bridge devices don't have this either, do they?  Can you name
> > >an advantage of having this?
> > 
> > I got the request several times with regard to VLANs.  Lots of people
> > (and applications) will want to know the interface type for various
> > reasons.  If you don't give them a nice programatic thing like an
> > IOCTL to call, they will undoubtedly start making assumptions based
> > off of the device name...
> 
> Makes sense..
> 
> Unfortunately SIOCGETTUNNEL is (SIOCDEVPRIVATE + 3), otherwise we could
> just say something like "If an ARPHRD_ETHER device supports SIOCGETTUNNEL,
> it's an ether/ip tunnel."
> 
> Any better ideas?  I hate adding more ioctls.

I think it should go into ip_tunnel_param, unforunately there are no
unused fields. Maybe schedule this for 2.7 together with a clean up
of all the tunnels so they share redundant code? Lots of gre related
code and comments spread over non-gre tunnels that should go away.

  reply	other threads:[~2005-01-12 23:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 22:24 [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-12 22:42 ` Ben Greear
2005-01-12 22:48   ` Lennert Buytenhek
2005-01-12 23:11     ` Ben Greear
2005-01-12 23:16       ` Lennert Buytenhek
2005-01-12 23:43         ` Thomas Graf [this message]
2005-01-13  0:18           ` Lennert Buytenhek
2005-01-13  0:28             ` Thomas Graf
2005-01-13  0:36               ` Lennert Buytenhek
2005-01-13  1:20                 ` Thomas Graf
2005-01-12 23:43         ` Ben Greear
2005-01-13  0:04 ` Stephen Hemminger
2005-01-13  0:29   ` Lennert Buytenhek
2005-01-13  7:49 ` Pekka Savola
2005-01-13  9:23   ` Lennert Buytenhek
2005-01-16 17:37     ` jamal
2005-01-16 18:55       ` tunneling in linux (was: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling) Lennert Buytenhek
2005-01-16 19:51         ` Pekka Savola
2005-01-16 19:57           ` Lennert Buytenhek
2005-01-17  5:45             ` Pekka Savola
2005-01-16 20:02         ` jamal
2005-01-16 20:20           ` Lennert Buytenhek
2005-01-16 20:37             ` Hasso Tepper
2005-01-16 21:21               ` Lennert Buytenhek
2005-01-16 21:32                 ` Hasso Tepper
2005-01-16 21:44                   ` Lennert Buytenhek
2005-01-16 23:09             ` jamal
2005-01-16 19:02       ` [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling Lennert Buytenhek
2005-01-16 20:05         ` jamal
2005-01-16 20:22           ` 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=20050112234344.GM26856@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=buytenh@wantstofly.org \
    --cc=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=shemminger@osdl.org \
    --cc=shollenbeck@verisign.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).