From: jamal <hadi@cyberus.ca>
To: "Gerd v. Egidy" <lists@egidy.de>
Cc: netdev@vger.kernel.org, dev@lists.strongswan.org
Subject: Re: xfrm by MARK: tcp problems when mark for in and out differ
Date: Thu, 14 Oct 2010 08:02:21 -0400 [thread overview]
Message-ID: <1287057741.3756.6.camel@bigi> (raw)
In-Reply-To: <201010131557.06588.lists@egidy.de>
On Wed, 2010-10-13 at 15:57 +0200, Gerd v. Egidy wrote:
> Hi,
>
> -> incoming packets are without mark, outgoing packets are marked with 5
>
You could use tc ingress path to mark incoming packets. Example:
----
tc qdisc add dev eth0 ingress
tc filter add dev eth0 parent ffff: protocol ip pref 9 u32 \
match ip src 192.168.1.0/32 flowid 1:5 action skbedit mark 5
---
just remember that src on outgoing is dst on incoming..
cheers,
jamal
next prev parent reply other threads:[~2010-10-14 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 13:57 xfrm by MARK: tcp problems when mark for in and out differ Gerd v. Egidy
2010-10-14 12:02 ` jamal [this message]
2010-10-14 13:01 ` Gerd v. Egidy
2010-10-14 13:14 ` jamal
2010-10-14 14:14 ` -j MARK in raw vs. mangle (was Re: xfrm by MARK: tcp problems when mark for in and out differ) Gerd v. Egidy
2010-10-14 12:05 ` xfrm by MARK: tcp problems when mark for in and out differ jamal
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=1287057741.3756.6.camel@bigi \
--to=hadi@cyberus.ca \
--cc=dev@lists.strongswan.org \
--cc=lists@egidy.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.