From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, green@msu.ru
Subject: Re: [Bugme-new] [Bug 14427] New: ipv6 forward cause strange route
Date: Mon, 2 Nov 2009 22:32:37 -0800 [thread overview]
Message-ID: <20091102223237.c0102f19.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-14427-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sat, 17 Oct 2009 10:42:01 GMT bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14427
>
> Summary: ipv6 forward cause strange route
> Product: Networking
> Version: 2.5
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV6
> AssignedTo: yoshfuji@linux-ipv6.org
> ReportedBy: green@msu.ru
> Regression: No
>
>
> When enabling forwarding for IPv6 on interface, in the routing table local
> appears new route. It like route to local ip but with all host bits set to 0.
> Example:
> --------------------------------------------------
> # cat /proc/sys/net/ipv6/conf/eth0/forwarding
> 0
> # ip -6 addr add 2001:db8:1:1::5/64 dev eth0
> # ip -6 route show table local
> ...
> local 2001:db8:1:1::5 via :: dev lo proto none metric 0 mtu 16436 advmss
> 16376 hoplimit 4294967295
> ...
> # echo 1 > /proc/sys/net/ipv6/conf/eth0/forwarding
> # ip -6 route show table local
> ...
> local 2001:db8:1:1:: via :: dev lo proto none metric 0 mtu 16436 advmss
> 16376 hoplimit 4294967295
> local 2001:db8:1:1::5 via :: dev lo proto none metric 0 mtu 16436 advmss
> 16376 hoplimit 4294967295
> ...
> --------------------------------------------------
> After enabling forwarding, route "2001:db8:1:1:: via :: dev lo" is added. No
> matter, forwarding is enabled before or after adding of address, this route is
> "on" with forwarding and "off" without it.
> Such behavior causes problems with /127 network masks. For example:
> --------------------------------------------------
> # echo 1 > /proc/sys/net/ipv6/conf/eth0/forwarding
> # ip -6 addr add 2001:db8:1:1::5/127 dev eth0
> # ip -6 route add default via 2001:db8:1:1::4
> RTNETLINK answers: Invalid argument
> --------------------------------------------------
> But if we disable forwarding (and strange route) when adding needed route, we
> will succeed.
> --------------------------------------------------
> # echo 0 > /proc/sys/net/ipv6/conf/eth0/forwarding
> # ip -6 route add default via 2001:db8:1:1::4
> # echo 1 > /proc/sys/net/ipv6/conf/eth0/forwarding
> --------------------------------------------------
> Default route remains in the table after enabling forwarding and it is doing in
> work. But in this case we still can not access 2001:db8:1:1::4, because it is
> routed to loopback:
> --------------------------------------------------
> # ping6 -c 1 2001:db8:1:1::4
> PING 2001:db8:1:1::4(2001:db8:1:1::4) 56 data bytes
> 64 bytes from 2001:db8:1:1::5: icmp_seq=1 ttl=64 time=0.114 ms
> --------------------------------------------------
> We get reply from self interface.
>
> This was tested on x86 and x86_64 with 2.6.30 kernel and some previous versions
> on ArchLinux (2.6.30 x86 and x86_64), Ubuntu (2.6.28-15-generic x86_64) and
> gentoo (2.6.30-gentoo-r5 x86_64).
>
next parent reply other threads:[~2009-11-03 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14427-10286@http.bugzilla.kernel.org/>
2009-11-03 6:32 ` Andrew Morton [this message]
2009-11-03 11:06 ` [Bugme-new] [Bug 14427] New: ipv6 forward cause strange route YOSHIFUJI Hideaki
2009-11-03 11:19 ` YOSHIFUJI Hideaki
2009-11-04 8:01 ` Pekka Savola
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=20091102223237.c0102f19.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=green@msu.ru \
--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).