SixXS::Sunset 2017-06-06

deham01 broken?
[de] Shadow Hawkins on Monday, 24 September 2012 11:17:00
Hi, it seems to me that deham01 has problems? I can reach the endpoint via icmp4. I also see encapsulated v6 packages being send to that endpoint IP but I do not get any reply? Cheers B
deham01 broken?
[ch] Jeroen Massar SixXS Staff on Monday, 24 September 2012 11:21:06
A traceroute or any other such thing would be so helpful in even remotely having something to look at.
deham01 broken?
[de] Shadow Hawkins on Monday, 24 September 2012 13:01:24
v4 trace: 1. 192.168.30.1 0.0% 10 0.6 0.7 0.4 2.5 0.7 2. 87.186.224.66 0.0% 10 18.0 17.9 17.2 18.9 0.5 3. 217.0.72.242 0.0% 10 18.0 18.1 17.7 18.6 0.3 4. f-ed4-i.F.DE.NET.DTAG.DE 0.0% 10 23.2 24.7 22.8 34.3 3.6 5. 80.150.168.62 0.0% 10 25.1 27.0 24.3 36.1 3.5 6. te3-1-0.gr11.kgham.de.easyne 0.0% 10 32.1 32.6 31.7 35.7 1.3 7. te3-1.111.br40.kgham.de.easy 0.0% 10 31.3 34.6 31.2 63.1 10.0 8. te3-2.br10.kgham.de.easynet. 0.0% 10 34.9 51.3 34.9 192.8 49.7 9. gi3-1-0.br10.noham.de.easyne 0.0% 10 33.6 34.1 33.3 35.6 0.7 10. gi1-7.cr10.noham.de.easynet. 0.0% 10 33.9 60.7 33.4 183.5 57.3 11. deham01.sixxs.net 0.0% 10 34.3 33.9 33.1 34.5 0.5 v6 trace not available as I get no v6 reply from that POP
deham01 broken?
[ch] Jeroen Massar SixXS Staff on Monday, 24 September 2012 13:05:15
That IPv4 traceroute only tells us that you are behind a NAT, thus hopefully you are using AYIYA and/or you have configured your DMZ correctly.
v6 trace not available as I get no v6 reply from that POP
Maybe you could start by providing details like how your tunnel is configured, what type it is etc? When you post there are these two big yellow/orange bars that point to the contact page's checklist, use it, it is there for a reason. Btw: deham01 is working fine

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

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