Hi,
I have two VMs running FreeBSD 9.1 and FreeBSD 7.3 on VMWare ESX Hypervisor. DHCP is enabled in both the VMs, but only the FreeBSD 9.1 is assigned a DHCP IP address. Note that I have other VMs too that run on the VMWare ESX, and all other VMs are assigned an IP address by the DHCP Server.
While FreeBSD 7.3 starts up, I see the following:
FreeBSD 9.1 configuration (IP assigned by DHCP):
FreeBSD 7.3 configuration (DHCP not activated):
/etc/resolv.conf doesn't exist. even if I place the same values as FreeBSD 9.1, the DHCPDISCOVER request still exists.
I have searched for this error online, but everywhere the problem was resolved with hardware replacement. Since in my setup I am using VMs, could anyone please give me pointers for troubleshooting this error?
Thanks.
Shehbaz
I have two VMs running FreeBSD 9.1 and FreeBSD 7.3 on VMWare ESX Hypervisor. DHCP is enabled in both the VMs, but only the FreeBSD 9.1 is assigned a DHCP IP address. Note that I have other VMs too that run on the VMWare ESX, and all other VMs are assigned an IP address by the DHCP Server.
While FreeBSD 7.3 starts up, I see the following:
Code:
DHCPDISCOVER on em0 to 255.255.255.255. port 67 interval 7
DHCPDISCOVER on em0 to 255.255.255.255. port 67 interval 14
DHCPDISCOVER on em0 to 255.255.255.255. port 67 interval 17
DHCPDISCOVER on em0 to 255.255.255.255. port 67 interval 14
DHCPDISCOVER on em0 to 255.255.255.255. port 67 interval 9
FreeBSD 9.1 configuration (IP assigned by DHCP):
Code:
# cat /etc/rc.conf
hostname="FreeBSD1"
ifconfig_em0="DHCP"
ifconfig_em0_ipv6="inet6 accept_rtadv"
sshd_enable="YES"
dumpdev="AUTO"
# cat /etc/resolv.conf
search abc.pqr.com
nameserver 10.60.132.40
nameserver 10.60.248.10
FreeBSD 7.3 configuration (DHCP not activated):
Code:
# cat /etc/rc.conf
hostname="FreeBSD73"
ifconfig_em0="DHCP"
ipv6_enable="YES"
keymap="us.iso"
sshd_enable="YES"
/etc/resolv.conf doesn't exist. even if I place the same values as FreeBSD 9.1, the DHCPDISCOVER request still exists.
I have searched for this error online, but everywhere the problem was resolved with hardware replacement. Since in my setup I am using VMs, could anyone please give me pointers for troubleshooting this error?
Thanks.
Shehbaz