RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:27:ae:b0:9b Iface lo inet loopback # The primary network interface My set up is a s follows, adapter 1 => host-only (intel pro/1000 T server (82543GC)Īdapter 2 => NAT (intel pro/1000 T server (82543GC)Īdapter 3 => bridged (intel pro/1000 T server (82543GC) //bridged to : Īdapter 4 => bridged (intel pro/1000 T server (82543GC) // bridged to : ħles # PCI device 0x8086:0x100f (e1000) The local IP's 192.168.56.x refuse connection as well.Īfter 3 days and multiple re-installs I still cant get this thing to do a basic config as I had it working before, any help is appreciated, I can start a session on adapter 4 as soon as ssh requests Log in it terminates connection and will not re engage. I can now ssh in via a dhcp address on adapter 3 (192.168.20.104), DNS seems to work fine with apt-get fetching. So I did a little digging and deleted the les, rebooted and now a different permutation. Initially I could ssh into 192.168.56.112, however an apt-get returned network un-reachable. However on restart I am having problems with the networking. The build went find with the guest fetching all required dependencies from the web no problem. I have duplicated the previous build from a deb amd64 business card iso. vdi crashed and could not be re-imported, so I downgraded to 4.1.4 that was working fine. Firstly, I had a stable VM working fine, then upgraded to the latest virtualbox edition and things went bad.
0 kommentar(er)
