|
Ticket ID: SIXXS #882085 Ticket Status: User PoP: gblon02 - Goscomb Technologies (London)
Robot emails that tunnel is down - when actually tunnel endpoint pingable from sixxs and other ipv6 networks
![[us]](/s/countries/us.gif) Shadow Hawkins on Saturday, 20 December 2008 00:54:35
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:
Hi
I am getting the robot message and checked out the router. I'm not sure why you are unable to ping my router. The ping problem is reflected on your "loss" graphs.
I can successfully ping it from many different IPv6 points on the Internet. Below is a tcpdump on one such ping.
tcpdump -i tun6to4 -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun6to4, link-type RAW (Raw IP), capture size 96 bytes
02:21:35.207501 IP6 2a01:30:1000::53 > 2a01:348:6:174::2: ICMP6, echo request, seq 1, length 64
02:21:35.208125 IP6 2a01:348:6:174::2 > 2a01:30:1000::53: ICMP6, echo reply, seq 1, length 64
02:21:36.198063 IP6 2a01:30:1000::53 > 2a01:348:6:174::2: ICMP6, echo request, seq 2, length 64
02:21:36.198682 IP6 2a01:348:6:174::2 > 2a01:30:1000::53: ICMP6, echo reply, seq 2, length 64
I have also pinged the router from the other tunnel I have from yourselves, T16374.
There is no ipv6 firewall or any route filtering on this router. The default route is for all IPv6 traffic to go to the end-point of the tunnel, which is yourselves.
ip -6 route show
::/96 via :: dev tun6to4 metric 256 mtu 1280 advmss 1220
2a01:348:6:174::/64 dev tun6to4 metric 256 mtu 1280 advmss 1220
default via ::77.75.104.126 dev tun6to4 metric 1024 mtu 1280 advmss 1220
Any suggestions, as Iâm not sure why you would not be able to ping me given this all works from other locations.
Other connectivity is also working, for example ssh (port 222 for this router).
Kind regards
Andrew
-------------
Robot emails that tunnel is down - when actually tunnel endpoint pingable from sixxs and other ipv6 networks
'ip -6 route show' is a bit short don't you think? It is missing at least link-local routes and a lot of other details. Also, you have to route via the tunnel endpoint given, thus <tunnel>::1 which is the PoP. The ::/96 is also silly.
I also wonder about the name of this interface, why did you call it 'tun6to4', as SixXS doesn't do 6to4. We provide proto-41, proto-41/heartbeat and AYIYA tunnels, the first is what you chose. I can only assume that you took a configuration example of a 6to4 interface and thought that that would work for a proto-41 tunnel, they are different things.
We also really don't care that you can ping from somewhere on the Internet, especially as you are not showing a traceroute for it. We do care that the PoP at <tunnel>::1 can ping <tunnel>::2 and vice versa. Showing a ping from some random place on the Internet is thus useless as packets can just go through some random other route which is not the PoP.
As for suggestions, try to actually read the "Reporting Problems" section on the Contact page and of course read the FAQ and actually supply all the requested data.
State change: user
The state of this ticket has been changed to user
Robot emails that tunnel is down - when actually tunnel endpoint pingable from sixxs and other ipv6 networks
Shadow Hawkins on Saturday, 20 December 2008 19:55:33
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:
Jeroen
I was somewhat surprised by the tone of your reply. I was asking for help to resolve this problem, not a bunch of sarcastic comments.
I had clearly stated that I was using the Sixxs network as well as other end points to ping the router, and the tcpdump clearly indicated that the router was sending ICMP6 pings to which my router was replying.
True I could have given better routing information, and in reply all you needed to do was ask for more information.
Changing the default route on my end has fixed the problem, the tunnel name was a typo, and it was running proto-41.
I know the service is best effort and I and others appreciate that. However this sort of support email does not exactly endear users to your network....
Andrew
Robot emails that tunnel is down - when actually tunnel endpoint pingable from sixxs and other ipv6 networks
I was somewhat surprised by the tone of your reply.
Please actually read the contact page, we are not your friendly helpdesk, we are not psychics either. We cannot resolve your problem.
... the tcpdump clearly indicated that the router was sending ICMP6 pings to which my router was replying.
Doesn't say a thing as it doesn't show which route the packets take, or over which IPv4 path these things are going. We ask for these things for a reason.
However this sort of support email does not exactly endear users to your network....
We are not a "support" of any kind, this is clearly stated on the contact page.
Also this is a forum, it is not email.
You clearly do not read what we write in big yellow boxes, nor even take the time to read and remove the pre-filled text in the text box. We put all of that there for a reason. If you take the time to actually read that and follow the instructions given, then that makes our part much easier and then we might reply in a better fashion. As it seems everybody is ignoring that, we point directly to the FAQ and the contact page and ignore the rest. Simple.
|
![[ch]](/s/countries/ch.gif)
on Saturday, 20 December 2008 11:37:27
Posting is only allowed when you are