I recently upgraded to Xubuntu 13.04 from 12.10, which required uninstalling and reinstalling VMWare Player for Linux. Soon after (not exactly sure the timing) I lost network connectivity on my host Xubuntu machine.

I have both Virtualbox and VMWare player installed, so I'm guessing that's why I have two vmnet entries.

On my host I can sometimes (seems to come and go) ping DNS (8.8.8.8) but never anything else (such as www.google.com). I've tried a number of things to no avail.

Is it a problem that vmnet1 has IP addr 192.168.254.1, which is on the same network as eth1 (192.168.254.27)? Is that interfering with eth1 and blocking network connectivity? Should vmnet1 be on a different internal network, like 10.x.x.x?

If so, how do I change it?

[Update]
Here is more information based on what @slm asked:

I can't say for sure, but it seems to me that it used to eth0. Not sure when it changed.

Here are a few more things I checked:

$ ls -d /sys/class/net/eth*
/sys/class/net/eth1

I don't much about modprobe, but someone suggested doing this:

$ modprobe -c | grep 'eth[0-9]'
blacklist eth1394

Not sure what that means.

Finally, on your question about /etc/udev/rules.d/70-persistent-net.rules. I actually have four entries, not sure why as it seems I have only one NIC (based on running sudo lshw -class network and above info)

vmnet1 & vmnet8 belong to vmware. 1 is for the host only network, 8 is for the NAT network.
–
slm♦Jun 13 '13 at 2:20

try to reconfigure network interface. you can do this by using system-config-network-tui utility
–
RazaJun 13 '13 at 3:23

@Salton I don't seem to have this command installed (only system-config-printer). Xubuntu usually suggests a package for uninstalled things, but not in this case. This note says it doesn't exist for Ubuntu systems: serverfault.com/questions/336231/…
–
quux00Jun 13 '13 at 22:00

@slm So it's not a problem that eth1 and vmnet1 on are the same subnet? That's not causing the issue?
–
quux00Jun 13 '13 at 22:16

The issue is that eth0 is getting setup incorrectly. eth1 shouldn't be there. See my edit to my answer and try the suggestions.
–
slm♦Jun 14 '13 at 3:49

2 Answers
2

It seems odd that your ethernet device is eth1 and not eth0. Do you recall if your ethernet device was eth0 previously? I would suspect that when you upgraded something happened with your udev rules.

Assuming you have only a single ethernet NIC in your system, check this file and make sure that there is only a single entry in it:

# /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# net device () (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="54:52:00:ff:ff:dd", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

You should only have a single SUBSYSTEM line at the end of this file. If you have more you'll need to delete any extra lines and make sure the one that remains is correct in terms of the MAC address it's specifying.

EDIT #1

Based on the OP's feedback on his file: /etc/udev/rules.d/70-persistent-net.rules, I'd make the following changes:

EDIT #2

Did you try re-installing it yet? Vmnet1 is suppose to be a local network just for the VMs and the host they're running on. I suspect what's going on is that the IP address that is getting used by your vmnet1 is also used by another system on your LAN causing a conflict. Take a look at this tutorial, titled: VMWare Interfaces Tutorial.

Specifically check out the section on Host only Network connection. This diagram from that tutorial shows a similar setup to what you're reporting.

So the problem would seem to be that your original eth1 device's IP address (192.168.254.27) and the IP address/subnet being used by vmnet (192.168.254.1) were conflicting because the routing local to your host was probably getting setup with conflicting routing.

There were probably entries that were routing traffic destined for a particular IP address to multiple locations, which isn't allowed.

See my updated info in the question section. I have entries for both eth0 and eth1 (and wlan0 and wlan1). Is it a problem to have eth1 mapped to my NIC? If so, how do I map eth0 to it instead?
–
quux00Jun 13 '13 at 22:08

See my edits, I believe you can make those changes and restart your network. You should see that eth0 should come up and get an IP address.
–
slm♦Jun 14 '13 at 3:48

I made the change and it did change my system to use eth0, rather than eth1, so that's good and thanks for that. However, it didn't solve the problem. Only after I uninstalled VMWare Player was my host network connectivity restored, so it was that conflict as I originally suspected.
–
quux00Jun 15 '13 at 1:58

1

@midpeter444 - glad you resolved your issue. I've updated my answer with more details. If you want to read up more on VMWare networking I've included a link to a good tutorial on it.
–
slm♦Jun 15 '13 at 2:45

The answer to my question was "yes" - VMWare was hosing my host network connectivity because it was on the same 192.168.x.x network. That was leading to incorrect routing. I uninstalled VMWare, telling it to remove all existing configurations (after backing up my guest images) and reinstalled. After reinstallation my host network continued to function and VMWare worked correctly (ie., I could boot guests and access the internet, etc.). So all is good now.