Page 1 of 1
Broken pipe on ssh
Posted: 2. May 2015, 19:18
by TechFreak
I have a windows 7 host on which I have installed Virtualbox. I have tried installing several versions of Ubuntu and even choosing a different version of Virtualbox. Whenever I ssh from the guest OS terminal, there is a momentary break in network causing a broken pipe. I have tried adding the line ServerAliveInterval 10,30,60 in my ssh_config but the network still breaks. I don't know what else to do. Please help.
Thanks
TF
Re: Broken pipe on ssh
Posted: 2. May 2015, 19:31
by Perryg
Re: Broken pipe on ssh
Posted: 2. May 2015, 19:52
by TechFreak
Here are the details:
VirtualBox version: 4.3.22
VBoxGuestAdditions installed
Host: Windows 7 64 bit, Available Memory- 61.8 GB
Guest: LUbuntu 14.04 - 64 bit , Base Memory- 512 MB
I don't know where to run the VBoxManage commands from? Please let me know if any other information is required.
Re: Broken pipe on ssh
Posted: 2. May 2015, 20:06
by Perryg
This seems to be your issue:
Code: Select all
00:01:29.443721 NAT: link down
00:01:34.568977 NAT: link up
00:01:34.584275 NAT: DNS#0: 137.138.16.5
00:01:34.584313 NAT: DNS#1: 137.138.17.5
00:04:17.796245 NAT: link down
00:04:24.370075 NAT: link up
00:04:24.374393 NAT: DNS#0: 137.138.16.5
00:04:24.374411 NAT: DNS#1: 137.138.17.5
00:04:25.442818 NAT: DHCP offered IP address 10.0.2.15
00:12:31.917044 NAT: link down
00:12:36.917670 NAT: link up
00:12:36.921905 NAT: DNS#0: 137.138.16.5
00:12:36.921931 NAT: DNS#1: 137.138.17.5
00:12:38.396568 NAT: DHCP offered IP address 10.0.2.15
00:29:21.473242 NAT: link down
00:29:26.473665 NAT: link up
00:29:26.476969 NAT: DNS#0: 137.138.16.5
00:29:26.476985 NAT: DNS#1: 137.138.17.5
00:29:28.434457 NAT: DHCP offered IP address 10.0.2.15
00:29:40.516671 NAT: link down
00:29:47.482482 NAT: link up
00:29:47.486030 NAT: DNS#0: 137.138.16.5
00:29:47.486044 NAT: DNS#1: 137.138.17.5
00:29:48.520234 NAT: DHCP offered IP address 10.0.2.15
VirtualBox has been working on the network stack for a few versions, (adding ipv6 and better driver support) unfortunately this has caused issues. You can downgrade to 4.3.12, install the latest drivers for your host, or try the version 5.0.* beta version to see if it fixes your issue.