|
Ticket ID: SIXXS #7557106 Ticket Status: User PoP: nlams05 - SURFnet (Amsterdam)
tunnel endpoint not reachable
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Sunday, 05 August 2012 16:09:07
For some days now my ipv6 tunnel stops working, after some time and/or restarts it suddenly starts working again.
tunnel_id T15235
# aiccu version
AICCU 2007.01.15-console-linux by Jeroen Massar
# uname -a
Linux ds9 2.6.32-39-server #86-Ubuntu SMP Mon Feb 13 23:15:11 UTC 2012 x86_64 GNU/Linux
# ifconfig
eth1 Link encap:Ethernet HWaddr 00:13:21:c6:0d:b0
inet addr:192.168.0.250 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2001:610:600:8489::1/64 Scope:Global
inet6 addr: fe80::213:21ff:fec6:db0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5302157 errors:0 dropped:0 overruns:0 frame:0
TX packets:3145911 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6735768832 (6.7 GB) TX bytes:656606486 (656.6 MB)
Interrupt:18
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:610:600:489::2/64 Scope:Global
inet6 addr: fe80::410:600:489:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:367935 errors:0 dropped:0 overruns:0 frame:0
TX packets:216255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:397198076 (397.1 MB) TX bytes:22743003 (22.7 MB)
# ip -6 route
2001:610:600:489::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
2001:610:600:8489::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:610:600:489::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
ping ipv4 pop endpoint.
# ping 192.87.102.107
PING 192.87.102.107 (192.87.102.107) 56(84) bytes of data.
64 bytes from 192.87.102.107: icmp_seq=1 ttl=57 time=9.69 ms
64 bytes from 192.87.102.107: icmp_seq=2 ttl=57 time=12.1 ms
64 bytes from 192.87.102.107: icmp_seq=3 ttl=57 time=11.0 ms
# tcpdump -n -i eth1 proto 1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
16:06:18.839567 IP 192.168.0.250 > 192.87.102.107: ICMP echo request, id 2406, seq 1, length 64
16:06:18.849226 IP 192.87.102.107 > 192.168.0.250: ICMP echo reply, id 2406, seq 1, length 64
16:06:19.841436 IP 192.168.0.250 > 192.87.102.107: ICMP echo request, id 2406, seq 2, length 64
16:06:19.853552 IP 192.87.102.107 > 192.168.0.250: ICMP echo reply, id 2406, seq 2, length 64
16:06:20.842752 IP 192.168.0.250 > 192.87.102.107: ICMP echo request, id 2406, seq 3, length 64
16:06:20.853785 IP 192.87.102.107 > 192.168.0.250: ICMP echo reply, id 2406, seq 3, length 64
can't ping ipv6 pop endpoint.
# ping6 2001:610:600:489::1
PING 2001:610:600:489::1(2001:610:600:489::1) 56 data bytes
~# tcpdump -n -i sixxs proto 41 or proto 58
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 96 bytes
16:01:12.078761 IP6 2001:610:600:489::2 > 2001:610:600:489::1: ICMP6, echo request, seq 31, length 64
16:01:13.084193 IP6 2001:610:600:489::2 > 2001:610:600:489::1: ICMP6, echo request, seq 32, length 64
16:01:14.085394 IP6 2001:610:600:489::2 > 2001:610:600:489::1: ICMP6, echo request, seq 33, length 64
16:01:15.085367 IP6 2001:610:600:489::2 > 2001:610:600:489::1: ICMP6, echo request, seq 34, length 64
no echo replies !
What can be wrong ???
State change: user
The state of this ticket has been changed to user
tunnel endpoint not reachable
What can be wrong ???
Lots of things.
But it seems that you have a problem with packet corruption of sorts or have configured the wrong password as the PoP is reporting:
Hash Fail : 1884168, last: :: 2012-08-05 19:23:19 (1344194599; 0 days 00:00:21 ago)
As such, check that you are not running multiple aiccu's and check that you have actually configured things correctly next to checking logs for any hints of problems.
tunnel endpoint not reachable
Shadow Hawkins on Sunday, 05 August 2012 22:07:14
I see this kind of errors:
ICMPv6 checksum failed [2001:0610:0600:0489:0000:0000:0000:0001 > 2001:0610:0600:0489:0000:0000:0000:0002]
I'm running one aiccu for sure, the password is configured in the aiccu.conf, so this can't be wrong.
The tunnel worked fine, only the last days I have connection problems.
tunnel endpoint not reachable
Something is corrupting your packets which causes the hash to fail and thus those packets to be dropped, that is the whole point of having that verification there.
tunnel endpoint not reachable
Shadow Hawkins on Monday, 06 August 2012 21:24:33
I see similar problems here: http://www.sixxs.net/tickets/?msg=tickets-5998238
There no solution yet for this problem yet ?
tunnel endpoint not reachable
I see similar problems here
What is the 'similar' problem? Your endpoint is generating broken packets.
tunnel endpoint not reachable
Shadow Hawkins on Wednesday, 08 August 2012 21:12:07
Similar is the 'ICMPv6 checksum failed' error.
But maybe I found the solution. The power supply of my Ubee cable modem died yesterday. I was still working for the internet connection but the phone part didn't work any longer, also all signal leds on the modem didn't work.
I replaced the power supply. This might explain the corruptions...
tunnel endpoint not reachable
Shadow Hawkins on Sunday, 12 August 2012 14:21:43
No more problems encountered so far.
I still get one or two 'ICMPv6 checksum failed' errors a day. But it looks like it doesn't interrupt anything.
|
![[ch]](/s/countries/ch.gif)
on Sunday, 05 August 2012 21:22:35
Posting is only allowed when you are