netdev - Re: [LARTC] ifb and ppp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1190294388.4734.6.camel@localhost>
Date:	Thu, 20 Sep 2007 09:19:48 -0400
From:	jamal <hadi@...erus.ca>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Frithjof Hammer <mail@...thjof-hammer.de>, lartc@...lman.ds9a.nl,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: [LARTC] ifb and ppp

On Thu, 2007-20-09 at 13:55 +0200, Patrick McHardy wrote:
> Please keep netdev and myself CCed.

and me too (I am way behind on netdev)

> Frithjof Hammer wrote:

> > Any further help/ideas?

Sorry, I didnt follow the thread - what is the goal to be achieved with
the setup?

> I misread the code, the device it looks at in tcf_mirred_init is
> the target device (ifb). So what it does is check whether the
> target device wants a link layer header and if it does restores
> the one from the source device. So currently it seems impossible
> to get rid of the PPP(oE) header.

It is tricky to redirect from devices that have disparity
in their view of link layer headers except for those that we know
dont expect anything. 

> Jamal, is that how its supposed to work?

Right - some netdevices on receipt will expect the link layer header.

cheers,
jamal

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html