PFSense can't pull DHCP from cable modem ESXI 5.5
-
Guys I actually tried to deploy PF to a VM this weekend however I ran into problems. I have a Dell 2816 manged switch I have a trunk running to my ESXI 5.5 box. The system only has one virtual switch and I have port groups coming off of that vswitch with various vlan tags. So I configured the PF vm using the Intel E1000 driver and two virtual nics my problem is I can't get the wan interface of PF to DHCP from the cable modem. I think this is a Vmware problem because my current PF box is an old p3 750 with an Intel Pro 1000 MT nic using vlans for cable modem and other networks that I have. BTW if I hook up an old Linksys E2000 I have no problem pulling DHCP from the cable modem.
Oct 22 06:04:40 dhclient[7702]: No working leases in persistent database - sleeping.
Oct 22 06:04:40 dhclient: FAIL
Oct 22 06:04:40 dhclient: Starting delete_old_states()
Oct 22 06:05:56 dhclient: FAIL
Oct 22 06:05:56 dhclient: Starting delete_old_states()
Oct 22 06:06:06 dhclient[8405]: connection closed
Oct 22 06:06:06 dhclient[8405]: exiting.
Oct 22 06:06:07 dhclient: PREINIT
Oct 22 06:06:07 dhclient: Starting delete_old_states()
Oct 22 06:06:07 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 1
Oct 22 06:06:08 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:06:10 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:06:12 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 3
Oct 22 06:06:15 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 6
Oct 22 06:06:21 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 11
Oct 22 06:06:32 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 13
Oct 22 06:06:45 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 10
Oct 22 06:06:55 dhclient[88416]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 13
Oct 22 06:07:08 dhclient[88416]: No DHCPOFFERS received.
Oct 22 06:07:08 dhclient[88416]: No working leases in persistent database - sleeping.
Oct 22 06:07:08 dhclient: FAIL
Oct 22 06:07:08 dhclient: Starting delete_old_states()
Oct 22 06:07:23 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:07:25 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:07:27 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 4
Oct 22 06:07:31 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 5
Oct 22 06:07:36 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 7
Oct 22 06:07:43 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 21
Oct 22 06:08:04 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 11
Oct 22 06:08:15 dhclient[8658]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 9
Oct 22 06:08:24 dhclient[8658]: No DHCPOFFERS received.
Oct 22 06:08:24 dhclient[8658]: No working leases in persistent database - sleeping.
Oct 22 06:08:24 dhclient: FAIL
Oct 22 06:08:24 dhclient: Starting delete_old_states()
Oct 22 06:10:22 dhclient: PREINIT
Oct 22 06:10:22 dhclient: Starting delete_old_states()
Oct 22 06:10:22 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:10:24 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 4
Oct 22 06:10:28 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 7
Oct 22 06:10:35 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 7
Oct 22 06:10:42 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 14
Oct 22 06:10:56 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 8
Oct 22 06:11:04 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 17
Oct 22 06:11:21 dhclient[7380]: DHCPDISCOVER on em1 to 255.255.255.255 port 67 interval 2
Oct 22 06:11:23 dhclient[7380]: No DHCPOFFERS received.
Oct 22 06:11:23 dhclient[7380]: No working leases in persistent database - sleeping.
Oct 22 06:11:23 dhclient: FAIL
Oct 22 06:11:23 dhclient: Starting delete_old_states()
Oct 22 06:12:39 dhclient: FAIL
Oct 22 06:12:39 dhclient: Starting delete_old_states() -
And are you rebooting your cable modem once you connect something with a new mac? Most cable modems I have seen require a power cycle if you connect something with a different mac than what was connected before. Be this a pc, be it different router or the virtual interface in a pfsense vm.
What I do to get around the problem with switch vms that I wan to use as my gateway on my esxi 5.5 box is just use the same mac on the vms that I am going to connect to the vswitch that connected to the physical nic in the host that is connected to the cable modem. That way i shutdown on vm and bring up a new vm and never have to power cycle the cable modem.
-
Seems like it would not be a mac problem since I hooked up another router and it had no problem pulling an IP from the cable modem.
-
I was able to get it working by using virtual guest tagging basically I'm using the 802.1q driver inside of Pfsense. Also by doing this I basically removed the vswitch from the picture. However, this weekend I plan on trying to make it work via virtual switch tagging.
