[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: vmware - lost in a fog of ambiguity

On Sun, 12 Mar 2006, Les Mikesell wrote:

On Sun, 2006-03-12 at 18:49, Matthew Saltzman wrote:

Folowing myself up: VMware runs its own dhcp server for the vmnet
interfaces.  See /etc/vmware/ for the config files (created by

The vmnet? devices are added to the host (physical) machine when
you run the configure script.  vmnet8 is the one used for NAT
connections.  I think vmnet1 is for host-only - I usually don't
configure that.  I don't think either would use a 172.x.x.x
range unless you specifed that during the configure run.

That's right, but vmnet1 and vmnet8 addresses are served to the virtual machine by VMware's dhcp server. I did nothing to get the following except run vmware-config.pl. vmnet8 is similar but also has a nat subdirectory with a config file in it.

I don't recall what the default subnet is if you don't configure one. I selected 192.168.20.x myself. IIRC, 172.x.x.x are the class-B nonroutable networks. If so, it wouldn't be an unreasonable default choice.

$ more /etc/vmware/vmnet1/dhcpd/dhcpd.conf
# Configuration file for ISC 2.0b6pl1 vmnet-dhcpd operating on vmnet1.
# This file was automatically generated by the VMware configuration program.
# If you modify it, it will be backed up the next time you run the
# configuration program.
# We set domain-name-servers to make some DHCP clients happy
# (dhclient as configued in SuSE, TurboLinux, etc.).
# We also supply a domain name to make pump (Red Hat 6.x) happy.
allow unknown-clients;
default-lease-time 1800;                # 30 minutes
max-lease-time 7200;                    # 2 hours

subnet netmask {
    option broadcast-address;
    option domain-name-servers;
    option domain-name "localdomain";


		Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]