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

Destination unreachable: Address unreachable

Started by obluda, August 17, 2008, 06:05:10 AM

Previous topic - Next topic

obluda

Hi,

I tried to find something useful in old posts, but without success. Iam really desperate guys, if you could please point me the right way, otherwise i'm going to contact my ISP. because of protocol41 block.


Server IPv4 address:  216.66.80.30
Server IPv6 address: 2001:0470:1f0a:844::1/64
Client IPv4 address: 89.102.137.167
Client IPv6 address: 2001:0470:1f0a:844::2/64



ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:19:db:cd:f7:db brd ff:ff:ff:ff:ff:ff
    inet6 fe80::219:dbff:fecd:f7db/64 scope link
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:19:db:cd:f7:db brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 brd 192.168.0.255 scope global br0
    inet6 fe80::219:dbff:fecd:f7db/64 scope link
       valid_lft forever preferred_lft forever
12: he-ipv6@br0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN
    link/sit 89.102.137.167 peer 216.66.80.30
    inet6 2001:470:1f0a:844::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::5966:89a7/128 scope link
       valid_lft forever preferred_lft forever



ip -6 route
2001:470:1f0a:844::/64 via :: dev he-ipv6  metric 256  mtu 1480 advmss 1420 hoplimit 4294967295
fe80::/64 via :: dev he-ipv6  metric 256  mtu 1480 advmss 1420 hoplimit 4294967295
default dev he-ipv6  metric 1024  mtu 1480 advmss 1420 hoplimit 4294967295



ping6 2001:0470:1f0a:844::2
PING 2001:0470:1f0a:844::2(2001:470:1f0a:844::2) 56 data bytes
64 bytes from 2001:470:1f0a:844::2: icmp_seq=1 ttl=64 time=0.027 msx



ping6 2001:0470:1f0a:844::1
PING 2001:0470:1f0a:844::1(2001:470:1f0a:844::1) 56 data bytes
From 2001:470:1f0a:844::2 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:470:1f0a:844::2 icmp_seq=2 Destination unreachable: Address unreachable



ping6 ipv6.google.com
PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
From obluda-1-pt.tunnel.tserv6.fra1.ipv6.he.net icmp_seq=1 Destination unreachable: Address unreachable
From obluda-1-pt.tunnel.tserv6.fra1.ipv6.he.net icmp_seq=2 Destination unreachable: Address unreachable



traceroute ipv6.google.com
traceroute to ipv6.google.com (2001:4860:0:1001::68), 30 hops max, 40 byte packets
1  obluda-1-pt.tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:844::2)  0.026 ms !H  0.012 ms !H  0.014 ms !H


I think it doesnt need any comment, I just cannot reach anything on the other side. Thanks alot.

obluda

i've forgot to inform you about ip[6]tables, which are both clear, isp has been involved too.

in tcpdump i can see only requests during pinging
tcpdump -i he-ipv6 ip6
15:19:29.991901 IP6 obluda-1-pt.tunnel.tserv6.fra1.ipv6.he.net > 2001:4860:0:1001::68: ICMP6, echo request, seq 275, length 64
15:19:30.991900 IP6 obluda-1-pt.tunnel.tserv6.fra1.ipv6.he.net > 2001:4860:0:1001::68: ICMP6, echo request, seq 276, length 64

obluda

looks like solved, di524 doesnt have proto41 support.  :-[