Forum - IPv6 tunnel died suddenly and can't get it to work anymore :: SixXS

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 13:34:20

I can only ping myself, the pop i can't ping anymore which says destination unreachable, I probably did something wrong, and can't figure it out... i figure there's something wrong with the routes, but my skills of routing is still very minimal, anyone that has any idea? sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:770:100:56::2/64 Scope:Global inet6 addr: fe80::3ecd:6fce/64 Scope:Link inet6 addr: fe80::c0a8:301/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:64 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8193 (8.0 Kb) [root@queen alien]# ping6 2001:770:100:56::1 PING 2001:770:100:56::1(2001:770:100:56::1) 56 data bytes From ::1 icmp_seq=2 Destination unreachable: Address unreachable From ::1 icmp_seq=3 Destination unreachable: Address unreachable From ::1 icmp_seq=4 Destination unreachable: Address unreachable From ::1 icmp_seq=5 Destination unreachable: Address unreachable notice the From ::1 ??? something seems wrong here please help me, i've just noticed it, and i'm already 11 hours down... :( thanks in advance

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 13:44:42

I think you can always user disable your tunnel, which doesn't cost credit. But I'm not sure. What does your "ip -6 tun" and "ip -6 route" output say? Greets Thorsten

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 14:23:25

when restarting the AICCU thing, i noticed this in my /var/log/messages ... do you have any idea what it is? Nov 6 14:11:04 queen kernel: Disabled Privacy Extensions on device cb71bc00(sixxs)

IPv6 tunnel died suddenly and can't get it to work anymore

Jeroen Massar SixXS Staff

on Saturday, 06 November 2004 14:37:07

That simply means you have a kernel which has RFC3041 (Privacy extensions) support compiled in.

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 14:08:36

i had tried those commands you see in the forum alot, without success... but now, the via doesn't look too good... [root@queen alien]# ip -6 tun sit0: ipv6/ip remote any local any ttl 64 nopmtudisc gre0: gre/ip remote any local any ttl inherit nopmtudisc sixxs: ipv6/ip remote 193.1.31.74 local 62.205.111.206 ttl 64 [root@queen alien]# ip -6 route 2001:770:100:56::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1220 fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1220 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1220 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1220 default via 2001:770:100:56::1 dev sixxs metric 1024 mtu 1280 advmss 1220 unreachable default dev lo proto none metric -1 error -101 advmss 1220

IPv6 tunnel died suddenly and can't get it to work anymore

Jeroen Massar SixXS Staff

on Saturday, 06 November 2004 14:26:46

2001:770:100:56::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220

This makes sure that the /64 is routed correctly onto the tunnel and that you can actually reach the other endpoint

default dev eth0 proto kernel metric 256 mtu 1500 advmss 1220

default dev eth1 proto kernel metric 256 mtu 1500 advmss 1220

These are bogus and should be removed. Inserted by the kernel because it didn't find a default route, I still don't get why they put this code into Linux...

default via 2001:770:100:56::1 dev sixxs metric 1024 mtu 1280 advmss 1220

This makes any packet go to the other side of the tunnel. But as the metric of the last is the highest the eth0/eth1's will be tried in turn and no packet will go out unless it is in the first /64. Next to that, you might want to run a heartbeat or aiccu client...

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 14:54:02

i run aiccu remove the default dev eth0 and eth1 things... i am wondering about that unreachable default thing below...

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 15:47:26

settings: [root@queen alien]# cat /etc/aiccu.conf # AICCU Configuration # Login information username MV31-6BONE password xxxxxxx # Interface names to use ipv4_interface eth1 ipv6_interface sixxs # The tunnel_id to use # (only required when there are multiple tunnels in the list) tunnel_id T5247 # Be verbose? verbose false # Daemonize? daemonize true # Automatic? automatic true [root@queen alien]# ifconfig eth0 Link encap:Ethernet HWaddr 00:11:2F:0B:39:9F inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0 inet6 addr: fe80::211:2fff:fe0b:399f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:55778 errors:0 dropped:0 overruns:0 frame:0 TX packets:33 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4920353 (4.6 Mb) TX bytes:5765 (5.6 Kb) Interrupt:17 Memory:fd900000-0 eth1 Link encap:Ethernet HWaddr 00:01:02:0F:C8:88 inet addr:62.205.111.206 Bcast:255.255.255.255 Mask:255.255.252.0 inet6 addr: fe80::201:2ff:fe0f:c888/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17611722 errors:0 dropped:0 overruns:0 frame:0 TX packets:312730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1114838818 (1063.1 Mb) TX bytes:31311620 (29.8 Mb) Interrupt:19 Base address:0xb400 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:202774 errors:0 dropped:0 overruns:0 frame:0 TX packets:202774 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:921397344 (878.7 Mb) TX bytes:921397344 (878.7 Mb) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:770:100:56::2/64 Scope:Global inet6 addr: fe80::3ecd:6fce/64 Scope:Link inet6 addr: fe80::c0a8:301/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:620 (620.0 b)

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 15:54:32

You should change your password! You just posted it. Another thingy: is your clock in sync?

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 21:48:21

holy crap, i've been really stupid... I've changed it already... ok, I do run ntpd, since a long time now... the only thing is that i've changed IP recently, but as i'm on heartbeat, it shouldn't matter... plus i've restarted it tons of times... does the timezone of this check if it's Daylight saving time? I'm in GMT+1 and the time has changed hour recently too... I'm using mdk 10.0 and that's just the link detection program from mandrake, but as it says, there's nothing configured like that... I guess, it all seems quite fine, i have no idea why it wouldn't work anymore... at this point i do not yet have a firewall on ip6, so that can't be it either, plus protocol 41 is passed too ... how do i make sure my timezone is absolutely correct with respect to DST and how do i make sure that my ntp is absolutely correct too? the POP is reachable in IPv4, the POP is reachable in IPv6 from another PC, a buddy from mine has confirmed that...

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Sunday, 07 November 2004 00:31:54

Hm, I give up now :? Perhaps you should contact sixxs staff. Be sure to include all the details mentioned on the contacts page that could help finding the problem. Perhaps sixxs can find something on the POP side.. Greets Thorsten

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Sunday, 07 November 2004 10:03:30

I've tried to contact them... haven't received a reply yet, i hope they reply soon, since my credits are going down

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 15:02:44

is this normal? -> privacy extensions? [root@queen alien]# ip tun del sixxs [root@queen alien]# /etc/init.d/aiccu start Starting AICCU (Automatic IPv6 Connectivity Configuration Utilit[ OK ]ces: [root@queen alien]# tail /var/log/messages Nov 6 14:59:27 queen aiccu: POP Id : iedub01 Nov 6 14:59:27 queen aiccu: IPv6 Local : 2001:770:100:56::2/64 Nov 6 14:59:27 queen aiccu: IPv6 Remote : 2001:770:100:56::1/64 Nov 6 14:59:27 queen aiccu: Tunnel Type : 6in4-heartbeat Nov 6 14:59:27 queen aiccu: Adminstate : enabled Nov 6 14:59:27 queen aiccu: Userstate : enabled Nov 6 14:59:27 queen aiccu: aiccu startup succeeded Nov 6 14:59:27 queen net.agent[8198]: add event not handled Nov 6 14:59:27 queen kernel: Disabled Privacy Extensions on device c1a09000(sixxs) Nov 6 14:59:27 queen aiccu: Beat()

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Saturday, 06 November 2004 16:03:00

As Jeroen stated above, the privacy extensions line is perfectly normal. I don't know what the net.agent line means. What is you OS, and what kernel version do you use?

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Sunday, 07 November 2004 01:41:48

tcpdump: [root@queen alien]# tcpdump -vv -i sixxs tcpdump: WARNING: sixxs: no IPv4 address assigned tcpdump: listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes 01:34:32.528198 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 1 (len 64, hlim 64) 01:34:33.527649 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 2 (len 64, hlim 64) 01:34:34.527471 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 3 (len 64, hlim 64) 01:34:34.592068 2001:770:100:56::2.32771 > bfib.ipng.nl.domain: 6564% [1au][|domain] (len 108, hlim 64) 01:34:35.527293 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 4 (len 64, hlim 64) 01:34:36.527113 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 5 (len 64, hlim 64) 01:34:36.593214 2001:770:100:56::2.32771 > 2001:838:1:1:210:dcff:fe20:7c7c.domain: 3282% [1au][|domain] (len 108, hlim 64) 01:34:37.526937 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 6 (len 64, hlim 64) 01:34:38.526757 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 7 (len 64, hlim 64) 01:34:38.594846 2001:770:100:56::2.32771 > exodus.bh.access.hea.net.domain: 1641% [1au][|domain] (len 108, hlim 64) 01:34:39.526604 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 8 (len 64, hlim 64) 01:34:40.526423 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 9 (len 64, hlim 64) 01:34:41.526250 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 10 (len 64, hlim 64) 01:34:42.526171 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 11 (len 64, hlim 64) 01:34:42.597185 2001:770:100:56::2.32771 > bfib.ipng.nl.domain: 60242[|domain] (len 97, hlim 64) 01:34:43.525894 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 12 (len 64, hlim 64) 01:34:44.525720 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 13 (len 64, hlim 64) 01:34:44.591644 2001:770:100:56::2.32771 > bfib.ipng.nl.domain: 47606% [1au][|domain] (len 108, hlim 64) 01:34:44.598662 2001:770:100:56::2.32771 > 2001:838:1:1:210:dcff:fe20:7c7c.domain: 56571[|domain] (len 97, hlim 64) 01:34:45.525510 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 14 (len 64, hlim 64) 01:34:46.525325 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 15 (len 64, hlim 64) 01:34:46.593405 2001:770:100:56::2.32771 > 2001:838:1:1:210:dcff:fe20:7c7c.domain: 11522% [1au][|domain] (len 108, hlim 64) 01:34:46.600304 2001:770:100:56::2.32771 > exodus.bh.access.hea.net.domain: 38529[|domain] (len 97, hlim 64) 01:34:47.525269 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 16 (len 64, hlim 64) 01:34:48.525093 2001:770:100:56::2 > 2001:770:100:56::1: icmp6: echo request seq 17 (len 64, hlim 64) 01:34:48.595050 2001:770:100:56::2.32771 > exodus.bh.access.hea.net.domain: 15843% [1au][|domain] (len 108, hlim 64) [root@queen alien]# tcpdump -v -i eth1 icmp tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 01:30:58.622411 IP (tos 0xc0, ttl 51, id 51896, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:30:59.623871 IP (tos 0xc0, ttl 51, id 51897, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:31:00.622451 IP (tos 0xc0, ttl 51, id 51898, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:31:01.622614 IP (tos 0xc0, ttl 51, id 51899, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:31:02.621471 IP (tos 0xc0, ttl 51, id 51900, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:31:03.621623 IP (tos 0xc0, ttl 51, id 51901, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable 01:31:04.621843 IP (tos 0xc0, ttl 51, id 51902, offset 0, flags [none], length: 152) sixxs-tb.bh.access.hea.net > cable-62-205-111-206.upc.chello.be: icmp 132: sixxs-tb.bh.access.hea.net protocol 41 unreachable I have stopped my firewall completely!... I'm totally at a loss... and the 24hours are almost over

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Monday, 08 November 2004 06:49:27

I might have the same problem (started on Friday afternoon, according to the tunnel latency/packet/loss logs), at least I have same symptoms here. I also have a heartbeat tunnel at HEAnet, and didn't change my config (and the router's uptime is over a week). It seems it just suddenly broke ... I've sent a mail to info@sixxs.net with more details about my config (this thread is already big enough), but it looks like it could be a problem on HEAnet's side ... I'll keep you updated ...

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Monday, 08 November 2004 10:19:45

well, i just got back from class and it seems that i has been solved in the last hour! nice, and all this time i thought it was me, since i've just new at this, I'm happy!

IPv6 tunnel died suddenly and can't get it to work anymore

Shadow Hawkins on Monday, 08 November 2004 11:42:33

Yes, they fixed it here aswell (just about 30mins ago).

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