[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1055259: marked as done (please include MPTCP patch)



Your message dated Fri, 3 Nov 2023 00:24:31 +0100
with message-id <6ytubchykpkacgmz2xqhrourql32x3jdluhj2zzzeqfuhrdkov@muzq5ajbalia>
and subject line 
has caused the Debian Bug report #1055259,
regarding please include MPTCP patch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1055259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055259
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:9.2p1-2+deb12u1
Severity: wishlist

Hi,

MPTCP support has been available in a pull request against upstream for a while:

  https://github.com/openssh/openssh-portable/pull/335

Unfortunately, upstream does not want it because OpenBSD doesn't support MPTCP.
Would it be possible for Debian to pull it in? I believe network-manager and
everything else should be MPTCP-ready now, giving you essentially mosh-like
roaming straight out of the box. The patch is essentially only adding an option
to change from IPPROTO_TCP to IPPROTO_MPTCP and then add some documentation.


-- System Information:
Debian Release: 12.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.10 (SMP w/56 CPU threads; PREEMPT)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_NO:en_US:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
OK, I actually tested this (fixing the merge conflicts was easy), and this
was less interesting than I'd thought; evidently, you can't hop from one
network to the other and have it work, you'd need to be on both networks
at the same time. So it's not a mosh replacement. (Also, it doesn't seem
to support the TOS setsockopt() for IPv6, so you get warnings.)

Closing for now.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

--- End Message ---

Reply to: