Matthieu Baerts
Matthieu Baerts
@jtzero thank you for having looked at this! This appears to work on GNOME Shell 48 as well.
@Agent-Hellboy thank you for having reported the issue upstream, and suggested a solution. Sadly, it looks like the discussions have stall. By chance, are there any workarounds that could be...
Hello, As a temporary workaround, you can force Go apps creating stream listening sockets not to use MPTCP by setting `GODEBUG=multipathtcp=0` env var.
> The default route is `via 192.168.13.1 dev enp3s0.3`. > > I've set up the subflow I want to use: > > ``` > $ sudo ip mp e >...
In other words, if you added the correct interface with the endpoint, you should not need to add these rules. That's what is mentioned in the 'warning' box: https://www.mptcp.dev/pm.html
Hi Saki, Sorry for the delay, it looks like we missed the issue. > But if I disconnect one interface and add it back as mptcp endpoint the IPv6 endpoint...
> The default behaviour on my laptop is that Network Manager (Version 1.42.4 ) creates the endpoints. Nice, I didn't know it was enabled by default. > connection.mptcp-flags: 0x0 (default)...
> Sorry for the delay. No problem! > > By chance, did you try by setting a different MPTCP endpoint ID? Maybe the ID is still marked as used by...
> And after the reconnect the IPv6 gets a new subflow ID. I think I'm a bit lost. Just to be sure: - you have 2 interfaces, each with one...
One last thing, if you have: - server: - endpoint signal v4 - endpoint signal v6 - client: - endpoint subflow v4 iface 1 - endpoint subflow v6 iface 1...