netdev - Re: [Patch net] loopback: explicitly set pkt_type to PACKET

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 16 May 2014 10:52:09 -0700
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	Linux Kernel Network Developers <netdev@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Cong Wang <cwang@...pensource.com>
Subject: Re: [Patch net] loopback: explicitly set pkt_type to PACKET_HOST

On Thu, May 15, 2014 at 1:34 PM, David Miller <davem@...emloft.net> wrote:
> From: Cong Wang <xiyou.wangcong@...il.com>
> Date: Wed, 14 May 2014 11:39:22 -0700
>
>> From: Cong Wang <cwang@...pensource.com>
>>
>> In a corner case where I redirect the packets from veth to lo,
>> packets are dropped silently when entering IP stack. This is
>> due to we have a different MAC addr on veth, so the packets are
>> marked as PACKET_OTHERHOST. And after they are redirect to lo,
>> this value is kept since lo has the same MAC addr with the packets.
>> Loopback should explicitly set it to PACKET_HOST before calling
>> eth_type_trans() for this specific case.
>>
>> Cc: David S. Miller <davem@...emloft.net>
>> Cc: "Eric W. Biederman" <ebiederm@...ssion.com>
>> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>
>> Signed-off-by: Cong Wang <cwang@...pensource.com>
>
> How exactly are you performing this redirection?

Oh, I meant using tc mirred action to redirect packets from vethX to lo.
Sorry for confusing.
--
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