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
The goal is to change the TTL in the IPv4 header and in the corresponding v6 option.
As discussed at the last meeting, the best for the sockopt is probably to propagate the info to all new subflows by default except there is a technical issue. If needed, BPF can be use to unset stuff.
The text was updated successfully, but these errors were encountered:
This adds support for IP_TTL and IPv6_UNICAST_HOPS, the IPv6 equivalent.
The socket option is propagated to all subflows by default.
Closes: multipath-tcp#296
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
matttbe
added a commit
to matttbe/mptcp_net-next
that referenced
this issue
Jul 13, 2023
This adds support for IP_TTL and IPv6_UNICAST_HOPS, the IPv6 equivalent.
The socket option is propagated to all subflows by default.
Closes: multipath-tcp#296
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
matttbe
added a commit
to matttbe/mptcp_net-next
that referenced
this issue
Jul 13, 2023
This adds support for IP_TTL and IPv6_UNICAST_HOPS, the IPv6 equivalent.
The socket option is propagated to all subflows by default.
Closes: multipath-tcp#296
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
It is currently unsupported.
The goal is to change the TTL in the IPv4 header and in the corresponding v6 option.
As discussed at the last meeting, the best for the sockopt is probably to propagate the info to all new subflows by default except there is a technical issue. If needed, BPF can be use to unset stuff.
The text was updated successfully, but these errors were encountered: