* [MPTCP] insonsistend subflow creation policy ?!?
@ 2021-02-17 16:42 Paolo Abeni
0 siblings, 0 replies; only message in thread
From: Paolo Abeni @ 2021-02-17 16:42 UTC (permalink / raw)
To: mptcp
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hello,
I just noted that the pm_netlink subflow creation policy is
inconsistent (or perhaps simply different ?!?) between signal and
add_addr subflows.
When the MPTCP socket tries to create additional subflow due an
'subflow' endpoint, it will filter out local addresses already in use
by existing subflow.
When MPTCP tries to create an additional subflow due to an incoming
'ADD_ADDR' option, it will try to create it regardless any existing
subflow using the relevant remote address (and port).
Should we change the above ?!? (e.g. applying some filters even for
ADD_ADDR). Or perhpas add some additional policy flag (like 'unique' or
'none') ?
WDYT?
Thanks!
Paolo
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-02-17 16:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-17 16:42 [MPTCP] insonsistend subflow creation policy ?!? Paolo Abeni
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.