Ticket ID: SIXXS #3993509 Ticket Status: User PoP: frmrs01 - Jaguar Network SARL (Marseille)
frmrs01 sending icmp port unreachable after tunnel establishment
Shadow Hawkins on Monday, 28 March 2011 20:28:28
Hi !
frmrs01 pop is not working anymore for me, and it seems it's general, see the graph stops at middle-of-March: https://www.sixxs.net/misc/traffic/?pop=frmrs01&last=1year
On my gateway, this yields:
gw:/home/creis# /etc/init.d/aiccu restart
Restarting SixXS Automatic IPv6 Connectivity Client Utility: aiccu
Tunnel Information for T20394:
POP Id : frmrs01
IPv6 Local : 2a01:240:fe00:5f::2/64
IPv6 Remote : 2a01:240:fe00:5f::1/64
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled
gw:/home/creis# tshark -lpni any host 78.153.240.201 &
[1]+ tshark -lpni any host 78.153.240.201 &
gw:/home/creis# ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8006::63) 56 data bytes
0.000000 2a01:240:fe00:5f::2 -> 2a00:1450:8006::63 ICMPv6 Echo request
0.001356 78.153.240.201 -> 192.168.1.253 ICMP Destination unreachable (Port unreachable)
0.093107 2001:0:5ef5:79fd:14c5:2ca8:a818:bf87 -> 2001:0:4137:9e76:145f:37de:c5f8:415f TCP 53202 > 58392 [SYN] Seq=0 Win=8192 Len=0 MSS=1220
0.094443 78.153.240.201 -> 192.168.1.253 ICMP Destination unreachable (Port unreachable)
1.007207 2a01:240:fe00:5f::2 -> 2a00:1450:8006::63 ICMPv6 Echo request
1.008739 78.153.240.201 -> 192.168.1.253 ICMP Destination unreachable (Port unreachable)
2.015203 2a01:240:fe00:5f::2 -> 2a00:1450:8006::63 ICMPv6 Echo request
2.016549 78.153.240.201 -> 192.168.1.253 ICMP Destination unreachable (Port unreachable)
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2015ms
Regards,
--
Helios de Creisquer <creis@balios.net>
State change: user
Jeroen Massar on Monday, 28 March 2011 20:31:01
The state of this ticket has been changed to user
frmrs01 sending icmp port unreachable after tunnel establishment
Jeroen Massar on Monday, 28 March 2011 20:37:12 frmrs01 pop is not working anymore for me, and it seems it's general, see the graph stops at middle-of-March: https://www.sixxs.net/misc/traffic/?pop=frmrs01&last=1year
The PoP traffic graphs are currently not available for any of the PoPs, see the open tickets. Individual tunnels are properly graphed though.
Tunnel Type : 6in4-heartbeat [..]
2.016549 78.153.240.201 -> 192.168.1.253 ICMP Destination unreachable (Port unreachable)
As such 'port unreachable' is impossible, as there are no ports for protocol-41.
There is an RFC1918 address there, did you really configure your NAT properly and can it cope with protocol 41. Why don't you use an AYIYA tunnel which is made for crossing NAT boxes?
What is the actual information below it? Also, your output is not showing any protocol 41 packets going out, which is strange to say the least.
Additionally, why are you trying to ping google? Are you able to ping the PoP side of the tunnel?
Please actually read the instructions and provide the requested details as stated on the contact page, as referred to that big orange box, without them, there is not much we can do.
[solved] frmrs01 sending icmp port unreachable after tunnel establishment
Shadow Hawkins on Tuesday, 29 March 2011 19:24:54
Hi,
First of all, thank you very much for the answer and sorry for the broken report:
- problem is corrected
- my provider forwarded the tunnel correctly until some days ago and just... stopped (?)
- looking at the graph, it fitted :-/
- I searched about reports on frmrs and found none, but I didn't thought of looking at a ticket about the graphing system.
- As for the unreachable, it seems the provider router sent them, faking the source of the ICMP as the destination IP for the proto-41 packets, and using port-unreach for whatever reason...
Sorry for the noise,
Regards,
Posting is only allowed when you are logged in. |