SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #4806541
Ticket Status: User

PoP: hubud02 - DIGI Kft (Budapest)

ISK issue T67073
[hu] Shadow Hawkins on Sunday, 29 May 2011 21:01:19
2011-05-22 12:55:16 SixXS approved tunnel T67073 to heartbeat on PoP hubud02
ICMP v6 test:
--- cl-8.bud-02.hu.sixxs.net ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9035ms rtt min/avg/max/mdev = 4.000/4.000/4.000/0.000 ms
ICMP v4 test:
--- 94-21-22-175.pool.digikabel.hu ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9012ms rtt min/avg/max/mdev = 3.792/4.104/4.396/0.189 ms
AICCU works fine:
ps aux |grep aiccu root 5714 0.0 0.4 3320 764 pts/2 S+ 20:54 0:00 grep aiccu root 21790 0.0 0.1 3208 296 ? Ss May22 0:09 /usr/sbin/aiccu start
The tunnel is up more than 7 days (168 hours), but i can not get 5 ISK for first week up.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 30 May 2011 09:10:56
Message is Locked
The state of this ticket has been changed to user
ISK issue T67073
[ch] Jeroen Massar SixXS Staff on Monday, 30 May 2011 09:11:31
Please see the FAQ about 'my endpoint does not ping' and of course the one on connection trackers, the answer to your issue is most likely there.
ISK issue T67073
[hu] Shadow Hawkins on Monday, 30 May 2011 12:38:35
The PoP you are connected to tests the latency of your connection by pinging using ICMPv6 Echo Request packets from the PoP's IPv6 endpoint to your IPv6 tunnel endpoint. One way to easily find out if you have a setup problem is by doing a tcpdump and pinging the PoP's endpoint and checking if you see a response coming back if that's the case leave your tcpdump running and see if you get the 20 ping's which are sent every 30 minutes. Thus you have 24 * 2 * 20 = 1920 pings the chance to be up every day.
ping6 cl-8.bud-02.hu.sixxs.net at HUBUD02(PoP) console with manually (thanks for PoP admin) tcpdump ip6 -i sixxs at T67073
12:12:18.754889 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 1, length 64 12:12:18.755085 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 1, length 64 12:12:19.756550 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 2, length 64 12:12:19.756719 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 2, length 64 12:12:20.757966 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 3, length 64 12:12:20.758140 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 3, length 64 12:12:21.759647 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 4, length 64 12:12:21.759897 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 4, length 64 12:12:22.761278 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 5, length 64 12:12:22.761430 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 5, length 64
ping6 gw-8.bud-02.hu.sixxs.net at T67073 tcpdump ip6 -i sixxs at T67073
12:25:50.729039 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 1, length 64 12:25:50.732685 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 1, length 64 12:25:51.730169 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 2, length 64 12:25:51.733874 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 2, length 64 12:25:52.731639 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 3, length 64 12:25:52.735206 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 3, length 64 12:25:53.733285 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 4, length 64 12:25:53.736819 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 4, length 64 12:25:54.734786 IP6 cl-8.bud-02.hu.sixxs.net > gw-8.bud-02.hu.sixxs.net: ICMP6, echo request, seq 5, length 64 12:25:54.738356 IP6 gw-8.bud-02.hu.sixxs.net > cl-8.bud-02.hu.sixxs.net: ICMP6, echo reply, seq 5, length 64
It seems like ok, but i have not any automatic ping from the PoP. I have an 1 hour tcpdump log but no ICMP request from HUBUD02 PoP.
ISK issue T67073
[hu] Shadow Hawkins on Monday, 30 May 2011 13:02:16
I am using hubud02 too, and didn't get any credits for the tunnel uptime. Also the tunnel latency graphs are missing (0bytes http response) from the tunnel detail page. Daniel
ISK issue T67073
[hu] Shadow Hawkins on Monday, 13 June 2011 15:52:39
I did not receive any ISK always yet. my latency graf my loss graf

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

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