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 02:20:07 +0100 [thread overview]
Message-ID: <20050113012007.GO26856@postel.suug.ch> (raw)
In-Reply-To: <20050113003625.GJ14280@xi.wantstofly.org>
* Lennert Buytenhek <20050113003625.GJ14280@xi.wantstofly.org> 2005-01-13 01:36
> On Thu, Jan 13, 2005 at 01:28:06AM +0100, Thomas Graf wrote:
>
> > > What's that? I can't find it in my kernel tree nor on google.
> >
> > Typo, sorry. I meant ip_tunnel_parm. Thinking of it, shouldn't protocol
> > in ip_tunnel_parm->iph->protocol be set to ETHER_IP so userspace could
> > find out this way?
>
> ip_tunnel_parm->iph->protocol for ether/ip tunnels is IPPROTO_ETHERIP,
> which is 97. So yeah, the info is in there. But this doesn't help you
> much in determining whether an arbitrary network device is in fact an
> ether/ip tunnel or not, since SIOCGETTUNNEL aliases with SIOCDEVPRIVATE+3.
Ahh.. You want userspace to be able to tell even if it is unclear
wether it is a tunnel. I think the only way to avoid a new ioctl would
be to introduce IFF_TUNNEL or alike and have userspace call GETTUNNEL
if it is set. This also solves the problem for all other tunnels.
You can also reuse one of the unused flags such as IFF_NOTRAILERS
since it would be read only anyway but I guess this would be too
much of a hack ;->
next prev parent reply other threads:[~2005-01-13 1:20 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
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 [this message]
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=20050113012007.GO26856@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).