Ticket ID: SIXXS #798140 Ticket Status: User PoP: deham01 - Easynet (Hamburg)
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
I cannot ping the PoP tunnel endpoint (no replies), but packets from their
endpoint arrive locally and are answered. However, it seems as if the replies
do not reach the tunnel endpoint as the status page reports 100% packet loss.
Also, Jeroen has verified that no packets arrive on the box.
I checked with the provider and they confirmed that the firewall ACCEPTs
everything, up- and downstream, including protocol 41.
I can reach the endpoint with IPv4 (tcp, icmp).
If I turn the tunnel to another machine, I (well, Jeroen) can see the packets
alright.
So it seems like something between 213.203.238.82 (2001:6f8:900:bb7::2) and
212.224.0.188 (2001:6f8:900:bb7::1) is dropping packets in one direction only.
After today's reboot of deham01, I could send exactly *one* packet (well,
I got a reply to exactly one echo-request), specifically the first one
I tried. I could not get another one in the hours since then.
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
I am leaving a ping6 running on the machine to 2001:6f8:900:bb7::1, in case that might help.
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
Actually, the machine is currently unreachable. Stay tuned...
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
Machine back and ping6 running.
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
This does seem like a weird local problem: I can send proto-41 to any IP out there up until the moment when this IP sends a proto-41 packet to me; from this point on, outgoing packets are blocked (it seems by 213.203.213.77), but incoming packets arrive fine.
State change: user
![]() ![]()
The state of this ticket has been changed to user
Outgoing packets seem not to reach PoP tunnel endpoint
Everything is fine for every other user, thus the only thing we can determine of this problem that it is somewhere between you and the PoP, but where exactly is unknown.
Outgoing packets seem not to reach PoP tunnel endpoint
![]()
It turns out that yes, in fact, the problem was an ISP PEBCAK. Unfortunately they just reloaded everything (sledgehammer approach) without trying to figure out the source.
|