Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/multipath-tcp/mptcp_net-next/issues/535 below:

display `MP_CAPABLE` C flag · Issue #535 · multipath-tcp/mptcp_net-next · GitHub

As described in the RFC, the C flag is an important info to display:

The third bit, labeled "C", is set to 1 to indicate that the sender of this option will not accept additional MPTCP subflows to the source address and port, and therefore the receiver MUST NOT try to open any additional subflows toward this address and port. This improves efficiency in situations where the sender knows a restriction is in place -- for example, if the sender is behind a strict NAT or operating behind a legacy Layer 4 load balancer.

But for the moment, it is not.

I guess just showing [C] is too vague, maybe deny-join?

Note that Wireshark and ptcpdump displays the info correctly.

Thanks to @majek for having reported this.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4