From: jamal <hadi@cyberus.ca>
To: "Gerd v. Egidy" <lists@egidy.de>
Cc: netdev@vger.kernel.org
Subject: Re: xfrm by MARK: tcp problems when mark for in and out differ
Date: Thu, 14 Oct 2010 09:14:58 -0400 [thread overview]
Message-ID: <1287062098.3756.9.camel@bigi> (raw)
In-Reply-To: <201010141501.59145.lists@egidy.de>
Gerd,
On Thu, 2010-10-14 at 15:01 +0200, Gerd v. Egidy wrote:
> this is wrong, the value in fl->mark is always 0. I must have confused some
> data in my debug printks.
>
> So it seems like the fl->mark is never initialized with the packet mark in the
> first place. What would be the correct stage in the kernel network stack to do
> that?
Can you try a simple setup without xfrm/ipsec and see if this reverse
path works? Was there a kernel where it worked?
cheers,
jamal
next prev parent reply other threads:[~2010-10-14 13:15 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
2010-10-14 13:01 ` Gerd v. Egidy
2010-10-14 13:14 ` jamal [this message]
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=1287062098.3756.9.camel@bigi \
--to=hadi@cyberus.ca \
--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 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).