• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

ssh

SSH on OSX Mojave failing with broken pipe error

Duncan Epping · Nov 26, 2018 ·

I recently upgraded my Macbook to OSX Mojave (10.14.1). Ever since I upgraded whenever I want to open an SSH session to any server on the internal (VMware) network I would receive the following error message:

packet_write_wait: connection to x.y.z. port 22: broken pipe

Very annoying as it made deploying labs in our dev cloud very complicated. I googled around and there were many suggestions on how to solve this, but none worked so far. A colleague today pointed me to thread on VMTN (surprisingly) which describes how to solve the problem. it is very simple, just add “ssh -o IPQoS=throughput” to your normal ssh command. So something like the following:

ssh -o IPQoS=throughput root@192.168.1.1

Thanks Alex for the pointer, and thanks Quinn for posting the solution on VMTN! Oh, and yes you can add the following to your ~/.ssh/config so that you don’t have the use the -o flag everytime:

Host *
IPQoS=throughput

Enable SSH on ESXi 4.1

Duncan Epping · Oct 3, 2010 ·

As, to my surprise, I still daily have 300/400 unique views on my article about how to enable SSH on ESXi 3.x I figured people would be interested in knowing how to enable it on ESXi 4.1. SSH is part of the TSM (Tech Support Mode) functionality. There are two different kind of Tech Support Modes:

  1. Local Tech Support (Commandline access)
  2. Remote Tech Support (SSH)

Enabling either of the two is really simple:

  • Open the ESXi console
  • Login(F2) and go to “Troubleshooting Options“
  • Now you will see options called “Tech Support”, hit “enter” on either Remote Tech Support (SSH) or Local Tech Support

You could of course also enable it through the vSphere Client:

  • Select the host and click the Configuration tab.
  • Click Security profile > Properties.
  • Click Local Tech Support or Remote Tech Support (SSH) and click Options.
  • Choose the desired startup policy and click Start, then click OK.
  • Verify that the daemon selected in step 3 shows as running in the Services Properties window.

mRemote 1.0!

Duncan Epping · Dec 28, 2007 ·

mRemote has just released version 1.0. For those who never heard of mRemote, it allows you to manage all your remote connections in a single place. It currently supports the RDP, VNC, SSH, Telnet, RAW, Rlogin, ICA and HTTP/S protocols. Pick it up at sourceforge.net.

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in