|
Ticket ID: SIXXS #6723082 Ticket Status: Resolved PoP: nlede01 - BIT BV (Ede)
shows as up, but does not respond to IPv4 ping
![[lu]](/s/countries/lu.gif) Shadow Hawkins on Wednesday, 28 March 2012 08:04:50
nlede01 is shown as "Status: up" on https://www.sixxs.net/pops/bit/, but it does not respond to IPv4 pings from two different ISPs, here's from one:
$ ping -c 10 nlede01.sixxs.net
PING nlede01.sixxs.net (193.109.122.244) 56(84) bytes of data.
From 1414.ae3.xr4.1d12.xs4all.net (194.109.7.129) icmp_seq=2 Destination Net Unreachable
It also fails to route tunnel traffic.
Obviously, aiccu test fails the second test.
$ traceroute nlede01.sixxs.net
traceroute to nlede01.sixxs.net (193.109.122.244), 30 hops max, 60 byte packets
1 tsomet.home.mamane.lu (10.0.2.10) 0.176 ms 0.135 ms 0.122 ms
2 modemadsl.home.mamane.lu (10.0.1.138) 67.855 ms 66.688 ms 65.375 ms
3 lo1.dr4.d12.xs4all.net (194.109.5.227) 31.538 ms 33.285 ms 34.877 ms
4 1414.ae3.xr4.1d12.xs4all.net (194.109.7.129) 38.729 ms !N
$ traceroute nlede01.sixxs.net
traceroute to nlede01.sixxs.net (193.109.122.244), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 16.252 ms 15.784 ms 15.281 ms
2 ip-87-240-218-1.dyn.luxdsl.pt.lu (87.240.218.1) 24.563 ms 26.565 ms 28.142 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 *
From another IPv6 connection:
$ traceroute6 nlede01.sixxs.net
traceroute to nlede01.sixxs.net (2001:7b8:3:4f:202:b3ff:fe46:bec) from 2001:888:19f0:2:2e0:81ff:fe54:abf9, port 33434, from port 44453, 30 hops max, 60 bytes packets
1 tsomet.mamane.lu (2001:888:19f0:2::a) 0.129 ms 0.101 ms 0.143 ms
2 xs4all2544.ipv6.xs4all.nl (2001:888:10:9f0::1) 22.949 ms 22.530 ms 23.325 ms
3 125.ae0.xr4.1d12.xs4all.net (2001:888:0:3::1) 25.715 ms 24.547 ms 20.946 ms
4 2001:888:1:4006::1 (2001:888:1:4006::1) 25.037 ms 22.115 ms 21.392 ms
5 amsix-501.xe-0-0-0.jun1.bit-1.network.bit.nl (2001:7f8:1::a501:2859:2) 23.816 ms 24.364 ms 22.062 ms
6 nlede01.sixxs.net (2001:7b8:3:4f:202:b3ff:fe46:bec) 25.128 ms 23.482 ms 21.627 ms
shows as up, but does not respond to IPv4 ping
Shadow Hawkins on Wednesday, 28 March 2012 08:10:21
Here's the ping from the other ISP:
$ ping nlede01.sixxs.net
PING nlede01.sixxs.net (193.109.122.244) 56(84) bytes of data.
From 213.166.61.97 icmp_seq=23 Destination Net Unreachable
From 213.166.61.97 icmp_seq=33 Destination Net Unreachable
From 213.166.61.97 icmp_seq=72 Destination Net Unreachable
From 213.166.61.97 icmp_seq=83 Destination Net Unreachable
From 213.166.61.97 icmp_seq=94 Destination Net Unreachable
From 213.166.61.97 icmp_seq=113 Destination Net Unreachable
From 213.166.61.97 icmp_seq=123 Destination Net Unreachable
From 213.166.61.97 icmp_seq=163 Destination Net Unreachable
From 213.166.61.97 icmp_seq=164 Destination Net Unreachable
From 213.166.61.97 icmp_seq=174 Destination Net Unreachable
shows as up, but does not respond to IPv4 ping
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 28 March 2012 09:45:48
With T36629 to nlede01 I have the same problem. Aiccu test doesn't ping the Remote/PoP Outer Endpoint (193.109.122.244), this is from 95.97.76.244 (UPC.nl network). From another ISP (Ziggo), there's no connectivity, too. IPv6 connectivity from the outside travels as far as the nlede01 endpoint of the tunnel, then halts.
(Might be related to a DDOS that Bit Internet experienced this morning:
http://bit.nl/home/support/storingen-onderhoud/storingen/?id=1332911152
Traffic statistics for nlede01 show no traffic after 7:00 this morning: https://www.sixxs.net/misc/traffic/?pop=nlede01&last=6hour)
State change: confirmed
The state of this ticket has been changed to confirmed
shows as up, but does not respond to IPv4 ping
When DDoS attacks happen to destinations in the special subnet where nlede01 lives the routes get removed from the Internet and thus it becomes unreachable. It should return shortly though for non directly connected networks.
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 28 March 2012 10:03:20
Posting is only allowed when you are