Topic: 6to4 not working

The content of this topic has been archived on 25 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 1 of 1

Post #1

blitzkrieg3

11 Apr 2009, 15:28

Edit: SOLVED

Hi,

I'm waiting from my Sixxs.net tunnel, but I can't seem to get 6to4 working. I was following the guide here http://oldwiki.openwrt.org/IPv6_howto.html. I was trying to use the instructions to set up /etc/hotplug.d/iface/10-ipv6 correctly, but I wound up doing it by hand.

Anyway this is the configuration I have presently.

# ip tunnel
sit0: ipv6/ip  remote any  local any  ttl 64  nopmtudisc
tun6to4: ipv6/ip  remote any  local 24.215.173.185  ttl 64

Added the tunnel.

# ip -6 addr 
1: lo: <LOOPBACK,UP> 
    inet6 ::1/128 scope host 
2: eth0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> qlen 1000
    inet6 fe80::213:10ff:fe96:5b5d/64 scope link 
3: eth1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> qlen 1000
    inet6 fe80::213:10ff:fe96:5b5f/64 scope link 
6: vlan0: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> 
    inet6 fe80::213:10ff:fe96:5b5d/64 scope link 
7: vlan1: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP> 
    inet6 fe80::213:10ff:fe96:5b5e/64 scope link 
10: br0: <BROADCAST,MULTICAST,UP> 
    inet6 2002:18d7:ad12:5678::1/64 scope global 
    inet6 fe80::213:10ff:fe96:5b5d/64 scope link 
11: tun6to4: <NOARP,UP> 
    inet6 ::24.215.173.185/128 scope global 
    inet6 2002:18d7:ad12::1/16 scope global

Set up the addresses, specifically both on tun6to4 and 2002: on br0

ip -6 route
::/96 via :: dev tun6to4  metric 256  mtu 1480 advmss 1420
2002:18d7:ad12:5678::/74 dev br0  metric 256  mtu 1500 advmss 1440
2002:18d7:ad12:5678::/64 dev br0  metric 256  mtu 1500 advmss 1440
2002::/16 dev tun6to4  metric 256  mtu 1480 advmss 1420
2000::/3 via ::192.88.99.1 dev tun6to4  metric 1  mtu 1480 advmss 1420
fe80::/64 dev eth0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev vlan0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev eth1  metric 256  mtu 1500 advmss 1440
fe80::/64 dev br0  metric 256  mtu 1500 advmss 1440
fe80::/64 dev vlan1  metric 256  mtu 1500 advmss 1440
fe80::/64 dev tun6to4  metric 256  mtu 1480 advmss 1420
ff00::/8 dev eth0  metric 256  mtu 1500 advmss 1440
ff00::/8 dev vlan0  metric 256  mtu 1500 advmss 1440
ff00::/8 dev eth1  metric 256  mtu 1500 advmss 1440
ff00::/8 dev br0  metric 256  mtu 1500 advmss 1440
ff00::/8 dev vlan1  metric 256  mtu 1500 advmss 1440
ff00::/8 dev tun6to4  metric 256  mtu 1480 advmss 1420
unreachable default dev lo  proto none  metric -1  error -128

routing table. Anyone see anything braindead here, I'm an ipv6 n00b.

(Last edited by blitzkrieg3 on 11 Apr 2009, 18:25)

Post #2

blitzkrieg3

11 Apr 2009, 16:21

Alright, I am able to ping www.kame.net by issuing a network restart. I guess a lot of setup is handled automatically now?

However, packets still aren't being routed from br0 to tun6to4! I've pasted my radvd.conf

# For more examples, see the radvd documentation.

interface br0
{            
        AdvSendAdvert on;

#
# Disable Mobile IPv6 support
#                            
        AdvHomeAgentFlag off;

        MinRtrAdvInterval 5;
        MaxRtrAdvInterval 10;

#
# example of a standard prefix
#                             
#       prefix fec0:0:0:1::/64
#       {                     
#               AdvOnLink on;
#               AdvAutonomous on;
#               AdvRouterAddr off;
#       };                        

        prefix 0:0:0:5678::/64
        {
                AdvOnLink on;
                AdvAutonomous on;
                AdvRouterAddr on;
        };


};

and before executing radvd, I do a

ip -6 addr add 2002:18d7:adb9:5678::1/64 dev br0

everything works on the radvdump.

I'll be hacking away on this later today but if anyone has any obvious suggestions please help

Post #3

blitzkrieg3

11 Apr 2009, 16:32

Here's how everything looks from the client side:

[root@zeik ~]# ip -6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 100
    inet6 ::5678:215:58ff:fe86:e449/64 scope global dynamic 
       valid_lft 2591992sec preferred_lft 604792sec
    inet6 fe80::215:58ff:fe86:e449/64 scope link 
       valid_lft forever preferred_lft forever
[root@zeik ~]# ip -6 route
0:0:0:5678::/64 dev eth0  proto kernel  metric 256  expires 2147157sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
default via fe80::213:10ff:fe96:5b5d dev eth0  proto kernel  metric 1024  expires 22sec mtu 1500 advmss 1440 hoplimit 64
[root@zeik ~]# ping6 fe80::213:10ff:fe96:5b5d
connect: Invalid argument
[root@zeik ~]# ping6 ::5678:215:58ff:fe86:e449
PING ::5678:215:58ff:fe86:e449(::5678:215:58ff:fe86:e449) 56 data bytes
64 bytes from ::5678:215:58ff:fe86:e449: icmp_seq=1 ttl=64 time=0.074 ms
64 bytes from ::5678:215:58ff:fe86:e449: icmp_seq=2 ttl=64 time=0.058 ms

Post #4

blitzkrieg3

11 Apr 2009, 18:26

Hmm,

I wasn't using the correct subnet. I think we should correct

Warning: use prefix 0:0:0:5678::/64 in your /etc/radvd.conf. The subnet 5678 is hardcoded in this script.

on the howto...

The discussion might have continued from here.

Page 1 of 1