SixXS::Sunset 2017-06-06

psinet pop germany taken out?
[de] Shadow Hawkins on Wednesday, 17 September 2003 04:24:12
hi *, i just found, that for the last two hours, latency stats on the german pop by psinet europe show NO latency (nor paketloss) for ALL hosts except zesbot.ipv6.surfnet.nl. so i did some testing... blackbox:/home/leeps# traceroute6 noc.sixxs.net traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:768:1900:82::2, 30 hops max, 16 byte packets 1 * * * 2 * * * blackbox:/home/leeps# ping6 -c 4 2001:768:1900:82::1 PING 2001:768:1900:82::1(2001:768:1900:82::1) 56 data bytes --- 2001:768:1900:82::1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3018ms mainframe:/home/lechte# traceroute6 noc.sixxs.net traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:768:193b::1, 30 hops max, 16 byte packets 1 * * * mainframe:/home/lechte# ping6 -c 4 2001:768:1900:28::1 PING 2001:768:1900:28::1(2001:768:1900:28::1) 56 data bytes --- 2001:768:1900:28::1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3014ms pings from outside to my endpoints show the same 100% loss, while tcdump on both boxes show nothing during that time. sixxs-traceroute-tool shows: traceroute to ipv6.mainframe.frontbone.de (2001:768:193b::1) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets 1 fe0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.512 ms 0.525 ms 0.431 ms 2 se2.ams-ix.ipv6.concepts-ict.net (2001:838:0:10::1) 3.522 ms 3.495 ms 3.514 ms 3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 3.861 ms 3.668 ms 3.678 ms 4 3ffe:1001:1:f00d::1 (3ffe:1001:1:f00d::1) 35.814 ms 35.303 ms 35.472 ms 5 3ffe:1001:1:f011::2 (3ffe:1001:1:f011::2) 53.044 ms 51.399 ms 51.516 ms 6 bb2-hst-fe4-0-0.muc.ipv6.eurocyber.net (2001:768:f:4::2) 87.698 ms bb2-hst-fe1-0-0.muc.ipv6.eurocyber.net (2001:768:f:3::2) 82.661 ms bb2-hst-fe4-0-0.muc.ipv6.eurocyber.net (2001:768:f:4::2) 85.89 ms 7 broker01.muc.de.ipv6.sixxs.net (2001:768:1:2::3) 87.313 ms !H 83.016 ms !H 83.145 ms !H my route-configuration is on both boxes nearly the same (except for the lack of interfaces on 'mainframe'... blackbox:/home/leeps# ip -6 ro 2001:768:1900:82::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1500 metric10 64 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1500 metric10 64 fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 64 ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1500 metric10 1 ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1500 metric10 1 ff00::/8 dev sixxs proto kernel metric 256 mtu 1280 advmss 1280 metric10 1 default via 2001:768:1900:82::1 dev sixxs metric 1024 mtu 1280 advmss 1280 metric10 64 any hints? sebastian lechte
psinet pop germany taken out?
[de] Shadow Hawkins on Wednesday, 17 September 2003 04:57:16
Hi, no hints. Just an ack. Same problem here. I've sent an email to info@sixxs.net. Let's see if the POP is up when I am awake again. ;) Kind regards Lars
psinet pop germany taken out?
[pl] Shadow Hawkins on Wednesday, 17 September 2003 08:27:03
There a afaik route error in IPv4: [root@fido:~/aaa/root/ipv6]$ traceroute 195.143.155.2 traceroute to 195.143.155.2 (195.143.155.2), 30 hops max, 38 byte packets 1 10.132.0.1 (10.132.0.1) 23.711 ms 24.974 ms 8.857 ms 2 * * * 3 pl-waw03a-rd1-ge-0-1-0.aorta.net (213.46.178.9) 7.994 ms 8.995 ms 37.333 ms 4 de-fra01a-rd2-pos-1-0.aorta.net (213.46.160.209) 36.433 ms 37.859 ms 36.826 ms 5 de-fra01a-rd1-ge-3-1.aorta.net (213.46.179.5) 61.329 ms 37.664 ms 40.429 ms 6 de-fra01a-ri1-ge-1-1-0.aorta.net (213.46.179.1) 40.975 ms 76.255 ms 38.690 ms 7 de-cix.de.psi.net (80.81.192.10) 39.919 ms 36.911 ms 39.376 ms 8 tier1-1.FRA5.psie.net (154.14.65.12) 38.155 ms 40.115 ms 40.479 ms 9 tier1-1.MUC2.psie.net (154.14.65.8) 45.777 ms 45.538 ms 47.158 ms 10 bb2-hst.psie.net.t (154.14.66.66) 48.712 ms 49.120 ms 48.630 ms 11 * * * 12 * * * 13 *
psinet pop germany taken out?
[ch] Jeroen Massar SixXS Staff on Wednesday, 17 September 2003 13:38:17
There was a IPv4 outness last night to that machine, it has been fixed by the onsite staff. Btw the heartbeat service works perfectly ;) Additional note: notifying info@sixxs.net is faster than putting stuff up in the forum which isn't checked regulary.. and mail is by multiple people. Note #2: if a traceroute doesn't work and you think your routes are correct then tcpdump :)

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker