netdev
[Top] [All Lists]

Missing routes cause BUG() in icmpv6_xmit_lock().

To: netdev@xxxxxxxxxxx
Subject: Missing routes cause BUG() in icmpv6_xmit_lock().
From: David Woodhouse <dwmw2@xxxxxxxxxx>
Date: Sun, 31 Aug 2003 15:56:29 +0100
Organization: Red Hat UK Ltd.
Sender: netdev-bounce@xxxxxxxxxxx
Kernel is Red Hat 2.4.21-20.1.2024.2.1.nptlsmp from the Severn beta.
Triggered as follows:

Configure 6to4 IPv6 address 2002:X:Y::1 on the ISDN dialup.

Enable IPv6 forwarding on all interfaces

Configure radvd to advertise 2002:X:Y:1234::/64 on internal eth0 device
Observe radvd doesn't add any routes for the 2002:X:Y:1234::/64 subnet. 
Bring up an internal machine on eth0.
Observe it receive an IPv6 address of the form 2002:X:Y:1234:.....

Attempt to ping6 a machine in the outside world from the internal host.
Observe that reply packets from the outside world to the internal
address are routed straight back _out_ the 6to4 tunnel again, in the
absence of sane routes -- with associated bitching...
        redirect: no link_local addr for dev
        Dead loop on virtual device tun6to4, fix it urgently!

Attempt to ping6 the router 2002:X:Y::1 from internal host.
Observe panic: http://www.linux.org.uk/~dwmw2/dcp_1575.jpg

Should initscripts set up an unreachable route for 2002:X:Y::/48 when
setting up a 6to4 tunnel? Should radvd set up routes to subnets of that
network when advertising them internally according to its configuration?

Certainly the kernel should do something other than panicking :)

-- 
dwmw2


<Prev in Thread] Current Thread [Next in Thread>