[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <0977189F-9778-4D1C-939D-FAD71595E5F6@gmail.com>
Date: Thu, 29 Oct 2015 15:00:26 +0000
From: Gilberto Bertin <gilberto.bertin@...il.com>
To: netdev@...r.kernel.org
Subject: [BUG] Any-IP IPv6 support broken
Hello,
testing Any-IP on my machine, I noticed that it's not working with IPv6
addresses.
Tests are performed on a 4.1 kernel.
Steps to reproduce the bug:
1- make sure Any-IP is working with IPv4 addresses:
# ip -4 route add local 4.4.4.0/24 dev eth0
with this command every packets with an IP in the subnet 4.4.4.0/24 will
be delivered to the eth0 interface.
We can test this:
$ ping 4.4.4.1 -c 1 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
$ ping 4.4.4.50 -c 1 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
$ ping 4.4.4.200 -c 1 | grep received
1 packets transmitted, 1 received, 0% packet loss, time 0ms
2- note that it's not actually working with IPv6 addresses:
# ip -6 route add local abcd:abcd:abcd:abcd::/64 dev eth0
$ ping6 -c 1 abcd:abcd:abcd:abcd::1 | grep received
1 packets transmitted, 0 received, 100% packet loss, time 0ms
$ ping6 -c 1 abcd:abcd:abcd:abcd::50 | grep received
1 packets transmitted, 0 received, 100% packet loss, time 0ms
$ ping6 -c 1 abcd:abcd:abcd:abcd::100 | grep received
1 packets transmitted, 0 received, 100% packet loss, time 0ms
Since the kernel should support Any-IP with IPv6 addresses (the patch
was submitted/accepted years ago [1]) I suspect this is a bug.
Even trying with the commands suggested by the patch [1]:
# ip -6 rule add from all iif eth0 lookup 200
# ip -6 route add local default dev lo table 200
I was not able to get it working.
Thank you.
[1] http://www.spinics.net/lists/netdev/msg141994.html
--
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
Powered by blists - more mailing lists