On 20210225, at 16:52, Jean-Pierre Schwickerath swinog@hilotec.net wrote:
Hi Jeroen
that "sinkhole" is just a misconfigured/internet-ignorant "load balancer": those things do not care about ICMP...
you are thus reaching the dest, it is just misconfigured: the Internet is just HTTP for many, they do not care about this TCP, ICMP or IP thing... be happy there is some kind of IPv6...
I wouldn't have noticed the issue if the loadbalancer / webserver had actually returned a webpage on port TCP/443. But it doesn't. So I tried from a different network to see if the issue is reproducible and that when I noticed the path taken by the traceroute packets.
Check with a tcpdump, don't forget to include ICMP.
Could also be an MTU issue or something on your side killing it.
Of course the behavior of the "load balancer" says quite a few things... sbb.ch is like that too...
Btw, when complaining about something, it is wise to include IP addresses, especially for the source...
The first hop of the traceroute is actually a good indicator for the source.
192.168.205.240 ?
DNS is ambiguous and reverses do not always match forwards. Including the actual IPs can thus be very useful...
That is, if you actually want it resolved.
You might want contact swisscom directly (good luck with that) or at least your ISPs that provide the connectivity, they might have better chance at contacting them. (taking transit over swissix is a fun one; but yea it is not that swisscom likes to peer, what else would a monopoly do)
Greets, Jeroen