Quad on Nostr: lamp fairly certain linux should handle that. But a response won't always go the same ...
lamp (nprofile…ey9f) fairly certain linux should handle that. But a response won't always go the same path through which it was received. It seems more likely to me that the packet from the container reaches the host, but due to some network config on the host it's the one that's struggling to reply.
When I've seen this kind of issue at work, 90% of the time it's been wrong route on one side, so the first packet probably makes it, the host replies via a different path, but that packet doesn't make it, so after a while it retries and this time the packet arrives, so it remembers the second path for the duration of the connection.
Also you haven't broken TCP, TCP doesn't care about this afaik. IP does routing decisions for each packet independently. So if anything is broken here it's IP
When I've seen this kind of issue at work, 90% of the time it's been wrong route on one side, so the first packet probably makes it, the host replies via a different path, but that packet doesn't make it, so after a while it retries and this time the packet arrives, so it remembers the second path for the duration of the connection.
Also you haven't broken TCP, TCP doesn't care about this afaik. IP does routing decisions for each packet independently. So if anything is broken here it's IP