[Top] [All Lists]

Re: RFC: Redirect-Device

To: bert hubert <ahu@xxxxxxx>
Subject: Re: RFC: Redirect-Device
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Fri, 01 Apr 2005 08:58:52 -0800
Cc: hadi@xxxxxxxxxx, "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev <netdev@xxxxxxxxxxx>
In-reply-to: <20050401090116.GA21361@xxxxxxxxxxxxxxx>
Organization: Candela Technologies
References: <424C6089.1080507@xxxxxxxxxxxxxxx> <1112303627.1073.71.camel@xxxxxxxxxxxxxxxx> <424C6B10.6030200@xxxxxxxxxxxxxxx> <1112306031.1073.109.camel@xxxxxxxxxxxxxxxx> <424C7813.4000101@xxxxxxxxxxxxxxx> <20050331143531.30f4eb8f.davem@xxxxxxxxxxxxx> <424C7F96.4070002@xxxxxxxxxxxxxxx> <1112311618.1090.20.camel@xxxxxxxxxxxxxxxx> <424C8E2C.70302@xxxxxxxxxxxxxxx> <20050401090116.GA21361@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020
bert hubert wrote:
On Thu, Mar 31, 2005 at 03:56:28PM -0800, Ben Greear wrote:

I think you are more comfortable with using netdevices and ioctls and

Definately.  Ever tried to sniff a socket with ethereal? :)

On loopback, all the time. I'm probably dense but I don't understand what
problem you've solved with this interface. Could you elaborate a bit?

It allows me to place a software bridge that can intercept all packets
from user-space via raw packet sockets, and kernel space via registering
an 'all' protocol on the device.  Please note that to bridge in this manner
I have to remove the IP protocol (set IP to, otherwise the IP stack
can interfere with the bridging behaviour.

By using a virtual pair of interfaces that are looped back, I can add an
IP to the second virtual network interface that does not interfere with
the two bridged interfaces (one physical, one redirect, both with IP

If there were an API to register handlers dynamically that act like the
netpoll hook (ie, with ability to consume frames), then I would not have to
remove the IP from the physical interface and I probably would not have had
to create these redirect devices.  But, when I was suggesting such a hook
in the past, it was shot down because it could allow someone to write their
own TCP stack, and the network guys did not want to allow this possibility.


Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc

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