Ticket ID: SIXXS #736349 Ticket Status: Resolved PoP: plwaw01 - ICM (Warsaw)
Status of my link is down but my link is working
![]()
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Statistics shows that my tunnel is down, but I cannot even ping the PoP site of the tunnel:
http://www.sixxs.net/tools/traceroute/
IPv6 traceroute from noc.sixxs.net @ SixXS NOC, AS12871 to 2001:6a0:200:36::1 :
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:838:1:1::1 0.0% 5 0.4 0.5 0.4 0.5 0.0 12871 Concepts ICT
ge-1-3-0.breda.ipv6.concepts-ict.net.
2. 2001:838:0:10::1 0.0% 5 2.4 2.4 2.3 2.4 0.0 12871 Concepts ICT
3. 2001:7f8:1::a500:1273:1 0.0% 5 2.6 2.6 2.6 2.7 0.1
zpr2.amt.cw.net.
4. 2001:5000:0:11d::1 0.0% 5 8.5 13.0 8.5 30.6 9.9 1273 Cable & Wireless Telecommunication Services GmbH
xe-0-1-0.xcr1.amd.cw.net.
5. 2001:5000:0:10d::2 0.0% 5 8.8 8.8 8.7 8.9 0.0 1273 Cable & Wireless Telecommunication Services GmbH
ge-6-0-0.dcr1.fra.cw.net.
6. 2001:5000:0:8::1 0.0% 5 8.8 8.8 8.8 8.9 0.1 1273 Cable & Wireless Telecommunication Services GmbH
so-4-0-0-bcr2.fra.cw.net.
7. 2001:5000:0:14::3 0.0% 5 8.8 9.0 8.8 9.3 0.2 1273 Cable & Wireless Telecommunication Services GmbH
ge-1-3-0-iar1.fra.cw.net.
8. 2001:5001:200:6::2 0.0% 5 37.5 37.6 37.5 37.7 0.1 1273 Cable & Wireless Telecommunication Services GmbH
9. 2001:2000:3010::2 0.0% 5 37.4 37.4 37.4 37.6 0.1 1299 TeliaSonera AB
s-ipv6-b1-link.ipv6.telia.net.
10. 2001:2000:3010:1::2 0.0% 5 46.2 46.3 46.1 46.4 0.2 1299 TeliaSonera AB
adm-ipv6-b1-link.ipv6.telia.net.
11. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0
It seems that there is some problem with link to my PoP and the IPv6 network.
Status of my link is down but my link is working
There is a routing change inside GEANT which is causing this. We are waiting for the problem to be resolved.
State change: confirmed
![]() ![]()
The state of this ticket has been changed to confirmed
Status of my link is down but my link is working
![]()
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
This affects probably every plwaw01 user, too (including me). I hope that tunnels won't be automaticly deleted due to this issue. Credit points are already subtracted for example.
Status of my link is down but my link is working
![]()
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Hello,
Same here (couldnt sleep cause of that ;d)
Please push Geant to fix this problem.
plpoz01 PoP lost IPv4 tunnel end-point configuration
![]()
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
This ticket may be related to the problems reported in the Ticket ID: SIXXS #736349.
Th plpoz01 lost information of IPv4 tunnel end-point:
The configuration for this tunnel looks like:
Tunnel Name WFiIS - PCSS 6in4 tunnel
PoP Name plpoz01
PoP Location Poznan, Poland Poland
PoP IPv4 150.254.166.147
Your Location Krakow, Poland Poland
Your IPv4 unknown (Tunnel not configured on PoP) <--- PROBLEM !!!
IPv6 Prefix 2001:808:100:1b::1/64
PoP IPv6 2001:808:100:1b::1
Your IPv6 2001:808:100:1b::2
Created 2008-01-23 20:55:47 CEST
Last Alive 2008-05-27 17:06:29 CEST
State Enabled
When "Change Endpoint location" button is clicked the correct information appears:
Change Endpoint
New IPv4 Endpoint: 149.156.110.250
New City: Krakow
New Country: Poland
The plpoz01 PoP's looking glass traceroute (http://www.ipv6.man.poznan.pl/cgi-bin/ping.cgi) shows no connectivity to PoP's own tunnel end-point:
traceroute6 2001:808:100:1b::1
traceroute to 2001:808:100:1b::1 (2001:808:100:1b::1), 30 hops max, 40 byte packets
1 css7.ipv6.man.poznan.pl (2001:808::7) 0.660 ms 0.482 ms 0.480 ms
2 plpoz01.sixxs.net (2001:808::66)(N!) 0.305 ms (N!) 0.310 ms (N!) 0.291 ms
The tcpdump from client endpoint:
~# tcpdump -i eth0 'host 150.254.166.147' -v
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
10:51:57.136067 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 124) cerber.ftj.agh.edu.pl > chives.man.poznan.pl: cl-28.poz-01.pl.sixxs.net > gw-28.poz-01.pl.sixxs.net: icmp6: echo request seq 4 (len 64, hlim 64)
10:51:57.146131 IP (tos 0x0, ttl 59, id 18506, offset 0, flags [none], length: 152) chives.man.poznan.pl > cerber.ftj.agh.edu.pl: icmp 132: chives.man.poznan.pl protocol 41 port 0 unreachable
10:51:58.136209 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 124) cerber.ftj.agh.edu.pl > chives.man.poznan.pl: cl-28.poz-01.pl.sixxs.net > gw-28.poz-01.pl.sixxs.net: icmp6: echo request seq 5 (len 64, hlim 64)
10:51:58.146364 IP (tos 0x0, ttl 59, id 18507, offset 0, flags [none], length: 152) chives.man.poznan.pl > cerber.ftj.agh.edu.pl: icmp 132: chives.man.poznan.pl protocol 41 port 0 unreachable
If this is network problem I hope we'll get back our lost credit points ;)
Username:PGT1-SIXXS
Full name:Piotr Gronek
Organisation:AGH-UST Faculty of Physics and Applied Computer Science
Email:gronek@ftj.agh.edu.pl
plpoz01 PoP lost IPv4 tunnel end-point configuration (cross-post)
![]()
Sorry for accidental cross-posting of the previous message :)
plpoz01 PoP lost endpoint IPv4 configuration
![]()
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
This ticket may be related to the problems reported in the Ticket ID: SIXXS #736349.
Th plpoz01 lost information of IPv4 tunnel end-point:
The configuration for this tunnel looks like:
Tunnel Name WFiIS - PCSS 6in4 tunnel
PoP Name plpoz01
PoP Location Poznan, Poland Poland
PoP IPv4 150.254.166.147
Your Location Krakow, Poland Poland
Your IPv4 unknown (Tunnel not configured on PoP) <--- PROBLEM !!!
IPv6 Prefix 2001:808:100:1b::1/64
PoP IPv6 2001:808:100:1b::1
Your IPv6 2001:808:100:1b::2
Created 2008-01-23 20:55:47 CEST
Last Alive 2008-05-27 17:06:29 CEST
State Enabled
When "Change Endpoint location" button is clicked the correct information appears:
Change Endpoint
New IPv4 Endpoint: 149.156.110.250
New City: Krakow
New Country: Poland
The plpoz01 PoP's looking glass traceroute (http://www.ipv6.man.poznan.pl/cgi-bin/ping.cgi) shows no connectivity to PoP's own tunnel end-point:
traceroute6 2001:808:100:1b::1
traceroute to 2001:808:100:1b::1 (2001:808:100:1b::1), 30 hops max, 40 byte packets
1 css7.ipv6.man.poznan.pl (2001:808::7) 0.660 ms 0.482 ms 0.480 ms
2 plpoz01.sixxs.net (2001:808::66)(N!) 0.305 ms (N!) 0.310 ms (N!) 0.291 ms
The tcpdump from client endpoint:
~# tcpdump -i eth0 'host 150.254.166.147' -v
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
10:51:57.136067 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 124) cerber.ftj.agh.edu.pl > chives.man.poznan.pl: cl-28.poz-01.pl.sixxs.net > gw-28.poz-01.pl.sixxs.net: icmp6: echo request seq 4 (len 64, hlim 64)
10:51:57.146131 IP (tos 0x0, ttl 59, id 18506, offset 0, flags [none], length: 152) chives.man.poznan.pl > cerber.ftj.agh.edu.pl: icmp 132: chives.man.poznan.pl protocol 41 port 0 unreachable
10:51:58.136209 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 124) cerber.ftj.agh.edu.pl > chives.man.poznan.pl: cl-28.poz-01.pl.sixxs.net > gw-28.poz-01.pl.sixxs.net: icmp6: echo request seq 5 (len 64, hlim 64)
10:51:58.146364 IP (tos 0x0, ttl 59, id 18507, offset 0, flags [none], length: 152) chives.man.poznan.pl > cerber.ftj.agh.edu.pl: icmp 132: chives.man.poznan.pl protocol 41 port 0 unreachable
If this is network problem I hope we'll get back our lost credit points ;)
(Sorry for accidental cross-posting into plwaw01 ticket)
Username: PGT1-SIXXS
Full name: Piotr Gronek
Organisation: AGH-UST Faculty of Physics and Applied Computer Science
Email: gronek@ftj.agh.edu.pl
State change: user
![]() ![]()
The state of this ticket has been changed to user
State change: resolved
![]() ![]()
The state of this ticket has been changed to resolved
|