stop using the public IP address for SSH connections to VMware guests

we've been setting `vmware.ssh_info_public = true` as an workaround to what turned to be hashicorp/vagrant#10730. we're now getting around this issue following the upstream suggested way - disabling `IPQoS` on guest's sshd side. Signed-off-by: António Meireles <antonio.meireles@reformi.st>
AntonioMeireles · Mar 24, 2019 · 537cec0 · 537cec0
1 parent e500712
commit 537cec0
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/Vagrantfile.template.rb b/Vagrantfile.template.rb
@@ -40,8 +40,6 @@
     config.vm.provider(vmware_provider) do |vmware|
       vmware.whitelist_verified = true
       vmware.gui = !headless
-      # FIXME: only way to behave past 24950 ...
-      vmware.ssh_info_public = true
 
       {
         'cpuid.coresPerSocket' => '1',

diff --git a/builders/template/etc/ssh/sshd_config b/builders/template/etc/ssh/sshd_config
@@ -8,3 +8,7 @@ AuthorizedKeysFile %h/.ssh/authorized_keys
 # 120s/60m
 ClientAliveInterval 120
 ClientAliveCountMax 30
+
+# XXX: workaround for https://github.com/hashicorp/vagrant/issues/10730
+# drop when fixed
+IPQoS lowdelay throughput