From: Denys Fedoryschenko <denys@visp.net.lb>
To: netdev@vger.kernel.org, hadi@cyberus.ca
Subject: kernel mode pppoe ppp if + ifb + mirred redirect, ethernet packets in ifb?!
Date: Mon, 12 Oct 2009 11:43:39 +0300 [thread overview]
Message-ID: <200910121143.39924.denys@visp.net.lb> (raw)
Hi
I am using kernel mode pppoe, and while using mirred on ppp interfaces (to
shape users upstream) noticed very strange behaviour (and IMHO wrong)
$2 - ppp interface
tc filter add dev $2 parent ffff: protocol ip prio 10 u32 \
match u32 0 0 flowid 1:1 \
action mirred egress redirect dev ifb0"
If i do tcpdump on ppp interface i can see normal ip traffic
PPPoE_146 ~ # tcpdump -ni ppp6 -c 100
tcpdump: WARNING:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp6, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
11:36:16.541742 IP 172.16.131.221.2182 > 64.4.50.51.443: Flags [F.], seq
2636760792, ack 2812561777, win 64963, length 0
If i do tcpdump on ifb0 i will see PPPoE incapsulated traffic!
PPPoE_146 ~ # tcpdump -ni ifb0 -c 100
tcpdump: WARNING: ifb0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ifb0, link-type EN10MB (Ethernet), capture size 96 bytes
11:36:58.949727 PPPoE [ses 0x15] IP 172.16.98.22.2081 > 94.75.218.20.80:
Flags [S], seq 3205622298, win 65535, options [mss 1440,nop,nop,sackOK],
length 0
11:36:58.531473 PPPoE [ses 0xd] IP 172.16.98.14.16526 > 128.16.130.164.445:
Flags [S], seq 98566173, win 65535, options [mss 1440,nop,nop,sackOK], length
0
Is it expected that redirecting ppp interface, that supposed to be clean IP
traffic is becoming eth encapsulated traffic?
Probably some bad interaction with kernel mode pppoe?
next reply other threads:[~2009-10-12 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:43 Denys Fedoryschenko [this message]
2009-10-12 13:10 ` kernel mode pppoe ppp if + ifb + mirred redirect, ethernet packets in ifb?! jamal
2009-10-12 14:15 ` Denys Fedoryschenko
2009-10-12 20:57 ` jamal
2009-10-12 21:54 ` Denys Fedoryschenko
2009-10-12 22:07 ` jamal
2009-10-12 22:44 ` Denys Fedoryschenko
2009-10-13 12:21 ` jamal
2009-10-13 12:45 ` Denys Fedoryschenko
2009-10-13 13:02 ` jamal
2009-10-13 14:34 ` Benjamin LaHaise
2009-10-14 12:00 ` jamal
2009-10-14 19:11 ` Jarek Poplawski
2009-10-14 19:59 ` Jarek Poplawski
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=200910121143.39924.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).