|
routing problem on subnet in the outgoing direction
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Monday, 28 February 2005 12:03:00
Hi all
I'm a bit stuck here, I can't get out of my subnet...
I have the following setup:
host A (v4/v6)--- internet (v4) --- GW (v4)----- ethernet --- host B
+---- host C
so B and C are on the same subnet.
host B is my tunnel endpoint, it is advertising a globally routable subnet on the ethernet. host C gets a subnet advertised from radvd on host B.
now when I traceroute6 to the global address of host C, it reaches it (checked using "tcpdump ip6") and sends back a reply, but it never progresses to the default route on the tunnel.
so I get a path: A ... B, C, B and then it stops.
forwarding is turned on for ipv6 in node B, so that can't be it. the routing table has a default route to the other end of my tunnel to sixxs.
routing table on B:
ip -6 route
2001:610:600:73::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 metric10 64
2001:610:635::/64 dev eth0 metric 1 mtu 1500 advmss 1440 metric10 64
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 metric10 64
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 metric10 64
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 metric10 1
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 metric10 1
default via 2001:610:600:73::1 dev sixxs metric 1024 mtu 1280 advmss 1220 metric10 64
unreachable default dev lo proto none metric -1 error -101 advmss 1220 metric10 255
I don't see what's wrong here, any suggestions?
tnx
Simon
routing problem on subnet in the outgoing direction
What kernel version is it? Firewalling? Tried tcpdumping the tunnel on host B to see if the packet goes out?
routing problem on subnet in the outgoing direction
Shadow Hawkins on Monday, 28 February 2005 17:04:12
It's a standard mandrake 10.1 kernel 2.6.8.1-12mdkenterprise
I don't see any packets coming through the tunnel on the way back, once the traceroute reaches the destination host.
at this time, I'm not firewalling ipv6
tnx
Simon
routing problem on subnet in the outgoing direction
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Monday, 28 February 2005 21:06:44
Did you do:
echo "1" > /proc/sys/net/ipv6/conf/all/forwarding
?
routing problem on subnet in the outgoing direction
Shadow Hawkins on Tuesday, 01 March 2005 00:15:58
Yes, as I mentioned in the first posting, forwarding is turned on in node B for all interfaces. Which is proven by the fact that the packets reach node C, but do not get back to the tunnel from node B on the way back...
/Simon
routing problem on subnet in the outgoing direction
Shadow Hawkins on Tuesday, 01 March 2005 21:20:58
Small teory (fix your config if needed):
Host B
add address sixxs you_endpoint_v6_address_from_sixxs
add route default to sixxs
add address sixxs 2001:610:635::1/128
add address eth0 2001:610:635:1::1/128
add route 2001:610:635:1::/64 to eth0
enable forwarfing
Host C
add address eth0 2001:610:635:1::2/128
add route default via dev eth0 or 2001:610:635:1::1/128
(not sure, one of this sould work)
Host [n]
add address eth0 2001:610:635:1::[n]/128
add route default via dev eth0 or 2001:610:635:1::1/128
(not sure, one of this sould work)
Should this work.
I have very similar config on Windows, here is the config:
http://fido.e-utp.net/ipv6/lan/
Article in Polish, to better understand (Siec lokalna=Local Area Network)
FIXED routing problem on subnet in the outgoing direction
Shadow Hawkins on Monday, 21 March 2005 22:52:58
Hi there
sorry for the long delay, I didn't have time earlier to go after this problem. It turned out to be really one of those things :-(
The kernel I'm using is a stock mandrake 10.1 kernel. For some reason I had the idea/misconception that the default route problem had been fixed in the kernel for some time now. But finally, when I had checked everything else, the solution came when I added 2000::/8 via <tunnel> to the routing table. This is probably not the precise correct mask, but I remembered this from a couple of years back...
Sorry for the confusion...
/Simon
FIXED routing problem on subnet in the outgoing direction
Shadow Hawkins on Monday, 28 March 2005 09:29:06
AFAIK it should be 2000::/3
FIXED routing problem on subnet in the outgoing direction
Shadow Hawkins on Sunday, 03 April 2005 13:35:03
You're correct, I later checked it and found my mistake (although 2000::/8 also works ;-)
/Simon
|
![[ch]](/s/countries/ch.gif)
on Monday, 28 February 2005 15:46:39
Posting is only allowed when you are