I successfully set up a point-to-point tunnel and I am trying to include my workstation in the ipv6 subnet so I can reach ipv6 services from it as well. Pinging to external addresses works from my server but not from my workstation although I have enabled forwarding for proto 41 trough iptables.
On my ipv6 enabled workstation (Windows XP Pro SP3) I do get an ipv6 address (2001:470:1f15:577:2400:a7f1:eaa0:1ed & 2001:470:1f15:577:219:dbff:fe4d:e640) where the second address is based on my mac address. When I try to ping these addresses from my server the dest. cannot be reached.
Probably I am overlooking something quite simplistic however I don't fully grasp the understanding behind routing network traffic since I always worked with NAT.
Any help will be greatly appreciated.
If any more information is needed just let me know and I'll send it as soon as possible.
With kind regards,
Henk
Netherlands, the
Server / Router: Debian Etch
eth0 = WAN
eth1 = LAN
sit0/1 = tunnel
venet0 = OpenVZ interface
Commands I have executed for the tunnel:
# ifconfig sit0 up
# ifconfig sit0 inet6 tunnel ::216.66.84.46
# ifconfig sit1 up
# ifconfig sit1 inet6 add 2001:470:1f14:577::2/64
# route -A inet6 add 2000::/3 dev sit1
# ifconfig |grep -A 4 -e sit -e eth
eth0 Link encap:Ethernet HWaddr 00:10:5A:2F:E8:32
inet addr:85.223.49.57 Bcast:85.223.63.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:567776171 errors:133 dropped:0 overruns:27 frame:142
TX packets:563207472 errors:0 dropped:0 overruns:0 carrier:0
--
eth1 Link encap:Ethernet HWaddr 7C:5B:F5:FC:1B:00
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2001:470:d128::1/48 Scope:Global
inet6 addr: fe80::7e5b:f5ff:fefc:1b00/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
--
sit0 Link encap:IPv6-in-IPv4
inet6 addr: ::127.0.0.1/96 Scope:Unknown
inet6 addr: ::85.223.49.57/96 Scope:Compat
inet6 addr: ::192.168.0.1/96 Scope:Compat
UP RUNNING NOARP MTU:1480 Metric:1
--
sit1 Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:1f14:577::2/64 Scope:Global
inet6 addr: fe80::55df:3139/64 Scope:Link
inet6 addr: fe80::c0a8:1/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
# cat /proc/sys/net/ipv6/conf/all/forwarding
1
# cat /etc/radvd.conf
interface eth1 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
prefix 2001:470:d128::/48 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
# route -6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 21740 1 lo
::85.223.49.57/128 :: U 0 0 1 lo
::127.0.0.1/128 :: U 0 0 1 lo
::192.168.0.1/128 :: U 0 0 1 lo
::/96 :: U 256 0 0 sit0
2001:470:1f14:577::/128 :: U 0 0 2 lo
2001:470:1f14:577::2/128 :: U 0 111 1 lo
2001:470:1f14:577::/64 :: U 256 3 0 sit1
2001:470:d128::/128 :: U 0 0 2 lo
2001:470:d128::1/128 :: U 0 13 1 lo
2001:470:d128::/48 :: U 256 0 0 eth1
2001:888:2163::3:0:10/128 2001:888:2163::3:0:10 UC 0 4 1 sit1
2000::/3 :: U 1 0 0 sit1
fe80::/128 :: U 0 0 2 lo
fe80::/128 :: U 0 0 2 lo
fe80::55df:3139/128 :: U 0 0 1 lo
fe80::c0a8:1/128 :: U 0 0 1 lo
fe80::7e5b:f5ff:fefc:1b00/128 :: U 0 13 1 lo
fe80::/64 :: U 256 0 0 eth1
fe80::/64 :: U 256 0 0 sit1
ff02::1/128 ff02::1 UC 0 366 0 eth1
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 sit1
eth1 on your server has been configured for your routed /48, but your workstation has an address from your routed /64 (which is weird, because it can't have gotten that from radvd)
Quote from: elc on September 07, 2008, 06:47:49 AM
eth1 on your server has been configured for your routed /48, but your workstation has an address from your routed /64 (which is weird, because it can't have gotten that from radvd)
In a previous configuration I did had configured my /64 in radvd, so I guess my WS got it from then. But I would expect that my WS would pick up the radvd change after a reboot or something?