|
Ticket ID: SIXXS #2759721 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
Routing issues?
![[de]](/s/countries/de.gif) Shadow Hawkins on Saturday, 09 October 2010 01:14:03
Hello all,
i'd like to ask if there are any routing-problems at dedus01?
since some minutes/hours, IPv6 through dedus01 isn't possible at all.
i have restarted aiccu, but there seems to be a 'black hole' to the next-hop:
Netfilter-settings on my router can't be the problem.
/code
==== Debug output =====
jupiter:~# /etc/init.d/aiccu restart
Restarting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)...Tunnel Information for T22615:
POP Id : dedus01
IPv6 Local : 2a01:198:200:5b0::2/64
IPv6 Remote : 2a01:198:200:5b0::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
.
jupiter:~#
jupiter:~# tcpdump -v -i sixxs -n &
[1] 9125
jupiter:~# tcpdump: WARNING: arptype 65534 not supported by libpcap - falling back to cooked socket
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: listening on sixxs, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
jupiter:~# ping6 -n sixxs.net
PING sixxs.net(2001:1af8:1:f006::6) 56 data bytes
01:10:43.330396 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a01:198:200:5b0::2 > 2001:1af8:1:f006::6: ICMP6, echo request, length 64, seq 1
01:10:44.343986 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a01:198:200:5b0::2 > 2001:1af8:1:f006::6: ICMP6, echo request, length 64, seq 2
01:10:45.343999 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a01:198:200:5b0::2 > 2001:1af8:1:f006::6: ICMP6, echo request, length 64, seq 3
01:10:46.344003 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2a01:198:200:5b0::2 > 2001:1af8:1:f006::6: ICMP6, echo request, length 64, seq 4
^C
--- sixxs.net ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3013ms
jupiter:~#
====================/code
every help would be appreciated !
greetings
roland
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 01:26:19
I'm also having issues with my tunnel/subnet going through dedus01
Tunnel up, but udp port 5072 unreachable
Shadow Hawkins on Saturday, 09 October 2010 02:54:02
My tunnel to dedus01 seems to be up according to aiccu, but no ipv6 packets go through it. Here some details, which may help to solve the problem:
1. Output from 'aiccu test'
Tunnel Information for T18898:
POP Id : dedus01
IPv6 Local : 2a01:198:200:2f4::2/64
IPv6 Remote : 2a01:198:200:2f4::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
2. I can not ping mytunnel endpoint 2a01:198:200:2f4::1
3. I am using the aiccu-package provided by debian lenny:
ii aiccu 20070115-9 SixXS Automatic IPv6 Connectivity Client Utility
4. With tcpdump I can see that udp port 5072 of the tunnel is unreachable:
02:25:26.321139 IP 91.184.37.98 > 192.168.42.65: ICMP 91.184.37.98 udp port 5072 unreachable, length 184
5. Here is the output of IPv4 and IPv6 traceroute to dedus01:
traceroute6 -n dedus01.sixxs.net
traceroute to dedus01.sixxs.net (2a01:198:200::2), 30 hops max, 40 byte packets
traceroute -n dedus01.sixxs.net
traceroute to dedus01.sixxs.net (91.184.37.98), 30 hops max, 40 byte packets
1 192.168.42.6 0.272 ms 0.108 ms 0.131 ms
2 192.168.42.1 0.240 ms 0.155 ms 0.178 ms
3 217.0.118.86 39.528 ms 41.535 ms 45.172 ms
4 87.186.243.154 45.324 ms 47.404 ms 50.300 ms
5 62.154.16.161 53.404 ms 55.034 ms 57.401 ms
6 80.156.161.118 59.034 ms 62.156.138.94 60.990 ms 80.156.161.118 62.653 ms
7 80.91.251.158 64.774 ms 80.91.251.162 66.405 ms 80.91.246.52 68.774 ms
8 80.91.251.194 74.385 ms 80.91.247.13 46.071 ms 45.994 ms
9 213.248.68.130 46.400 ms 48.083 ms 48.205 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * 91.184.37.98 46.790 ms *
Tunnel up, but udp port 5072 unreachable
Shadow Hawkins on Saturday, 09 October 2010 10:05:05
Hello!
I have the same problems. I also used dedus01 with AYIYA.
Information from SixXS:
Tunnel Information for T17767
PoP Namededus01
PoP LocationDuesseldorf, Germany
PoP IPv4 91.184.37.98
TIC Servertic.sixxs.net (default in AICCU)
Your IPv4AYIYA, currently momentarily unavailable
PoP IPv6 2a01:198:200:250::1
Your IPv62a01:198:200:250::2
PoP dedus91 is available over IPv4. Ping to 91.184.37.98 still works.
If i send ping packets to 2a01:198:200:250::1 then i get an icmpv4 reply from 91.184.37.98.
ICMPv4 Message Type 3, Code 3 -> Destination unreachable (Port unreachable).
It seems the AYIYA protocol is down on dedus01.
Greets Lars
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 10:20:43
Hello
I'm also have problems with my Aiccu Tunnel endpoint dedus01
i don't can ping/trace my tunnelendpoint
Tunnel Information for T21430
Tunnel NameTunnel to Home C1812-tu6
PoP Namededus01
PoP LocationDuesseldorf, Germany
PoP IPv491.184.37.98
TIC Servertic.sixxs.net (default in AICCU)
Your LocationDortmund, Germany
Your IPv4Heartbeat, currently momentarily unavailable
IPv6 Prefix2a01:198:200:4e8::1/64
PoP IPv62a01:198:200:4e8::1
Your IPv62a01:198:200:4e8::2
Created2009-05-18 14:16:24 CEST
Last Alive2010-10-08 23:44:43 CEST
rcedler01#ping 2a01:198:200:4e8::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2A01:198:200:4E8::1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
rcedler01#traceroute 2A01:198:200:4E8::1
Type escape sequence to abort.
Tracing the route to gw-1257.dus-01.de.sixxs.net (2A01:198:200:4E8::1)
1 * * *
2 * * *
3 * * *
4 * * *
rcedler01#traceroute 91.184.37.98
Type escape sequence to abort.
Tracing the route to dedus01.sixxs.net (91.184.37.98)
1 217.0.119.51 20 msec 20 msec 20 msec
2 87.186.232.42 24 msec 24 msec 20 msec
3 217.239.37.150 20 msec 20 msec
d-ec1-i.D.DE.NET.DTAG.DE (62.154.43.134) 24 msec
4 217.243.219.136 24 msec 24 msec 24 msec
5 dedus01.sixxs.net (91.184.37.98) 28 msec 24 msec 24 msec
Best Regards
Michael Edler
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 10:21:24
Confirming for T25477:
nexthop 2a01:198:200:7ef::1 does not answer icmp,
udp4 packets to POP result in "port 3740 unreachable".
Tunnel information page graphs seem to have the tunnel working till around midnight.
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 10:27:06
confirming problems with aiccu
Starting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)...Tunnel Information for T19440:
POP Id : dedus01
IPv6 Local : 2a01:198:200:33f::2/64
IPv6 Remote : 2a01:198:200:33f::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
seems up but no v6 answers from peer
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 10:51:45
Hi.
Same problem for my AYIYA endpoint. The problem occured between 00:00 and 00:15. I ping my IPv6 enabled webserver every 15 minutes. On 00:00 I got echo replies but since 00:15 there are no more replies. AICCU does not give any error messages at all and my routing and firewall are set up properly.
I guess that this outage kept me from getting 5 ISK last night. I got the last ISK on September 25th at 01:16 and last night another two weeks were over and I had my tunnel up 24/7. No single hour with ping timeouts. Do I have to wait another two weeks for "the money"?
Kind regards
Kay Zumbusch
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 11:12:31
Ditto here, Aiccu works, sets up the tunnel, but the POP responds with ICMP unreachable to the UDP Encapsulated IPv6 Packets.
11:09:56.135572 IP 192.168.50.24.36870 > 91.184.37.98.5072: UDP, length 148
11:09:56.170883 IP 91.184.37.98 > 192.168.50.24: ICMP 91.184.37.98 udp port 5072 unreachable, length 184
11:09:57.150115 IP 192.168.50.24.36870 > 91.184.37.98.5072: UDP, length 148
11:09:57.185490 IP 91.184.37.98 > 192.168.50.24: ICMP 91.184.37.98 udp port 5072 unreachable, length 184
Tunnel Information for T21986:
POP Id : dedus01
IPv6 Local : 2a01:198:200:52b::2/64
IPv6 Remote : 2a01:198:200:52b::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
.
cheerio
Steve
Routing issues?
Shadow Hawkins on Saturday, 09 October 2010 11:13:21
Hello,
I can confirm this problem for my Heartbeat-tunnel T16014 - as the above messages only mentioned AYIYA-style tunnels, I thought, I might add this information.
aiccu test fails in Step 6, when testing ping6 to the remote tunnel endpoint (as I figured out myself earlier *g*).
Interestingly, the static tunnel to/from our root-server which is also terminated on dedus01 works flawlessly (tried ping6 sixxs.net and www.heise.de); I can even ping the "remote" IPv6-address of my T16014 from there.
Wireshark-Capture of the "Destination unreachable (port unreachable)"-return packets:
0000 00 00 02 00 00 00 00 00 00 00 00 00 00 00 08 00 ........ ........
0010 45 00 00 98 e7 8a 00 00 39 01 92 2f 5b b8 25 62 E....... 9../[.%b
0020 54 a3 31 ee 03 03 62 f6 00 00 00 00 45 00 00 7c T.1...b. ....E..|
0030 00 00 40 00 39 29 39 ae 54 a3 31 ee 5b b8 25 62 ..@.9)9. T.1.[.%b
0040 60 00 00 00 00 40 3a 40 2a 01 01 98 02 00 01 34 `....@:@ *......4
0050 00 00 00 00 00 00 00 02 2a 01 01 98 02 00 01 34 ........ *......4
0060 00 00 00 00 00 00 00 01 80 00 12 55 0c 2a 00 06 ........ ...U.*..
0070 98 2b b0 4c cb e7 04 00 08 09 0a 0b 0c 0d 0e 0f .+.L.... ........
0080 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f ........ ........
0090 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f !"#$%&' ()*+,-./
00a0 30 31 32 33 34 35 36 37 01234567
I'll hve to shutdown aiccu for now until this is resolved, because I'll be gone for the weekend and I want my email to keep arriving, thus force usage of IPv4.
Matthias Merz
dedus01 down?
Shadow Hawkins on Saturday, 09 October 2010 11:14:31
Proto 41 and heartbeat to dedus01 result in ICMP unreachable.
tcpdump log:
IP 80.144.102.138.37934 > 91.184.37.98.3740: UDP, length 87
IP 91.184.37.98 > 80.144.102.138: ICMP 91.184.37.98 udp port 3740 unreachable, length 123
IP 80.144.102.138 > 91.184.37.98: IP6 2a01:198:200:99f::2 > 2a01:198:200:99f::1: ICMP6, echo request, seq 1, length 64
IP 91.184.37.98 > 80.144.102.138: ICMP 91.184.37.98 protocol 41 port 0 unreachable, length 132
IP 80.144.102.138 > 91.184.37.98: IP6 2a01:198:200:99f::2 > 2a01:198:200:99f::1: ICMP6, echo request, seq 2, length 64
IP 91.184.37.98 > 80.144.102.138: ICMP 91.184.37.98 protocol 41 port 0 unreachable, length 132
IP 80.144.102.138 > 91.184.37.98: IP6 2a01:198:200:99f::2 > 2a01:198:200:99f::1: ICMP6, echo request, seq 3, length 64
IP 91.184.37.98 > 80.144.102.138: ICMP 91.184.37.98 protocol 41 port 0 unreachable, length 132
Routing issues?
Shadow Hawkins  on Saturday, 09 October 2010 12:20:48
Hi,
thank you for reporting this. The routing itself seems to have been okay at all times, but the tunnel-software seems to have caused problems. We'll look into that more closely with SixXS-staff.
At the moment connectivity is back again.
Kind regards,
Stefan Neufeind, SpeedPartner GmbH (dedus01)
State change: resolved
 Shadow Hawkins on Saturday, 09 October 2010 12:21:03
The state of this ticket has been changed to resolved
Same problem again
Shadow Hawkins on Saturday, 23 October 2010 21:20:29
Hello,
it seems, that there are the same problems with dedus01 again. The symptoms are the same as described in my posting below.
thanks for help && greetings,
Andreas
Same problem again
Shadow Hawkins on Saturday, 23 October 2010 21:29:46
i can confirm this, too.
Same problem again
Shadow Hawkins on Saturday, 23 October 2010 22:16:09
Also having problems to reach the internet throu this pop
Same problem again
Shadow Hawkins on Sunday, 24 October 2010 00:08:20
Yup, same problem again. I can reach my tunnel endpoint from outside, but none of the networks behind it.
Tunnel to dedus01 down
Shadow Hawkins on Saturday, 30 October 2010 17:23:06
My tunnel to dedus01 is down again since 15:30 CEST. The detailed symptoms are described in my other posting:
- udp port 5072 of PoP unreachable
- PoP pingable
- after a restart aiccu says, the tunnel is up and working
Tunnel to dedus01 down
Shadow Hawkins on Saturday, 30 October 2010 18:11:28
Tunnel is down again.
Same symptomes as described earlier in this ticket.
|
Posting is only allowed when you are