You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Solution
I guess just showing [C] is too vague, maybe deny-join?
Considered alternatives
Note that Wireshark and ptcpdump displays the info correctly.
Description
As described in the RFC, the C flag is an important info to display:
But for the moment, it is not.
Solution
I guess just showing
[C]
is too vague, maybedeny-join
?Considered alternatives
Note that Wireshark and ptcpdump displays the info correctly.
Additional context
Thanks to @majek for having reported this.
The text was updated successfully, but these errors were encountered: