netdev
[Top] [All Lists]

Re: tun device - bug or feature? WAS(Re: IMQ / new Dummy device post.

To: Max Krasnyansky <maxk@xxxxxxxxxxxx>
Subject: Re: tun device - bug or feature? WAS(Re: IMQ / new Dummy device post.
From: jamal <hadi@xxxxxxxxxx>
Date: 26 Apr 2004 22:22:26 -0400
Cc: netdev@xxxxxxxxxxx, syrius.ml@xxxxxxxxxx, Jeff Garzik <jgarzik@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>
In-reply-to: <1083007898.7788.276.camel@localhost>
Organization: jamalopolis
References: <wazza.87ad18jbdl.fsf@message.id> <1082427350.1034.70.camel@jzny.localdomain> <wazza.87fzayw1fy.fsf@message.id> <wazza.87fzaxmr6x.fsf@message.id> <wazza.87hdvddqxq.fsf@message.id> <1082639764.1059.81.camel@jzny.localdomain> <87oepjx65r.87n053x65r@87llknx65r.message.id> <1082719745.1057.27.camel@jzny.localdomain> <1082816083.1054.32.camel@jzny.localdomain> <1083007898.7788.276.camel@localhost>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 2004-04-26 at 15:31, Max Krasnyansky wrote:

> Well TUN does not have any hw headers so there is nothing to pull :).

didnt notice the dev->hard_header_len being 0 before ;->
In that case it makes sense to have nothing to pull.
Theres about 5 devices like that.
I need to rethink a little on behavior of mirred with devices that have
no hardware headers. I may speacial case them.

cheers,
jamal


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