█████ ██ ███████ █████████

Oct 11, 2013 22:19

███ ██████████ ████ ██ ███ █████ ██ █████████ ██ █████████ ██ ███ ████████ ███████ ███ █████ ███ █████ ██████████████

█ ████ ████ ███████ █████████ ████ ██████████ ██ ██ ███████ ██ ██ █████ █ █████████ ████ ███ ███████ ██ █████ ███████ ██ ███████ █████████████ ██ █████ ██ ██ ███ ████ █████████████ ███ █ ████ ████ ██ ███ ██████████ ███ ████ ████ ██ ( Read more... )

linux

Leave a comment

Comments 2

captain_aj October 11 2013, 13:34:02 UTC
What kind of packets in particular are failing to route? Have you determined this using ICMP, or is it only with TCP connections? The reason I ask is that this sounds like the dreaded path MTU discovery problem where intermediate routers for certain destinations fail to be helpful (there's a solution involving clamping the MTU with iptables, but google is far more eloquent than I could ever be).

Reply

crazyscot October 11 2013, 23:17:58 UTC
At least TCP and ICMP (ping) are affected. I tend to notice when TCP stops working.

Reply


Leave a comment

Up