[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170517.113948.1940714175629191091.davem@davemloft.net>
Date: Wed, 17 May 2017 11:39:48 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: mulmer@...dlepoint.com
Cc: netdev@...r.kernel.org
Subject: Re: [Patch][IPv6] Fix wrong routing mechanism for Link Local IPv6
packets
From: Michael Ulmer <mulmer@...dlepoint.com>
Date: Tue, 16 May 2017 15:37:39 +0000
> Blast from the past. 10 years back Wei Dong submitted the patch found (amongst several places) here:
> http://lists.openwall.net/netdev/2007/01/30/20
>
> Problem:
> I have a firewall rule that DNATs ipv6 traffic from a destination address to ::1. The route lookup gives me the Main table & forwards that DNAT'd traffic instead of sending it to local process.
>
> Example:
> Looking at this from a netfilter point of view, a client (IP of fd00::5) requests a web page at [2000::25:0:0:1]:8080. The firewall rule DNATs it to ::1 (note that I threw a -j TRACE in raw's REROUTING).
> TRACE: nat:PREROUTING:rule:2 SRC=fd00::5 DST=2000::25:0:0:1
> TRACE: mangle:FORWARD:rule:1 SRC=fd00::5 DST=::1
>
> The patch is verbatim (as is the subject line for this
> email). Traffic DNAT'd to ::1 now goes to mangle's INPUT chain after
> routing decision. I'm not sure why it was removed--I'm assuming it
> was an accident--as I can't find a record in the mailing list
> archive.
It's not by accident, he received feedback from Yoshifuji and suggested
alternative ways to fix his problem:
http://marc.info/?l=linux-netdev&m=117020569620697&w=2
In fact, Yoshifuji stated that some of the behaviors are indeed
intentional.
Powered by blists - more mailing lists