From: "Sebastian Pöhn" <sebastian.poehn@gmail.com>
To: Bob Miller <bob@computerisms.ca>
Cc: netfilter@vger.kernel.org
Subject: Re: packet marking
Date: Thu, 05 Mar 2015 20:44:13 +0100 [thread overview]
Message-ID: <1425584653.3192.3.camel@gmail.com> (raw)
In-Reply-To: <54F78167.6070104@computerisms.ca>
Is there a reason to use decimal numbers? 0x1E and 0x28 are quite
complex marks to set. Maybe use 0x30 and 0x40 instead.
Is there any other place where marking is done?
Why not providing us with a full iptables-save output?
On Mi, 2015-03-04 at 14:04 -0800, Bob Miller wrote:
> I have been reading man pages and googling and I am not finding
> understanding. maybe somebody can explain:
>
> under my mangle table (using iptables-restore to load):
>
> -A PREROUTING -p udp -m udp --dport 4500 -j MARK --set-mark 30
> -A PREROUTING -s 192.168.171.0/24 -m mark ! --mark 30 -j MARK --set-mark 40
> -A PREROUTING -m mark --mark 30 -j LOG --log-prefix vpnX30
> -A PREROUTING -m mark --mark 40 -j LOG --log-prefix vpnX40
>
> This logs packets with both marks.
>
> If I change the LOG target to POSTROUTING, like so:
>
> -A POSTROUTING -m mark --mark 30 -j LOG --log-prefix vpnX30
> -A POSTROUTING -m mark --mark 40 -j LOG --log-prefix vpnX40
>
> only packets with the mark 40 are logged. I think it should log both.
>
> If I consult the nfpacket flow chart, nat/PREROUTING comes after
> mangle/PREROUTING, and I cannot log packets with a mark of 30 there either.
>
> Traffic keeps flowing, so the packets themselves are not being dropped,
> but the mark apparently is not passed from the initial chain. Everything
> I have read indicates it should be. what could I have done (or not
> done) to make this happen? Or better yet, what should I be reading that
> would explain this? I get the feeling I am overlooking something really
> obvious...
prev parent reply other threads:[~2015-03-05 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 22:04 packet marking Bob Miller
2015-03-05 7:01 ` Michal Kubecek
2015-03-05 19:44 ` Sebastian Pöhn [this message]
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=1425584653.3192.3.camel@gmail.com \
--to=sebastian.poehn@gmail.com \
--cc=bob@computerisms.ca \
--cc=netfilter@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