Hi,
I'm using Workstation Player 12.5.2 build-4638234 (latest?) on an Ubuntu 16.04 (4.4.0-57-generic), with an Ubuntu 16.04 (same) guest. The wifi network I'm connecting to has a small (5 mins) DHCP lease time. (This setting is out of my control.) As a result, the host renews the DHCP config quite often (2-5 mins), and every time it does, the guest experiences a small network disconnect. This causes, for instance, a web browser running on the guest to often report pages as unavailable. This is very annoying, and it's something that doesn't happen with a browser running on the host. I'm trying to understand if there's a way to avoid such "hiccups". Specifically, why does the guest network adapter have to go down&up for every such event?? Thanks!
My detailed network settings are below:
- The host uses a wifi connection, managed by NetworkManager, with DHCP.
- The VM has 2 virtual network adapters, one NAT and one host-only. Both are set to use fixed IPs. The host-only adapter has no issues. Here is the config for the NAT adapter:
# /etc/vmware/vmnet8/dhcpd/dhcpd.conf
allow unknown-clients;
default-lease-time 1800; # default is 30 minutes
max-lease-time 7200; # default is 2 hours
subnet 192.168.71.0 netmask 255.255.255.0 {
range 192.168.71.128 192.168.71.254;
option broadcast-address 192.168.71.255;
option domain-name-servers 192.168.71.2;
option domain-name localdomain;
default-lease-time 1800; # default is 30 minutes
max-lease-time 7200; # default is 2 hours
option netbios-name-servers 192.168.71.2;
option routers 192.168.71.2;
}
host vmnet8 {
hardware ethernet 00:50:56:C0:00:08;
fixed-address 192.168.71.1;
option domain-name-servers 0.0.0.0;
option domain-name "";
option routers 0.0.0.0;
}
- In the guest, both adapters are set to use static IPs through NetworkManager:
# /etc/NetworkManager/system-connections/NAT\ Network
...
[ipv4]
address1=192.168.71.10/24,192.168.71.2
dns=192.168.71.2;
dns-search=
method=manual
...
- Here is what I see in syslog during DHCP renewal, apart from other NM-related messages:
On host:
Jan 3 10:51:23 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:53:27 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:55:52 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
Jan 3 10:57:56 daemon.info vmnet-natd: RTM_NEWADDR: index:3, addr:192.168.100.183
On guest:
Jan 3 10:51:25 kern.info kernel:[286522.503468] e1000: ens33 NIC Link is Down
Jan 3 10:51:31 kern.info kernel:[286528.515317] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:53:29 kern.info kernel:[286646.747963] e1000: ens33 NIC Link is Down
Jan 3 10:53:33 kern.info kernel:[286650.756319] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:55:53 kern.info kernel:[286791.025117] e1000: ens33 NIC Link is Down
Jan 3 10:55:57 kern.info kernel:[286795.059015] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jan 3 10:57:57 kern.info kernel:[286915.279562] e1000: ens33 NIC Link is Down
Jan 3 10:58:01 kern.info kernel:[286919.287363] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
