Summary: | vmware-server retains old network address | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Humphrey <peter> |
Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Humphrey
2008-07-16 09:31:48 UTC
Hiya Peter, First off, I'd suggest dealing with one network adapter at a time. Start up the vmware machine and then disable one or the other of the networks and tests how it works. You haven't quite provided enough information to figure everything out. You said you changed the address of both connections, but you can't change the address of a bridge, because it's a bridge. Each individual machine making use of the bridge will need its IP address changing, or the DHCP server handing out address will need to be reconfigured. Which method are your client machines using on the bridged interface to get an IP address? Static or dynamic? After you've verified that the bridged connection is only doing exactly what it's supposed to, swap over to the host-only connection, and again test it in isolation. Put wireshark on both the client and host, and see what traffic the client's seeing, what traffic the host's seeing, and whether your 192.168.129.x packets are originating on the client or not. You said the windows boxes IP was correct, so how is this likely to be a vmware issue? If the client thinks it has the correct address, the server thinks it has the correct address, and there's no NATing going on, vmware isn't going to touch any of the packets... I'm really not convinced this is a package issue, but more of a configuration issue. Given how much complexity is going on (your network's, the vmware client's setup, the host machine's setup and the vmware-server config itself) I'm fully expecting this to be configuration related and not code related. If you're just asking for advice, you'd be best off consulting on the Gentoo forums, the gentoo-user mailing list, on IRC, or on the Vmware Technology Network (VMTN) forums, rather than filing a full fledged bug about the package itself. Sorry I can't be of more help, but bugzilla is not a user support resource... Please let me know how you get on, but I'm going to mark this bug as NEEDINFO, meaning I'll need you to either track down exactly where the failing in vmware server is or it's going to stay closed I'm afraid... 5:( |