Forum - Tunnel up but can't ping PoP IPv6 :: SixXS - IPv6 Deployment & Tunnel Broker

Tunnel up but can't ping PoP IPv6

Shadow Hawkins on Sunday, 28 October 2012 09:38:31

I've setup aiccu and the tunnel is up an running. (at least it says so on the SixXS website, and I have some RX and TX packets on my sixxs interface) But it does not work. I can't ping the PoP end of the tunnel. Although I can ping everything else From my Router - ping PoP IPv4 - works - ping my IPv6 - works - ping PoP IPv6 - fails From the internet (http://centralops.net/co/Ping.aspx) - ping PoP IPv6 - works - ping my IPv6 - fails My interfaces look like this:

br0 Link encap:Ethernet HWaddr 00:25:9C:42:C0:83 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: 2a01:1e8:e100:834f:225:9cff:fe42:c083/64 Scope:Global inet6 addr: fe80::225:9cff:fe42:c083/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:556955 errors:0 dropped:0 overruns:0 frame:0 TX packets:875528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:184045942 (175.5 MiB) TX bytes:1117326483 (1.0 GiB) br0:0 Link encap:Ethernet HWaddr 00:25:9C:42:C0:83 inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0 Link encap:Ethernet HWaddr 00:25:9C:42:C0:83 inet6 addr: fe80::225:9cff:fe42:c083/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2425422 errors:12 dropped:0 overruns:0 frame:6 TX packets:1668587 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2532628074 (2.3 GiB) TX bytes:700001664 (667.5 MiB) Interrupt:4 Base address:0x2000 eth 1 and 2 like the 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 MULTICAST MTU:16436 Metric:1 RX packets:202 errors:0 dropped:0 overruns:0 frame:0 TX packets:202 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:27218 (26.5 KiB) TX bytes:27218 (26.5 KiB) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2a01:1e8:e100:34f::2/64 Scope:Global inet6 addr: fe80::a9fe:ff01/64 Scope:Link inet6 addr: fe80::a00:1/64 Scope:Link inet6 addr: fe80::c0a8:102/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:47 errors:0 dropped:0 overruns:0 frame:0 TX packets:1015 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6628 (6.4 KiB) TX bytes:139587 (136.3 KiB) vlan1 Link encap:Ethernet HWaddr 00:25:9C:42:C0:83 inet6 addr: fe80::225:9cff:fe42:c083/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1543283 errors:0 dropped:0 overruns:0 frame:0 TX packets:1215472 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1381930341 (1.2 GiB) TX bytes:521649412 (497.4 MiB) vlan2 Link encap:Ethernet HWaddr 00:25:9C:42:C0:84 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::225:9cff:fe42:c084/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:882003 errors:0 dropped:0 overruns:0 frame:0 TX packets:453107 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1106872891 (1.0 GiB) TX bytes:178351564 (170.0 MiB)

This is all on a my dd-wrt router. The router Itself is behind an other local (192.168.1.0/24) network which then is connected to the Internet. For my local network behind this router (10.0.0.0/24) I have setup a radvd which seems to work properly. Because I can ping the router from the clients via ipv6 and vice versa. So this seems to work. Any idea why I can't ping the PoP end of the tunnel from my router altough the tunnel seems to be up and running? I'm pretty new to IPv6, so I might have missed something really basic.

Tunnel up but can't ping PoP IPv6

Shadow Hawkins on Wednesday, 31 October 2012 12:17:55

If you're unable to ping the other side of the tunnel, the tunnel is not up. That is confirmed when the external host was unable to ping your side of the tunnel. What sort of tunnel are you using?

Tunnel up but can't ping PoP IPv6

Jeroen Massar SixXS Staff

on Wednesday, 31 October 2012 12:26:07

Looks like it is proto-41 based:

sixxs Link encap:IPv6-in-IPv4

And as he is behind multiple layers of NAT that are not under his control, that most very likely will not work. The PoP side can be pinged as he is apparently using heartbeat and the PoP will mark the tunnel up (and thus ping on it's side) because of that. The packets will never find their way to the NATted IPv4 endpoint though. Best solution: switch the tunnel type to AYIYA.

Please note Posting is only allowed when you are logged in.