All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Frithjof Hammer <mail@frithjof-hammer.de>
Cc: lartc@mailman.ds9a.nl, Linux Netdev List <netdev@vger.kernel.org>,
	jamal <hadi@cyberus.ca>
Subject: Re: [LARTC] ifb and ppp
Date: Thu, 20 Sep 2007 11:55:06 +0000	[thread overview]
Message-ID: <46F25F9A.7010007@trash.net> (raw)
In-Reply-To: <200709192342.03646.mail@frithjof-hammer.de>

Please keep netdev and myself CCed.

Frithjof Hammer wrote:
>>Does this patch help?
> 
> 
> A further examiniation:
> [...]
> printk ("fri: mein type %x\n",dev->type);
>                 switch (dev->type) {
> 
> [...]
> shows this:
> 
> root@router:/usr/src/linux-source-2.6.21# dmesg | grep fri
> fri: mein type 1
> 
> that is defined as ARPHRD_ETHER in include/linux/if_arp.h.
> 
> As far as i understand this means, that my ppp0 device is recognized as 
> Ethernetinterface.
> 
> Any further help/ideas?


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.

Jamal, is that how its supposed to work?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2007-09-20 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 12:17 [LARTC] ifb and ppp Frithjof Hammer
2007-09-19 13:04 ` Patrick McHardy
2007-09-19 17:51 ` Frithjof Hammer
2007-09-19 21:42 ` Frithjof Hammer
2007-09-20 11:55   ` Patrick McHardy [this message]
     [not found]     ` <1190294388.4734.6.camel@localhost>
2007-09-20 14:00       ` Frithjof Hammer
2007-09-20 15:26         ` Patrick McHardy

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=46F25F9A.7010007@trash.net \
    --to=kaber@trash.net \
    --cc=hadi@cyberus.ca \
    --cc=lartc@mailman.ds9a.nl \
    --cc=mail@frithjof-hammer.de \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.