Specifications

CHAPTER 7 Networking
257
If, however, the processes are running because they supply routing information, then
you need to configure them so they do not advertise routes to the host-only network.
Unfortunately, the version of routed that comes with many distributions of Linux
has no support for specifying that an interface should not be advertised. Consult the
routed(8) manual page for your system in case you have a more contemporary
version of the software.
The gated process requires some configuration. You need to explicitly exclude the
VMnet1 interface from any protocol activity. If you need to run virtual machines on a
host-only network on a multihomed system where gated is used and have
problems doing so, please contact VMware technical support by submitting a
support request at www.vmware.com/requestsupport.
Other Potential Issues with Host-Only Networking
on a Linux Host
The following are common issues you may encounter when you are configuring a
host-only network.
DHCPD on the Linux Host Does Not Work After GSX Server Installation
If you were running the DHCP server program dhcpd on your machine before
installing GSX Server, it probably was configured to respond to DHCP requests from
clients on any network interface present on the machine. When host-only networking
is configured, an additional network interface, VMnet1, is marked “up” and available
for use, and dhcpd may notice this.
In such cases, some dhcpd implementations abort if their configuration files do not
include a subnet specification for the interface — even if dhcpd is not supposed to
respond to messages that arrive through the interface.
The best solution to this problem is to add a line in the following format to the dhcpd
configuration file:
subnet <net>.0 netmask 255.255.255.0 {}
<net> is the network number assigned to your host-only network — for example,
192.168.0. This configuration file entry informs dhcpd about the host-only network
and tells it explicitly not to respond to any DHCP requests it sees coming from it.
An alternative solution is to explicitly state the set of network interfaces that you want
dhcpd to listen to each time you start the program. For example, if your machine has
one Ethernet interface, eth0, then each time you start dhcpd, list it on the
command line:
dhcpd eth0