Hurricane Electric's IPv6 Tunnel Broker Forums
May 25, 2013, 03:52:11 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Hurricane Electric's Tunnelbroker.net forums!
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Destination unreachable: Address unreachable  (Read 2367 times)
yang0914
Newbie
*
Posts: 4


View Profile
« on: April 29, 2012, 08:48:27 am »

Hi, all:
I have created a ipv6 tunnel on a Fedora server with the following commands:
Code:
modprobe ipv6
ip tunnel add he-ipv6 mode sit remote 74.82.46.6 local 10.21.0.8 ttl 255
ip link set he-ipv6 up
ip addr add 2001:470:23:5d8::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
I use the private IP address(10.21.0.Cool instead of my public address(114.xx.xx.xx)
But when I finish all the steps and ping6 a ipv6 address like 2001:470:23:5d8::1 or www.kame.net,
The response will always show "Destination unreachable: Address unreachable"

Could someone tell me where I have gone wrong?
Thanks.
Logged
cholzhauer
Hero Member
*****
Posts: 2082


View Profile
« Reply #1 on: April 29, 2012, 06:16:26 pm »

Are you able to ping the HE side of the tunnel?

Is your router router properly forwarding protocol41?
Logged
yang0914
Newbie
*
Posts: 4


View Profile
« Reply #2 on: April 29, 2012, 06:39:27 pm »

I can ping the IPv4 address of the remote tunnel end point, but not work with the IPv6 address. Huh
And my router can forward the proto41 packets.   
Logged
cholzhauer
Hero Member
*****
Posts: 2082


View Profile
« Reply #3 on: April 29, 2012, 07:47:57 pm »

Yeah I meant if you could ping the ipv6 address.  How do you know your router can forward protocol 41?
Logged
yang0914
Newbie
*
Posts: 4


View Profile
« Reply #4 on: April 29, 2012, 10:57:31 pm »

Because someone else has done this before ...
Logged
broquea
Senior Network Engineer, SEVEN Networks (AS19733)
Hero Member
*****
Posts: 1379



View Profile WWW
« Reply #5 on: April 29, 2012, 11:00:54 pm »

Someone with your computers and network, or just someone on the 'net? Smiley

Post useful stuff like interface configurations and routing table on the machine trying to use the tunnel.

What model NAT appliance are you behind?

Have you tried putting your host in it's DMZ?
Logged
yang0914
Newbie
*
Posts: 4


View Profile
« Reply #6 on: April 29, 2012, 11:34:52 pm »

Someone on the same net.

The following is the output of 'ifconfig -a'.
Code:
he-ipv6   Link encap:IPv6-in-IPv4 
          inet6 addr: fe80::a00:20f/128 Scope:Link
          inet6 addr: 2001:470:23:5d8::2/64 Scope:Global
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:936 (936.0 b)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:452 errors:0 dropped:0 overruns:0 frame:0
          TX packets:452 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:63991 (62.4 KiB)  TX bytes:63991 (62.4 KiB)

p16p1     Link encap:Ethernet  HWaddr 08:00:27:29:AA:C9 
          inet addr:10.21.0.8  Bcast:10.21.0.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe29:aac9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:718 errors:0 dropped:0 overruns:0 frame:0
          TX packets:952 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:263530 (257.3 KiB)  TX bytes:122182 (119.3 KiB)

sit0      Link encap:IPv6-in-IPv4 
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Output of 'ip addr':
Code:
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: p16p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:29:aa:c9 brd ff:ff:ff:ff:ff:ff
    inet 10.21.0.8/24 brd 10.21.0.255 scope global p16p1
    inet6 fe80::a00:27ff:fe29:aac9/64 scope link
       valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
12: he-ipv6: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1480 qdisc noqueue state UNKNOWN
    link/sit 10.21.0.8 peer 74.82.46.6
    inet6 2001:470:23:5d8::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:20f/128 scope link
       valid_lft forever preferred_lft forever

And here is the 'tcpdump -i he-ipv6 ip6' record when I ping6 to the server side of the tunnel:
Code:
14:32:21.724235 IP6 yang0914-1-pt.tunnel.tserv22.tyo1.ipv6.he.net > yang0914-1.tunnel.tserv22.tyo1.ipv6.he.net: ICMP6, echo request, seq 1, length 64
14:32:22.730144 IP6 yang0914-1-pt.tunnel.tserv22.tyo1.ipv6.he.net > yang0914-1.tunnel.tserv22.tyo1.ipv6.he.net: ICMP6, echo request, seq 2, length 64
14:32:23.731075 IP6 yang0914-1-pt.tunnel.tserv22.tyo1.ipv6.he.net > yang0914-1.tunnel.tserv22.tyo1.ipv6.he.net: ICMP6, echo request, seq 3, length 64
14:32:24.731518 IP6 yang0914-1-pt.tunnel.tserv22.tyo1.ipv6.he.net > yang0914-1.tunnel.tserv22.tyo1.ipv6.he.net: ICMP6, echo request, seq 4, length 64
14:32:25.733127 IP6 yang0914-1-pt.tunnel.tserv22.tyo1.ipv6.he.net > yang0914-1.tunnel.tserv22.tyo1.ipv6.he.net: ICMP6, echo request, seq 5, length 64
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!