From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Greg Scott <GregScott@InfraSupportEtc.com>
Subject: Re: Ebtables hook order anomaly
Date: Tue, 25 Mar 2008 13:57:24 +0100 [thread overview]
Message-ID: <47E8F6B4.4030800@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0803250455030.9368@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
>
> On Tuesday 2008-03-25 03:28, Jan Engelhardt wrote:
>>
>>> None of my packets that were supposed to have that "3" mark ever kept
>>> them. For some reason, they either never were marked or they were
>>> marked and then the mark disappeared.
>>
>> I can reproduce it. [...]
>> Now that is indeed interesting. I had this thought, maybe the mark
>> does not disappear, maybe ebtables is run -- contrary to most graphics
>> depicting the netfilter flow -- _after_ iptables. So I tried:
>>
>> iptables -t mangle -A POSTROUTING -j LOG --log-prefix "[ipt] " -d
>> 134.76.13.21
>> ebtables -A OUTPUT -p ipv4 --ip-destination 134.76.13.21 --log
>> --log-prefix "[ebt] "
>>
>> with the result of:
>>
>> [214961.190130] [ipt] IN= OUT=br0 SRC=10.10.106.161 DST=134.76.13.21
>> LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=ICMP TYPE=8 CODE=0
>> ID=59252 SEQ=1
>>
>> [214961.190186] [ebt] IN= OUT=sis0 MAC source = 00:0a:e6:98:ed:d7
>> MAC
>> dest = 68:a8:3e:d3:d0:fb proto = 0x0800
>>
>> which means ebtables actually comes after iptables, and hence, your
>> mark 3 will not show up as you expected.
Indeed, on output bridge netfilter will run after IPv4 netfilter.
Does that explain things?
next prev parent reply other threads:[~2008-03-25 12:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 1:18 ebtables and iptables different behavior between 2.6.18 on fc6 and 2.6.23 on fc8 Greg Scott
2008-03-25 2:28 ` Jan Engelhardt
2008-03-25 6:48 ` Ebtables hook order anomaly (was: ebtables and iptables different behavior between 2.6.18 on fc6 and 2.6.23 on fc8) Jan Engelhardt
2008-03-25 12:57 ` Patrick McHardy [this message]
2008-04-09 14:07 ` Ebtables hook order anomaly Jan Engelhardt
2008-04-09 14:36 ` Patrick McHardy
2008-04-09 14:54 ` Jan Engelhardt
2008-04-09 15:04 ` Patrick McHardy
2008-04-09 15:12 ` Greg Scott
2008-04-09 16:11 ` Jan Engelhardt
2008-04-09 16:18 ` Greg Scott
2008-04-09 15:05 ` Greg Scott
2008-04-09 15:11 ` Patrick McHardy
2008-04-09 15:21 ` Greg Scott
2008-04-09 15:23 ` Patrick McHardy
2008-04-09 15:39 ` Greg Scott
-- strict thread matches above, loose matches on Subject: below --
2008-03-25 13:32 Greg Scott
2008-03-25 13:49 ` Patrick McHardy
2008-03-25 15:22 ` Jan Engelhardt
2008-03-25 15:30 ` Patrick McHardy
2008-03-25 14:17 Greg Scott
2008-03-25 17:02 Greg Scott
2008-03-26 7:16 ` Patrick McHardy
2008-03-27 7:55 Greg Scott
2008-03-30 21:21 Greg Scott
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=47E8F6B4.4030800@trash.net \
--to=kaber@trash.net \
--cc=GregScott@InfraSupportEtc.com \
--cc=jengelh@computergmbh.de \
--cc=netfilter-devel@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.