This bug was fixed in the package openssh - 1:7.9p1-10
---
openssh (1:7.9p1-10) unstable; urgency=medium
* Temporarily revert IPQoS defaults to pre-7.8 values until issues with
"iptables -m tos" and VMware have been fixed (closes: #923879, #926229;
LP: #1822370).
-- Colin
** Changed in: openssh (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client broken pipe
Sta
** Also affects: openssh (Ubuntu Disco)
Importance: Critical
Assignee: Colin Watson (cjwatson)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1
@jsavanyo: Thanks for following up! The iptables-related part of the
discussion may yet yield an openssh packaging change; we'll see.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.n
@paelzer: A day is a bit soon to be stressing about lack of feedback, I
think. We have time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta open
VMware bug 2319367 was closed as a duplicate of bug 2275007 which was
closed as a duplicate of bug 2201049. Good news is that bug 2201049 is
fixed in a future unreleased version of Workstation and Fusion. I'm not
aware of a plan to back port fix to maintenance patch yet. I will ask.
--
You rec
No feedback on the Debian ML [1] yet, how do we go on with this knowing
that our Freeze is in 8 days?
@CJwatson - are you going to drive that in Debian according to Feedback (or the
lack thereof) to your mail and then sync it to Disco in time?
For now I'll assume so - no offense please, I just ne
The internal VMware bug 2319367 I created was closed as a duplicate of
bug 2275007
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client
This is Workstation and Player 15 I do not have ability to test on ESXi
I am using VMnet8
On 4/2/19 1:30 PM, John Savanyo wrote:
> Can someone clarify, what VMware products is this know to affect
> (vSphere/ESXi or Workstation/Fusion) and what versions? Also what
> virtual NIC is used in the VM?
Can someone clarify, what VMware products is this know to affect
(vSphere/ESXi or Workstation/Fusion) and what versions? Also what
virtual NIC is used in the VM?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubunt
I created internal VMware bug 2319367 to track looking into this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client broken pipe
Stat
Just to be prepared I added an MP for this at [1].
But I agree to cjwatson that we should (if possible) either revert this in
Buster+Disco or none of them to not split up the behavior of different releases
even more.
Never the less, one might want to peek at the change and or play with the PPA
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/365396
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Ti
FYI - Up for discussion in the scope of Debian-Buster at [1].
[1]: https://lists.debian.org/debian-devel/2019/04/msg00010.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: openssh (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client broken pipe
Status i
I filed this bug at Debian as well => https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=926229
** Bug watch added: Debian Bug tracker #926229
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926229
** Also affects: openssh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926
Colin was so kind to also find this reference [1] in Debian.
Which asks about the same revert, but not yet for it affecting VMWare - instead
it seems it also conflicts with "iptables -m tos" as well.
I'll bring it up with VMWare, but if also conflicting with some iptables
options that would be on
Until resolved - as a landing page (I'll put that in the description as well):
The summary for the workarounds for now is:
You can configure your /etc/ssh/ssh_config permanently
Host *
IPQoS lowdelay throughput
Or per command via:
$ ssh -o IPQoS=throughput user@host
---
Per the other bugs
@Frank - that is good for you and thanks for confirming my assumptions.
But it is unfortunate for openssh :-/
** Bug watch added: github.com/hashicorp/vagrant/issues #10730
https://github.com/hashicorp/vagrant/issues/10730
--
You received this bug notification because you are a member of Ubun
I don't want to revert this as that just takes the pressure off VMware;
ultimately this is their bug that they need to fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/182
Thanks for the responses Christian.
This client does indeed run in VMware, VMware Player 15
Running it using /ssh -o IPQoS=throughput user@host /and it functions
correctly on multiple hosts.
On 4/1/19 4:30 AM, Christian Ehrhardt wrote:
> Interesting and maybe related
>
> https://communities.vm
@cjwatson - I subscribed you as you usually look after ssh(d) - have you
heard about that issue before or have any special recommendation
already?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs
Interesting and maybe related
https://communities.vmware.com/thread/590825
https://github.com/vmware/open-vm-tools/issues/287
https://bugzilla.redhat.com/show_bug.cgi?id=1624437
The TL;DR of those is that VMWare would have issues with the AF21 QoS flag.
Does your client run in VMWare by chance?
Maybe the keepalive defaults got changed?
All past references to the issue refer to some sort of keepalive to avoid the
issue.
For example [1]
Be aware that some suggestions on [1] configure the sever, while your
issue is on the client side (at least that is where the upgrade
happened.
You could
Running the echo command on those hosts gives me: SSH-2.0-OpenSSH_7.6p1
Ubuntu-4ubuntu0.3
Protocol mismatch.
I can ping those hosts
If I use the linux version of putty on the system I can ssh into those
hosts
Not seeing anything related in dmesg
On 3/29/19 2:33 PM, Seth Arnold wrote:
> Hello,
Hello,
Are there any messages in dmesg that look related? Can you ping those
hosts? Do you get ssh banners if you run:
echo "" | nc x.x.x.x 22
?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
htt
26 matches
Mail list logo