netdev - Re: xfrm by MARK: tcp problems when mark for in and out differ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1287062098.3756.9.camel@bigi>
Date:	Thu, 14 Oct 2010 09:14:58 -0400
From:	jamal <hadi@...erus.ca>
To:	"Gerd v. Egidy" <lists@...dy.de>
Cc:	netdev@...r.kernel.org
Subject: Re: xfrm by MARK: tcp problems when mark for in and out differ

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

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html