netdev
[Top] [All Lists]

Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling

To: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
Subject: Re: [PATCH][RFC] etherip: Ethernet-in-IPv4 tunneling
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Wed, 12 Jan 2005 15:43:52 -0800
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20050112231615.GF14280@xxxxxxxxxxxxxxxxx>
Organization: Candela Technologies
References: <20050112222437.GC14280@xxxxxxxxxxxxxxxxx> <41E5A7E9.4030101@xxxxxxxxxxxxxxx> <20050112224810.GE14280@xxxxxxxxxxxxxxxxx> <41E5AEAC.8060706@xxxxxxxxxxxxxxx> <20050112231615.GF14280@xxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020
Lennert Buytenhek wrote:
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.

How about add one IOCTL that takes a small (naturally packed/aligned, 
fixed-size!)
struct that has within it an enumeration of specific commands and whatever 
fields
are needed for arguments.  Then you only need to add a single IOCTL to the 
system,
and you can add more commands at will.

Ben

--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc  http://www.candelatech.com


<Prev in Thread] Current Thread [Next in Thread>