Upstreaming multipath TCP

Re:Upstreaming multipath TCP by yrro on Friday September 27, 2019 @02:50AM (#21089157)

This is how Linux still works by default, right? Behaviour that is quite surprising, at least it was to me when I discovered that it, in conjunction with many tools (e.g., docker) conveniently enabling up forwarding on all interfaces, unwittingly transforms multi-homed hosts into routers...

[ Parent | on HN ]

Re:Upstreaming multipath TCP by bogomipz on Friday September 27, 2019 @12:13PM (#21093521)

I don't think this is correct, it should be disabled by default(net.ipv4.ip_forward=0). At least it is in the major distros I'm familiar with. What distro are you using?

[ Parent | on HN ]

Re:Upstreaming multipath TCP by yrro on Tuesday October 01, 2019 @04:20AM (#21123181)

Distros disable it by default but it gets silently enabled when you install things like docker (and maybe livbirt) and so on.

At least Docker (as it was pointed out by a sibling reply to my comment) also sets the FORWARD chain policy to DROP.

[ Parent | on HN ]

Re:Upstreaming multipath TCP by bboreham on Friday September 27, 2019 @03:22AM (#21089329)

I believe Docker stopped doing that a couple of years back. Or it sets the default on the forward chain to drop.

[ Parent | on HN ]

Re:Upstreaming multipath TCP by yrro on Tuesday October 01, 2019 @04:17AM (#21123162)

You're right, something is setting the FORWARD chain policy to DROP and I guess it's docker.

[ Parent | on HN ]