|
Ticket ID: SIXXS #754750 Ticket Status: User PoP: nlams05 - SURFnet (Amsterdam)
Delay before the endpoint is pingable
![[nl]](/s/countries/nl.gif) Carmen Sandiego on Sunday, 29 June 2008 15:05:45
I'm currently running an experimental test setup, but the issue also happens in a more 'consumer based setup'. I guess this is more a technical question, than an actual problem.
Trivial setup:
Speedtouch 716v5 - | NAT | - Switch (Asus GigaX 1024P) - PC (Linux 2.6.25 /aiccu/heartbeat)
:nat mapadd intf=Internet type=nat outside_addr=213.84.249.129
inside_addr=192.168.1.4 foreign_addr=194.109.5.241 protocol=6to4
Experimental setup
Speedtouch 716v5 - | NAT | - Switch (Asus GigaX 1024P) - Switch (HP J4121A ProCurve Switch 4000M / C.09.28) [VLAN 255] - Router (Linux 2.6.25 / aiccu/heartbeat) [VLAN 255]
:nat mapadd intf=Internet type=nat outside_addr=213.84.249.129
inside_addr=192.168.255.254 foreign_addr=194.109.5.241 protocol=6to4
In both occasions it takes a while before the tunnel gets 'active', I mean with that the following:
ping6 2001:610:600:f6::1
PING 2001:610:600:f6::1(2001:610:600:f6::1) 56 data bytes
64 bytes from 2001:610:600:f6::1: icmp_seq=282 ttl=64 time=12.7 ms
You see that there are already 281 packets that went lost. In this case you might understand while 'aiccu test' does not actually fail, but it also doesn't work instantly.
1: 192.168.255.1 (192.168.255.1) 1.434ms pmtu 1500
1: 192.168.255.254 (192.168.255.254) 5.046ms
2: 195.190.242.1 (195.190.242.1) asymm 3 26.782ms
3: 42.ge-1-1-0.xr4.1d12.xs4all.net (194.109.5.49) asymm 5 28.115ms
4: ipv6-tb.xs4all.net (194.109.5.241) asymm 5 29.510ms reached
Resume: pmtu 1500 hops 4 back 5
1?: [LOCALHOST] pmtu 1280
1: gw-247.ams-05.nl.sixxs.net 32.579ms reached
Resume: pmtu 1280 hops 1 back 1
I'm not really reporting a problem here, since it fixes itself, I merely try to figure out why it doesn't work instantly. (Could be I missed a FAQ entry)
State change: user
The state of this ticket has been changed to user
Delay before the endpoint is pingable
Contact the vendor of your hardware/operating system, check with Wireshark what is going on etc.
Delay before the endpoint is pingable
Carmen Sandiego on Monday, 30 June 2008 19:35:30
I tried to reproduce the same problem today, and 'aiccu test' works instantly again (both systems). It might be the Speedtouch 'natting'.
I don't know if this bug can be open, or closed to later investigation, when it will be able to reproduce it again.
Delay before the endpoint is pingable
Carmen Sandiego on Tuesday, 08 July 2008 14:33:54
tv skinkie # tcpdump host 192.87.102.107
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
14:19:31.122990 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 92
14:19:31.135217 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:19:31.135967 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:19:31.135997 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:19:35.124324 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 92
14:19:39.124314 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 92
14:20:31.136104 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:21:31.136235 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:22:31.136361 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:23:31.136479 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:24:31.136617 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:25:31.136735 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:26:31.136851 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:27:31.136971 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:28:31.137088 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:29:31.137211 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:30:31.137326 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:30:31.176847 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 108
14:30:31.798718 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 108
14:30:34.919413 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 116
14:30:39.787145 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 116
14:31:31.137445 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
14:32:07.834522 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 148
14:32:07.835049 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 148
14:32:08.836554 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 148
14:32:08.837023 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 148
14:32:09.837095 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 148
14:32:09.837568 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 148
14:32:10.836680 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 148
14:32:10.836995 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 148
14:32:11.836721 IP sixxs.surfnet.nl.5072 > 10.0.0.24.55213: UDP, length 148
14:32:11.837023 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 148
14:32:31.137570 IP 10.0.0.24.55213 > sixxs.surfnet.nl.5072: UDP, length 44
This is my ayiya output. This is a totally different location...
|
![[ch]](/s/countries/ch.gif)
on Sunday, 29 June 2008 21:15:04
Posting is only allowed when you are