[ale] IPv6 routing issues

JK jknapka at kneuro.net
Fri Sep 4 14:49:54 EDT 2009


Thank you for your assistance, Mike.  addrs and routes below.

Michael H. Warfield wrote:

> 	Run the following and post them.  Sanitize them if you like,
> personally, I don't care about mine, people can look up my v6 addresses
> in my DNS just like all my v4 address.  My space is 2001:4830:3000::/48
> from OCCAID.
> 
> 	Run the following.
> 
> 	ip -6 addr ls
> 	ip -6 route ls


Note, I'm behind a NAT DSL modem/router; I hope that's not the
problem.  My impression is that once the tunnel is up the
IP4 NAT should not be an issue.

eth0 is the interface connected to the DSL box.

eth1 is local.

wlan2 is talking to a wifi router in front of a TWRR cable
connection, but it's just a backup and doesn't have anything
routed through it at the moment.

The default IP4 route goes out eth0 through the DSL box.


jk at polymath #  ip -6 addr ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
     inet6 fe80::2a0:ccff:fedb:bed0/64 scope link
        valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
     inet6 2001:5c0:1504:e100::1/64 scope global
        valid_lft forever preferred_lft forever
     inet6 fe80::224:8cff:fe0a:6dfa/64 scope link
        valid_lft forever preferred_lft forever
12: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
     inet6 fe80::2a1:b0ff:feab:1117/64 scope link
        valid_lft forever preferred_lft forever
14: sit1 at NONE: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280
     inet6 2001:5c0:1400:b::3f71/128 scope global
        valid_lft forever preferred_lft forever
     inet6 fe80::c0a8:6572/64 scope link
        valid_lft forever preferred_lft forever
     inet6 fe80::c0a8:6604/64 scope link
        valid_lft forever preferred_lft forever
     inet6 fe80::af7:1/64 scope link
        valid_lft forever preferred_lft forever

jk at polymath #  ip -6 route ls
2001:5c0:1400:b::3f71 via :: dev sit1  proto kernel  metric 256  mtu 1280 advmss 1220 hoplimit 
4294967295
2001:5c0:1504:e100::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
2001:5c0:1504:e100::/56 dev eth0  metric 1  mtu 1500 advmss 1440 hoplimit 4294967295
2000::/3 dev sit1  metric 1024  mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth1  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev wlan2  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev sit1  proto kernel  metric 256  mtu 1280 advmss 1220 hoplimit 4294967295
default dev sit1  metric 1024  mtu 1280 advmss 1220 hoplimit 4294967295


> 	I'm a Fedora / rpm / sysv init person so it may be a little more
> challenging for me to figure out whats wrong on that Ubuntu box.


Well, I'm doing all this manually at the moment.  I tend to keep my
own set of setup scripts and invoke them from /etc/rc.local, in order
to avoid having to care about SysV vs BSD init stuff when I switch
distros/machines.  Once I get things working manually and understand
why they work, I add them to my scripts. So I don't care how all this
fits into the Ubuntu init stuff; I just want to generally understand
how to set up an IP6 tunnel and route traffic thru it.

-- JK



More information about the Ale mailing list