Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Debian “wheezy” cannot ping6 out  (Read 6054 times)

Blitzsy

  • Newbie
  • *
  • Posts: 3
Debian “wheezy” cannot ping6 out
« on: September 24, 2012, 07:25:12 PM »

I cannot determine why my ipv6 tunnel is not working, Everything seems to register fine. I have few people help as well to debug it, but to no avail. I am using a linksys e2000 router and have tried enabling dmz. Anytime I try to ping6 out it just hangs with no response or failure. Any help explaining what I am doing wrong is appropriated


commands used:
Code: [Select]
modprobe ipv6
ip tunnel add he-ipv6 mode sit remote 209.51.181.2 local 68.43.181.209 ttl 255
ip link set he-ipv6 up
ip addr add 2001:470:1f10:104::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr

ifconfig:
Code: [Select]
eth0      Link encap:Ethernet  HWaddr b8:27:eb:ec:bb:f7
          inet addr:192.168.1.126  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:feec:bbf7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:803 errors:0 dropped:0 overruns:0 frame:0
          TX packets:986 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:75721 (73.9 KiB)  TX bytes:121596 (118.7 KiB)

he-ipv6   Link encap:IPv6-in-IPv4
          inet6 addr: fe80::c0a8:17e/128 Scope:Link
          inet6 addr: 2001:470:1f10:104::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:188 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:19552 (19.0 KiB)

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: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)

sit0      Link encap:IPv6-in-IPv4
          inet6 addr: ::192.168.1.126/96 Scope:Compat
          inet6 addr: ::127.0.0.1/96 Scope:Unknown
          UP RUNNING 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)

Client ipv6 ping
Code: [Select]
PING 2001:470:1f10:104::2(2001:470:1f10:104::2) 56 data bytes
64 bytes from 2001:470:1f10:104::2: icmp_seq=1 ttl=64 time=0.573 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=2 ttl=64 time=0.250 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=3 ttl=64 time=0.214 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=4 ttl=64 time=0.207 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=5 ttl=64 time=0.217 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=6 ttl=64 time=0.203 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=7 ttl=64 time=0.216 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=8 ttl=64 time=0.220 ms

Client ipv6 traceroute6
Code: [Select]
traceroute to 2001:470:1f10:104::2 (2001:470:1f10:104::2), 30 hops max, 80 byte packets
 1  Blitzsy-1-pt.tunnel.tserv9.chi1.ipv6.he.net (2001:470:1f10:104::2)  0.210 ms  0.129 ms  0.122 ms

ipv6.google.com traceroute6
Code: [Select]
traceroute to ipv6.google.com (2607:f8b0:400f:801::1011), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
« Last Edit: September 24, 2012, 07:28:01 PM by Blitzsy »
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2701
Re: Debian “wheezy” cannot ping6 out
« Reply #1 on: September 25, 2012, 04:51:59 AM »

You're behind a NAT....you'd need to replace your public IP address with the private IP address...
Logged

Blitzsy

  • Newbie
  • *
  • Posts: 3
Re: Debian “wheezy” cannot ping6 out
« Reply #2 on: September 25, 2012, 04:11:12 PM »

You're behind a NAT....you'd need to replace your public IP address with the private IP address...

I just noticed that after I posted, I am not sure if the linux route commands are working so I decided to try inserting it into my /etc/network/interfaces configuration. It doesn't seem to work though still cannot ping6 out.

/etc/network/interfaces config
Code: [Select]
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.126
gateway 192.168.1.1
netmask 255.255.255.0

auto he-ipv6
iface he-ipv6 inet6 v4tunnel
address 2001:470:1f10:104::2
netmask 64
endpoint 209.51.181.2
ttl 255
gateway 2001:470:1f10:104::1
local 192.168.1.126

ifconfig
Code: [Select]

eth0      Link encap:Ethernet  HWaddr b8:27:eb:ec:bb:f7
          inet addr:192.168.1.126  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:feec:bbf7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2260 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2236 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:273396 (266.9 KiB)  TX bytes:313228 (305.8 KiB)

he-ipv6   Link encap:IPv6-in-IPv4
          inet6 addr: fe80::c0a8:17e/128 Scope:Link
          inet6 addr: 2001:470:1f10:104::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:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:2688 (2.6 KiB)

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:3252 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3252 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:383448 (374.4 KiB)  TX bytes:383448 (374.4 KiB)

sit0      Link encap:IPv6-in-IPv4
          inet6 addr: ::192.168.1.126/96 Scope:Compat
          inet6 addr: ::127.0.0.1/96 Scope:Unknown
          UP RUNNING 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)

ping6 2001:470:1f10:104::1
Code: [Select]
PING 2001:470:1f10:104::1(2001:470:1f10:104::1) 56 data bytes
64 bytes from 2001:470:1f10:104::1: icmp_seq=1 ttl=64 time=71.2 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=2 ttl=64 time=54.4 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=3 ttl=64 time=50.0 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=4 ttl=64 time=50.7 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=5 ttl=64 time=66.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=6 ttl=64 time=47.7 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=7 ttl=64 time=47.5 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=8 ttl=64 time=61.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=9 ttl=64 time=47.6 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=10 ttl=64 time=50.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=11 ttl=64 time=43.3 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=12 ttl=64 time=44.2 ms
--- 2001:470:1f10:104::1 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11014ms
rtt min/avg/max/mdev = 43.349/53.056/71.254/8.562 ms

ping6 2001:470:1f10:104::2
Code: [Select]
PING 2001:470:1f10:104::2(2001:470:1f10:104::2) 56 data bytes
64 bytes from 2001:470:1f10:104::2: icmp_seq=1 ttl=64 time=0.221 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=2 ttl=64 time=0.222 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=3 ttl=64 time=0.218 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=4 ttl=64 time=0.214 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=5 ttl=64 time=0.230 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=6 ttl=64 time=0.216 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=7 ttl=64 time=0.204 ms
64 bytes from 2001:470:1f10:104::2: icmp_seq=8 ttl=64 time=0.201 ms
--- 2001:470:1f10:104::2 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7005ms
rtt min/avg/max/mdev = 0.201/0.215/0.230/0.020 ms

traceroute6 2001:470:1f10:104::1
Code: [Select]
traceroute to 2001:470:1f10:104::1 (2001:470:1f10:104::1), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

traceroute6 2001:470:1f10:104::2
Code: [Select]
traceroute to 2001:470:1f10:104::2 (2001:470:1f10:104::2), 30 hops max, 80 byte packets
 1  Blitzsy-1-pt.tunnel.tserv9.chi1.ipv6.he.net (2001:470:1f10:104::2)  0.209 ms  0.134 ms  0.123 ms

traceroute6 ipv6.google.com
Code: [Select]
traceroute to ipv6.google.com (2607:f8b0:400f:801::1012), 30 hops max, 80 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2701
Re: Debian “wheezy” cannot ping6 out
« Reply #3 on: September 25, 2012, 05:54:54 PM »

I guess I'm confused...you posted a good ping command from the HE side of the tunnel

Quote
ping6 2001:470:1f10:104::1

PING 2001:470:1f10:104::1(2001:470:1f10:104::1) 56 data bytes
64 bytes from 2001:470:1f10:104::1: icmp_seq=1 ttl=64 time=71.2 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=2 ttl=64 time=54.4 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=3 ttl=64 time=50.0 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=4 ttl=64 time=50.7 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=5 ttl=64 time=66.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=6 ttl=64 time=47.7 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=7 ttl=64 time=47.5 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=8 ttl=64 time=61.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=9 ttl=64 time=47.6 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=10 ttl=64 time=50.8 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=11 ttl=64 time=43.3 ms
64 bytes from 2001:470:1f10:104::1: icmp_seq=12 ttl=64 time=44.2 ms
--- 2001:470:1f10:104::1 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11014ms
rtt min/avg/max/mdev = 43.349/53.056/71.254/8.562 ms

Logged

Blitzsy

  • Newbie
  • *
  • Posts: 3
Re: Debian “wheezy” cannot ping6 out
« Reply #4 on: September 25, 2012, 06:47:01 PM »

When I try to ping to ipv6.google.com it just hangs with no response, I am going to check logs for relevance.

edit: found these in the log files

Code: [Select]
/var/log/debug
    Sep 25 18:53:35 raspberrypi kernel: [   27.897421] eth0: no IPv6 routers present
   
/var/log/daemon.log
    Sep 25 18:53:30 raspberrypi dbus[1356]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
    Sep 25 18:53:31 raspberrypi dbus[1356]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
    Sep 25 18:53:31 raspberrypi ntpd[1507]: ntpd 4.2.6p5@1.2349-o Sat May 12 10:38:11 UTC 2012 (1)
    Sep 25 18:53:31 raspberrypi ntpd[1509]: proto: precision = 2.000 usec
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Sep 25 18:53:31 raspberrypi polkitd[1497]: started daemon version 0.105 using authority implementation `local' version `0.105'
    Sep 25 18:53:31 raspberrypi dbus[1356]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen and drop on 1 v6wildcard :: UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 3 eth0 192.168.1.126 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 4 sit0 ::192.168.1.126 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 5 he-ipv6 fe80::c0a8:17e UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 6 sit0 ::127.0.0.1 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 7 eth0 fe80::ba27:ebff:feec:bbf7 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 8 he-ipv6 2001:470:1f10:104::2 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: Listen normally on 9 lo ::1 UDP 123
    Sep 25 18:53:31 raspberrypi ntpd[1509]: peers refreshed

/var/log/messages
    Sep 25 18:53:28 raspberrypi kernel: [   15.726332] IPv6 over IPv4 tunneling driver
    Sep 25 18:53:28 raspberrypi kernel: [   16.978022] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    Sep 25 18:53:28 raspberrypi kernel: [   17.001034] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

/var/log/kern.log
    Sep 25 18:53:28 raspberrypi kernel: [   10.467156] NET: Registered protocol family 10
    Sep 25 18:53:28 raspberrypi kernel: [   15.362502] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Sep 25 18:53:28 raspberrypi kernel: [   15.726332] IPv6 over IPv4 tunneling driver
    Sep 25 18:53:28 raspberrypi kernel: [   16.978022] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    Sep 25 18:53:28 raspberrypi kernel: [   17.001034] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Sep 25 18:53:30 raspberrypi kernel: [   21.991740] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SS
    Sep 25 18:53:35 raspberrypi kernel: [   27.897421] eth0: no IPv6 routers present
« Last Edit: September 25, 2012, 08:14:51 PM by Blitzsy »
Logged