System has been working smoothly in a light duty web development/testing setting. Various clients, win, freebsd, linux, rarely more than one running at a time.
-
Until Today
Client installs have been fairly smooth, ( sometimes need custom vm, and choose specific scsi driver).
Client Networks, Bridged, Host, & Nat are all used daily and all work.
***Note: On some linux clients the first interface found is always eth1, eth0 device can't be found, but networking, whether Bridged, Host or Nat, still works fine.
-
NOW
Host and Nat work perfectly. No Bridged networks work. No packets seen. Interface works normally, but as if unplugged.
Turned off host firewall, turned off host selinux policies, re-ran vmware-config, un-installed vmware and re-installed. Always the same result, Host and Nat work perfectly. No Bridged networks work. No error messages reported in host /var/log/vmware or on client.
Single or multiple virtual eth cards, same result. Two virtual eth's, one on Host, one on NAT, both work, move one to bridge - no connection.
Assign client eth to bridge, looks fine, but won't dhcp. Manually assign an address, can ping itself but can't get out. Tcpdump on host sees no packets or arp.
Have been running vmplayer and vmserver successfully on Mandriva2007spring, Ubuntu7.04, F7 without vmware-any-any patches.
Are the vmware-any-any patches still recommended?
Anyone else seeing this bridge behavior on F7?
Answer found: http://communities.vmware.com/thread/46069
Changed mac addresses in .vmx
Remove /etc/udev/rules.d/ files containing old mac address
Created new /etc/iftab with new mac address
Modified /etc/network/interfaces to new ip addresses
Reboot vm client
*Answer found: http://communities.vmware.com/thread/46069
This pertains to moving clients to different hosts. This client issue was on the same box. I do dual boot and access the same vm's from either WinXP or various linux distros, usually with no problems. Perhaps the dual boot caused the issue?