From: Gilberto Bertin <gilberto.bertin@gmail.com>
To: netdev@vger.kernel.org
Subject: [BUG] Any-IP IPv6 support broken
Date: Thu, 29 Oct 2015 15:00:26 +0000 [thread overview]
Message-ID: <0977189F-9778-4D1C-939D-FAD71595E5F6@gmail.com> (raw)
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
next reply other threads:[~2015-10-29 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:00 Gilberto Bertin [this message]
2015-10-29 15:34 ` [BUG] Any-IP IPv6 support broken Eric Dumazet
2015-10-30 0:44 ` Maciej Żenczykowski
2015-11-02 18:45 ` Gilberto Bertin
2015-11-02 21:30 ` Maciej Żenczykowski
2015-10-29 18:39 ` Hannes Frederic Sowa
2015-10-29 18:58 ` Gilberto Bertin
2015-10-29 19:09 ` Hannes Frederic Sowa
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=0977189F-9778-4D1C-939D-FAD71595E5F6@gmail.com \
--to=gilberto.bertin@gmail.com \
--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).