Ticket ID: SIXXS #756446 Ticket Status: User PoP: simbx01 - Amis (Maribor)
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Tuesday, 01 July 2008 08:07:22
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:
Problem: No ICMPv6 ECHO requests recieved from the PoP; The tunnel is otherwise
fully operational;
Who am I
Username:PVP19-RIPE (If this is what you mean by NIC..)
Full name:Plamen Vassilev Petrov
Info on the tunnel:
Tunnel Type 6in4 Static
Tunnel Name FS IPv6
PoP Name simbx01
PoP Location Maribor, Slovenia
PoP IPv4 212.18.63.73
Your Location Silistra, Bulgaria
Your IPv4 83.228.35.12
IPv6 Prefix 2001:15c0:65ff:64::1/64
PoP IPv6 2001:15c0:65ff:64::1
Your IPv6 2001:15c0:65ff:64::2
Created 2006-04-18 15:05:41 CEST
Last Alive 2008-06-28 16:08:09 CEST
State Enabled
Additional info:
The machine that uses the tunnel is a Dell SC440, connected to the internet
via a ADSL modem (provider: Bulgarian Telecommunications Company). There are three (3) ethernet adapters in this PC: one is connected directly to the ADSL modem, the other two ethernet adapters are serving two physical subnets; the machine acts as a gateway for both LANs, using NAT.
The software running on the machine is Slackware 12 Linux with some updates through compilation from sources; The currently running kernel is 2.6.25.9.
Output of "ifconfig -a" command:
eth0 Link encap:Ethernet HWaddr 00:15:17:39:EE:23
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:17ff:fe39:ee23/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99063 errors:0 dropped:0 overruns:0 frame:0
TX packets:69376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:104917845 (100.0 MiB) TX bytes:8397455 (8.0 MiB)
Memory:efcc0000-efce0000
eth1 Link encap:Ethernet HWaddr 00:1A:A0:38:8A:1B
inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::21a:a0ff:fe38:8a1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:108385 errors:0 dropped:0 overruns:0 frame:0
TX packets:158834 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11382894 (10.8 MiB) TX bytes:193034700 (184.0 MiB)
Interrupt:17
eth2 Link encap:Ethernet HWaddr 00:0E:2E:5C:27:E6
inet addr:192.168.199.1 Bcast:192.168.199.255 Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe5c:27e6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12606 errors:0 dropped:0 overruns:0 frame:0
TX packets:13574 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1722508 (1.6 MiB) TX bytes:8690864 (8.2 MiB)
Interrupt:16 Base address:0x6f00
gre0 Link encap:UNSPEC HWaddr 00-00-00-00-FF-00-73-69-00-00-00-00-00-00-00 -00
NOARP MTU:1476 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 -00
NOARP MTU:1460 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:27214 errors:0 dropped:0 overruns:0 frame:0
TX packets:27214 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2024448 (1.9 MiB) TX bytes:2024448 (1.9 MiB)
sit0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-73-69-00-00-00-00-00-00-00 -00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
sixxs_t Link encap:UNSPEC HWaddr C0-A8-01-02-00-00-73-69-00-00-00-00-00-00-00 -00
inet6 addr: 2001:15c0:65ff:64::2/64 Scope:Global
inet6 addr: fe80::c0a8:102/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:875 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64592 (63.0 KiB) TX bytes:1140 (1.1 KiB)
teql0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 -00
NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Output of "traceroute 212.18.63.73" command:
traceroute to 212.18.63.73 (212.18.63.73), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 1.238 ms 2.006 ms 1.187 ms
2 212-39-87-234.btc-net.bg (212.39.87.234) 10.977 ms 10.594 ms 10.729 ms
3 212.39.69.212 (212.39.69.212) 20.476 ms 19.815 ms 15.973 ms
4 212.39.69.225 (212.39.69.225) 19.731 ms 212.39.69.226 (212.39.69.226) 20.168 ms 212.39.69.210 (212.39.69.210) 16.423 ms
5 42-91-39-212.btc-net.bg (212.39.91.42) 47.889 ms 50.846 ms 10-91-39-212.btc-net.bg (212.39.91.10) 57.459 ms
6 ffm-b6-link.telia.net (213.248.94.25) 48.152 ms 54.330 ms 52.954 ms
7 ffm-bb1-link.telia.net (80.91.249.81) 61.951 ms ffm-bb1-link.telia.net (80.91.254.162) 53.648 ms 61.111 ms
8 win-b2-link.telia.net (80.91.252.77) 70.942 ms 76.619 ms 69.196 ms
9 amis-ic-124783-win-b2.c.telia.net (213.248.72.106) 73.693 ms 67.135 ms 72.942 ms
10 maribor3-po-1.amis.net (212.18.41.137) 65.200 ms 77.107 ms 71.194 ms
11 simbx01.sixxs.net (212.18.63.73) 69.444 ms 69.134 ms 75.442 ms
Output of "traceroute6 2001:15c0:65ff:64::1" command:
traceroute to 2001:15c0:65ff:64::1 (2001:15c0:65ff:64::1) from 2001:15c0:65ff:64::2, 30 hops max, 16 byte packets
1 gw-101.mbx-01.si.sixxs.net (2001:15c0:65ff:64::1) 77.683 ms 77.308 ms 77.934 ms
Output of "ip route show" command:
192.168.199.0/24 dev eth2 proto kernel scope link src 192.168.199.1
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2
192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.1
127.0.0.0/8 dev lo scope link
default via 192.168.1.1 dev eth0 metric 1
Output of "ip -6 route show" command:
2001:15c0:65ff:64::/64 via :: dev sixxs_t metric 256 expires -7399sec mtu 1280 advmss 1220 metric 10 4294967295
fe80::/64 dev eth2 metric 256 expires -7398sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 via :: dev sixxs_t metric 256 expires -7398sec mtu 1280 advmss 1220 metric 10 4294967295
fe80::/64 dev eth0 metric 256 expires -7396sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev eth1 metric 256 expires -7395sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev eth2 metric 256 expires -7398sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev sixxs_t metric 256 expires -7398sec mtu 1280 advmss 1220 metric 10 4294967295
ff00::/8 dev eth0 metric 256 expires -7396sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev eth1 metric 256 expires -7395sec mtu 1500 advmss 1440 metric 10 4294967295
default via 2001:15c0:65ff:64::1 dev sixxs_t metric 1024 expires -7398sec mtu 1280 advmss 1220 metric 10 4294967295
unreachable default dev lo proto none metric -1 error -101 metric 10 255
And here you can see some stats, collected on my end of the tunnel.
Also, on this forum thread I posted a 10 minutes worth of tcpdump output - there are no ICMPv6 ECHO requests recieved in these 10 minutes.
And finally, thanks for your time!
If this turns out to be my fault, or that I'm missing something, and I hope you can point out where I'm mistaken.
Any help will be greatly appreciated!
Regards,
Plamen Petrov
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Tuesday, 01 July 2008 08:24:20
Dear Staff,
I've been discussing with colleague and we have the same issue with this PoP (simbx01). No ICMPv6 packets seen over hours and yet fully operational tunnel. Traffic flows normaly in and out, no packetloss or large round trip times.
My info:
NIC: MRR3-SIXXS
PoP Name simbx01
PoP Location Maribor, Slovenia Slovenia
PoP IPv4 212.18.63.73
Your Location Ljubljana, Slovenia Slovenia
Your IPv4 193.77.153.51
IPv6 Prefix 2001:15c0:65ff:161::1/64
PoP IPv6 2001:15c0:65ff:161::1
Your IPv6 2001:15c0:65ff:161::2
Created 2008-02-28 14:49:55 CEST
Last Alive 2008-06-28 16:08:10 CEST
# uname -a
FreeBSD core.perkmandlc.org 5.4-STABLE FreeBSD 5.4-STABLE #2: Sun Oct 23 16:46:22 CEST 2005 root@core.perkmandlc.org:/usr/obj/usr/src/sys/ESY i386
# ifconfig
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=48<VLAN_MTU,POLLING>
inet 192.168.x.1 netmask 0xffffff00 broadcast 192.168.x.255
inet6 fe80::250:fcff:fecc:2d42%rl0 prefixlen 64 scopeid 0x1
inet6 2001:15c0:6699::1 prefixlen 64
ether 00:50:fc:cc:2d:42
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
rl1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=48<VLAN_MTU,POLLING>
ether 00:50:fc:b3:86:d6
media: Ethernet autoselect (10baseT/UTP)
status: no carrier
pfsync0: flags=0<> mtu 2020
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33208
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
inet 193.77.153.51 --> 213.250.19.90 netmask 0xffffffff
Opened by PID 238
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 193.77.153.51 --> 212.18.63.73
inet6 2001:15c0:65ff:161::2 --> 2001:15c0:65ff:161::1 prefixlen 128
# netstat -rn -f inet6
Routing tables
Internet6:
Destination Gateway Flags Netif Expire
default 2001:15c0:65ff:161::1 UGS gif0
::1 ::1 UH lo0
2001:15c0:65ff:161::1 2001:15c0:65ff:161::2 UH gif0
2001:15c0:65ff:161::2 link#8 UHL lo0
2001:15c0:6699::/64 link#1 UC rl0
2001:15c0:6699::1 00:50:fc:cc:2d:42 UHL lo0
fe80::%rl0/64 link#1 UC rl0
fe80::219:99ff:fe40:13c%rl0 00:19:99:40:01:3c UHLW rl0
fe80::250:fcff:fecc:2d42%rl0 00:50:fc:cc:2d:42 UHL lo0
fe80::%lo0/64 fe80::1%lo0 U lo0
fe80::1%lo0 link#5 UHL lo0
fe80::250:fcff:fecc:2d42%tun4 link#7 UHL lo0
fe80::250:fcff:fecc:2d42%gif1 link#10 UHL lo0
ff01::/32 ::1 U lo0
ff02::%rl0/32 link#1 UC rl0
ff02::%lo0/32 ::1 UC lo0
ff02::%tun0/32 fe80::250:fcff:fecc:2d42%tun0 UC tun0
ff02::%gif0/32 link#8 UC gif0
# ping6 sixxs.net
PING6(56=40+8+8 bytes) 2001:15c0:65ff:161::2 --> 2001:838:1:1:210:dcff:fe20:7c7c
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=0 hlim=51 time=46.698 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=1 hlim=51 time=46.498 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=2 hlim=51 time=46.469 ms
16 bytes from 2001:838:1:1:210:dcff:fe20:7c7c, icmp_seq=3 hlim=51 time=45.590 ms
^C
--- sixxs.net ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 45.590/46.314/46.698/0.427 ms
# telnet sixxs.net 80
Trying 2001:838:1:1:210:dcff:fe20:7c7c...
Connected to sixxs.net.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
#
Sincerely yours,
Marko Rizvic
State change: user
Jeroen Massar on Tuesday, 01 July 2008 11:28:07
The state of this ticket has been changed to user
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Tuesday, 01 July 2008 11:30:26
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:
I have same problem. My tunnel is reported as dead.
Who am i:
Username:DRT1-SIXXS
Full name:Daniel Rimal
Organisation:TUL
Email:daniel.rimal@uvt.cz
Address:Strupcice 112
Strupcice
Czech republic
Phone:+420777091423
Created:2006-10-15 12:44:36 CEST
Last Modified:2006-10-15 22:11:14 CEST
Credits:171 ISK
Country: Czech Republic Czech Republic (cz)
I receive this message:
This is the tunnelrobot at SixXS, mailing you to inform you that your
tunnel to Amis has not been replying to pings for a period of time
Here's the information regarding the tunnel:
Handle : DRT1-SIXXS
PoP Name : simbx01 (si.medinet [AS8591])
Your Location: Chomutov, cz
SixXS IPv6 : 2001:15c0:65ff:d3::1/64
Your IPv6 : 2001:15c0:65ff:d3::2/64
SixXS IPv4 : 212.18.63.73
Your IPv4 : 217.75.209.107
Last known responding: 2008-06-28 16:08:10
but, my tunnel is OK:
[root@darek ~]# ping6 2001:15c0:65ff:d3::1
PING 2001:15c0:65ff:d3::1(2001:15c0:65ff:d3::1) 56 data bytes
64 bytes from 2001:15c0:65ff:d3::1: icmp_seq=1 ttl=64 time=61.0 ms
64 bytes from 2001:15c0:65ff:d3::1: icmp_seq=2 ttl=64 time=61.0 ms
64 bytes from 2001:15c0:65ff:d3::1: icmp_seq=3 ttl=64 time=60.2 ms
64 bytes from 2001:15c0:65ff:d3::1: icmp_seq=4 ttl=64 time=60.5 ms
64 bytes from 2001:15c0:65ff:d3::1: icmp_seq=5 ttl=64 time=50.3 ms
--- 2001:15c0:65ff:d3::1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 50.344/58.665/61.092/4.183 ms
[root@darek ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:4F:3B:76:CD
inet addr:217.75.209.107 Bcast:217.75.209.127 Mask:255.255.255.128
inet6 addr: fe80::230:4fff:fe3b:76cd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2604809 errors:0 dropped:0 overruns:0 frame:0
TX packets:136926 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292370801 (278.8 MiB) TX bytes:31273592 (29.8 MiB)
eth1 Link encap:Ethernet HWaddr 00:02:B3:B3:9F:B3
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:15c0:665b::1/64 Scope:Global
inet6 addr: fe80::202:b3ff:feb3:9fb3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3486661 errors:0 dropped:0 overruns:0 frame:0
TX packets:1857739 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:722527449 (689.0 MiB) TX bytes:227827437 (217.2 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1251159 errors:0 dropped:0 overruns:0 frame:0
TX packets:1251159 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2816416963 (2.6 GiB) TX bytes:2816416963 (2.6 GiB)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:15c0:65ff:d3::2/64 Scope:Global
inet6 addr: fe80::d94b:d16b/128 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:6865 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:510472 (498.5 KiB) TX bytes:5456 (5.3 KiB)
[root@darek ~]# ping6 www.cesnet.cz -n
PING www.cesnet.cz(2001:718:1:101:204:23ff:fe52:221a) 56 data bytes
64 bytes from 2001:718:1:101:204:23ff:fe52:221a: icmp_seq=1 ttl=51 time=246 ms
64 bytes from 2001:718:1:101:204:23ff:fe52:221a: icmp_seq=2 ttl=51 time=99.1 ms
64 bytes from 2001:718:1:101:204:23ff:fe52:221a: icmp_seq=3 ttl=51 time=120 ms
64 bytes from 2001:718:1:101:204:23ff:fe52:221a: icmp_seq=4 ttl=51 time=88.1 ms
--- www.cesnet.cz ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 88.110/138.448/246.348/63.351 ms
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Tuesday, 01 July 2008 16:27:56
I checked the FAQ, but if you don't mind me asking:
What does
Ticket Status: User
mean? Does it mean, that the problem is on my (user) end?
Thanks,
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Tuesday, 01 July 2008 19:10:29
Could this be related to our problems with simbx01?
Go to the latency stats, for time period select one week, for what to show - select any of the last two options in the list (latency stats between PoPs and well known destinations), check the box in front of simbx01, then press View.
What I'm seeing is that the simbx01 PoP is having troubles - at least with the stats, if not more....
And strangely enough, the graph's collected data end at the exact same time my/our tunnels are reported as "last seen alive"....
Fully working static 6-in-4 tunnel is reported dead on its stats page; No ICMPv6 ECHO requests recieved; Lots of ICMPv6 Multicast listener requests and reports
Shadow Hawkins on Wednesday, 09 July 2008 14:04:08
Well, at least to me, it seems so: a day or two after my previous post here, the simbx01 PoP was reported as "known to have problems".
As I'm writing this, my tunnel is back up, and everything seems fine.
A little more info from the appropriate people would have been really nice - I mean, when I reported this, I was definitely somewhere back on the line of people, saying that they are having troubles with their IPv6 tunnelsl; yet, all the admins did to most of these reports was to change the status of the tickets to "User", which I still don't know what exactly means (see my above posts).
Anyway, thanks for getting simbx01 back up and running!
Posting is only allowed when you are logged in. |