• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Problems with tunnelbroker (Destination unreachable: Address unreachable)

Started by vbserver, March 29, 2011, 12:19:44 PM

Previous topic - Next topic

vbserver

Hi @all :)

I have some problems setting up my tunnel :( Here my bash history:


synology> ls
sit.ko      tunnel4.ko
synology> insmod tunnel4.ko
synology> insmod sit.ko

synology> chroot /volume1/debian/debian/ /bin/bash

root@synology:/# ip tunnel add he-ipv6 mode sit remote 209.51.161.58 local 84.74.139.146 ttl 255
root@synology:/# ip link set he-ipv6 up
root@synology:/# ip addr add 2001:470:4:28b::2/64 dev he-ipv6
root@synology:/# ip route add ::/0 dev he-ipv6
root@synology:/# ip -f inet6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436
   inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,ALLMULTI,NOTRAILERS,UP,LOWER_UP> mtu 1500 qlen 532
   inet6 2001:1620:f48::3/64 scope global
      valid_lft forever preferred_lft forever
   inet6 fe80::211:32ff:fe05:cd90/64 scope link
      valid_lft forever preferred_lft forever
6: he-ipv6: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480
   inet6 2001:470:4:28b::2/64 scope global
      valid_lft forever preferred_lft forever

root@synology:/# ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8002::93) 56 data bytes
From vbserver-1-pt.tunnel.tserv12.mia1.ipv6.he.net icmp_seq=1 Destination unreachable: Address unreachable
From vbserver-1-pt.tunnel.tserv12.mia1.ipv6.he.net icmp_seq=2 Destination unreachable: Address unreachable
From vbserver-1-pt.tunnel.tserv12.mia1.ipv6.he.net icmp_seq=3 Destination unreachable: Address unreachable
From vbserver-1-pt.tunnel.tserv12.mia1.ipv6.he.net icmp_seq=4 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3022ms

root@synology:/#


What's wrong? Please tell me if you need some more infos :)

greetings & thx,
patrick


EDIT: Wrong category, please move ;)

cholzhauer

Couple things...are you behind nat?

Second thing, don't use that ::3 address on your local adapter.  On your tunnel page, there should be a routed /64 line...use an address from that and put it on eth0

vbserver

Hi and thanks for the fast answer :)

the ::3 is from SIXXS (don't want to use it 1 more minute ... ;)). Yes, i'm behind a nat. I tried it on another debian box, works  :o

patrick

cholzhauer

Yeah, remove the address from eth0...that'll create problems.

If you're behind NAT, you need to use your NAT address to create your tunnel

vbserver

wow, thank you, works  :)


root@synology:/# ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8002::93) 56 data bytes
64 bytes from 2a00:1450:8002::93: icmp_seq=1 ttl=53 time=253 ms
64 bytes from 2a00:1450:8002::93: icmp_seq=2 ttl=53 time=250 ms
64 bytes from 2a00:1450:8002::93: icmp_seq=3 ttl=53 time=256 ms
64 bytes from 2a00:1450:8002::93: icmp_seq=4 ttl=53 time=251 ms
^C
--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3023ms
rtt min/avg/max/mdev = 250.800/253.123/256.426/2.224 ms
root@synology:/#

bye bye sixxs, welcome HE :D


Thank you so much :)

sdogr

hi vbserver
how did you compile the kernel modules?
i've been looking everywhere but cannot find anything...
thanks and regards
sdogr