From: Stephen Hemminger <shemminger@osdl.org>
To: Philip Craig <philipc@snapgear.com>
Cc: Joerg Roedel <joro-lkml@zlug.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] EtherIP tunnel driver (RFC 3378)
Date: Thu, 14 Sep 2006 10:33:32 +0900 [thread overview]
Message-ID: <20060914103332.641e7ff0@localhost.localdomain> (raw)
In-Reply-To: <4508AE92.1090202@snapgear.com>
On Thu, 14 Sep 2006 11:21:22 +1000
Philip Craig <philipc@snapgear.com> wrote:
> Joerg Roedel wrote:
> > + To configure tunnels an extra tool is required. You can download
> > + it from http://zlug.fh-zwickau.de/~joro/projects/ under the
> > + EtherIP section. If unsure, say N.
>
> To obtain a list of tunnels, this tool calls SIOCGETTUNNEL
> (SIOCDEVPRIVATE + 0) for every device in /proc/net/dev. I don't think
> this is safe, but I don't have a solution for you.
>
> Is there a reason why you have a separate tool rather than modifying
> iproute2?
>
> I don't know if you are aware of this older etherip patch by Lennert
> Buytenhek: http://www.wantstofly.org/~buytenh/etherip/
SIOCDEVPRIVATE usage makes it hard to do 32 bit compatibility layer.
next prev parent reply other threads:[~2006-09-14 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 20:41 [PATCH] EtherIP tunnel driver (RFC 3378) Joerg Roedel
2006-09-13 16:27 ` Patrick McHardy
2006-09-14 1:21 ` Philip Craig
2006-09-14 1:33 ` Stephen Hemminger [this message]
2006-09-14 9:52 ` Joerg Roedel
2006-09-14 10:11 ` Patrick McHardy
2006-09-14 23:06 ` Philip Craig
2006-09-15 8:17 ` Joerg Roedel
2006-09-18 20:52 ` Lennert Buytenhek
2006-09-19 7:08 ` Joerg Roedel
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=20060914103332.641e7ff0@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=joro-lkml@zlug.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=philipc@snapgear.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).