Post #224857
2026-02-02 22:57 UTC
@TechSupport@equestria.social I'm gonna buy you whatever drink you would like if we ever meet.
The first packet that doesn't return is supposed to be ~4200 bytes large! It does seem to be a fragmentation issue.
And it's possible that Azure's load balancer or proxy or something really likes to send large packets that break the connection, which would explain the subnet specificity.
Replies (1)
-
@Karcsesz@equestria.social 2026-02-03 00:03
@TechSupport@equestria.social Adding a mangle rule that clamps MSS seems to have fixed it. For some reason linux sends higher than advisable MSS to some hosts and I guess pmtud is getting swallowed from that subnet so it can't correct itself? This is all still very fresh knowledge to me so correct me if I'm being a dumbass xP