VMware Communities
jdege
Contributor
Contributor

Network is unreachable?

I'm running Workstation 8.0.1 on a Linux Mint 12.0 host (basically, it's Ubuntu, with some GUI changes).

I've been running a Linux Mint guest, under that, for some time, without difficulties.

Today, I was playing around with vmrun, trying to see if I could use it to suspend the Ubuntu guest.  Suspend and Start both seemed to work fine, except that when the guest came back up, it had lost the ability to connect to the network, Running ping from a command-line in the guest returns "connect: Network is unreachable".

I restarted the guest, then restarted the host and the guest, I reinstalled the VMware tools, all to no effect.

I had been running in Bridged mode, I switched to NAT, and still nothing.

I'm at a loss.  Any ideas?

Just as an update: I copied the .vmx from a backup, in case something had been changed.  No difference, networking was still disabled.

So I restored from backup, and that networking worked fine. Ran the current version again, and networking is still broken.

I'm at a loss as to what might have happened, but I'm thinking the best solution might be to copy off the files that have changed, and then do a restore.

0 Kudos
11 Replies
louyo
Virtuoso
Virtuoso

Does the network adapter (in the guest) show "connected"? You might try disconnecting and then reconnecting.

If so, what is the result of ifconfig -a in your guest?

Does it show the same subnet as your host?

Lou

0 Kudos
WoodyZ
Immortal
Immortal

louyo wrote: If so, what is the result of ifconfig -a in your guest?

Just an FYI... Nowadays with most Linux distros when no other arguments are given with -a, -a is implied and therefore it is not necessary as it will not output any additional information then ifconfig already does by itself. Smiley Wink

0 Kudos
jdege
Contributor
Contributor

On the guest:

10:23 PM job:1995> ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:56:3a:94:67 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:19680 (19.6 KB)  TX bytes:19680 (19.6 KB)

On the host:

eth0      Link encap:Ethernet  HWaddr 00:e0:4c:ec:0e:ec 
          inet addr:192.168.0.129  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:4cff:feec:eec/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17042 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16353 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13950218 (13.9 MB)  TX bytes:3324599 (3.3 MB)
          Interrupt:20 Base address:0xe800

eth1      Link encap:Ethernet  HWaddr 00:24:21:29:c4:ae 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:43 Base address:0xa000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5225 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5225 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:22603012 (22.6 MB)  TX bytes:22603012 (22.6 MB)

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:c0:00:01 
          inet addr:172.16.199.1  Bcast:172.16.199.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:27 errors:0 dropped:0 overruns:0 frame:0
          TX packets:643 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vmnet8    Link encap:Ethernet  HWaddr 00:50:56:c0:00:08 
          inet addr:192.168.8.1  Bcast:192.168.8.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:275 errors:0 dropped:0 overruns:0 frame:0
          TX packets:634 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

On the restored guest, where the networking works:

eth0      Link encap:Ethernet  HWaddr 00:0c:29:74:04:31 
          inet addr:192.168.0.130  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe74:431/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2031 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2482534 (2.4 MB)  TX bytes:279834 (279.8 KB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3936 (3.9 KB)  TX bytes:3936 (3.9 KB)

0 Kudos
WoodyZ
Immortal
Immortal

eth0 in the Guest is not UP, in a Terminal try the following command:

sudo ifup eth0
0 Kudos
jdege
Contributor
Contributor

I'd already tried "ifconfig eth0 up" and it did nothing.

"ifup eth0" returns "Ignoring unknown interface eth0=eth0".

0 Kudos
louyo
Virtuoso
Virtuoso

In Mint, what do you see for it in:

Control Center/Network ?

Lou

0 Kudos
WoodyZ
Immortal
Immortal

First of all while Linux Mint is base on Ubuntu nonetheless it is not an officially supported Host/Guest so it's not unreasonable to expect some issues, especially with VMware Tools.  That said, while I do have a Linux Mint VM I am not where I can access it however in an Ubuntu VM I have no problem using the following two commands to bring eth0 down/up.

sudo ifconfig eth0 down

sudo ifconfig eth0 up

These command clealy change the state of eth0 without error and I'd expect it to also work in Linux Mint however cannot confirm that at the moment.  I'd act just as if this was a Physical Machine and do the expected diagnostic/troubleshooting to see where the issue lies.

0 Kudos
jdege
Contributor
Contributor

They didn't work.  "eth0" isn't being recognized as a network.

It seems an odd result from doing a suspend.

Still, I've restored from backup, and things are working,  So while it would be nice to understand what went wrong, I'm not going to waste any more time on it.

Thanks, all, for the suggestions.

0 Kudos
knystol
Contributor
Contributor

Same issue on VMware Fusion 8.5 on a Debian9, I had to add default gateway:

ip route add default via 192.168.0.1 dev eth0

Replace that IP with your vmnet? shared network router IP.

0 Kudos
msam2020
Contributor
Contributor

I had the same problem. Here is what I did to fix:

  • # dhclient -r eth0
  • # dhclient eth0
Lonesurvivor112
Contributor
Contributor

This fixed it for me.

Why does this need to be set if the IP is static?

Tags (1)
0 Kudos