Lan clients not getting IP addresses
I have never had a problem until a storm just past. My Home PF has been running for years and is configured as such:
LAN - 192.168.1.1 it uses a lagg0 to connect to a managed switch 5224. I have 5 vlans connected to this lagg0. All Vlans are working and getting IPs and DNS? I can ping the host 192.168.1.1 Pfsense. I can configure and use the WebGui from all points of the network.
Only the parent (segment) 192.168.1.x machines are not getting an IP ? I have only a handful of machines on this segment Esxi(2) Dell R610, Switches(2) Dell 2816/5224. Both are failing on DHCP. These machines are static addresses assigned by PF DHCP.
For the life of me and all my searching I cannot understand this issue. I considered the lagg being an issue, but then how are all the other segments working fine? I cant see it being a switch issue as all the vlans on the switch are working? I even have port on the switch I can plug a PC into and it does not get an IP addresss? I static IP'd that PC and still cannot reach the anything. I pinged google from the PFSense using that network segment and I can reach the internet. I am totally not seeing why this is happening and is now a conundrum. I have reboot many times. brought a PF config restore prior to the storm. Any help or insight would be greatly appreciated.
PFsense Log on DCHP is showing multiple entries of these machines requesting IP and PFsense sending them ever second.
Dec 26 08:51:08 dhcpd DHCPOFFER on 192.168.1.8 to d4:be:d9:ad:b4:9e via lagg0
Dec 26 08:51:08 dhcpd DHCPDISCOVER from d4:be:d9:ad:b4:9e via lagg0
Dec 26 08:51:07 dhcpd DHCPOFFER on 192.168.1.6 to 18:03:73:f4:a4:27 via lagg0
Dec 26 08:51:07 dhcpd DHCPDISCOVER from 18:03:73:f4:a4:27 via lagg0
Dec 26 08:51:05 dhcpd DHCPOFFER on 192.168.1.8 to d4:be:d9:ad:b4:9e via lagg0
Dec 26 08:51:05 dhcpd DHCPDISCOVER from d4:be:d9:ad:b4:9e via lagg0
Dec 26 08:51:05 dhcpd DHCPOFFER on 192.168.1.7 to d4:be:d9:ad:b4:96 via lagg0
Dec 26 08:51:05 dhcpd DHCPDISCOVER from d4:be:d9:ad:b4:96 via lagg0
Dec 26 08:50:57 dhcpd DHCPOFFER on 192.168.1.6 to 18:03:73:f4:a4:27 via lagg0
Dec 26 08:50:57 dhcpd DHCPDISCOVER from 18:03:73:f4:a4:27 via lagg0
Dec 26 08:50:48 dhcpd DHCPOFFER on 192.168.1.7 to d4:be:d9:ad:b4:96 via lagg0
Sniff on the client - is it seeing the offer?
If so - why is it not accepting it?
@johnpoz thanks for responding, I assume "sniff" is referring to event log on the PC. The Applications and Services Logs/Microsoft/Windows/NetworkProfile log. There is a EventId 4004 "Network State Change Event" that fires whenever a network connection is made or re-identified. Not much details there. I cannot tell which interface these events are for. When I switch to LAN cable on my PC I get the bogus IP 169.x.x.x assigned. When I switch to wifi works fin. I disabled the PF Parent LAN interface DHCP and then I lost all connectivity in the backend, make sense as vlans are routing through the LAN via lagg. I restore to a point for the change and backend is back, parent lan dhcp/nor static still not working? Was I right on your sniff quote?
LAN cable on my PC I get the bogus IP 169.x.x.x assigned
That means it didn't get a dhcp..
Sniff - do a packet capture so you can actually see the dhcp traffic. If this is PC then you can for sure run wireshark on it.. Its free..
Then you can actually see what happens with the dhcp.. you would see the discover go out, and the offer come back, etc.
@johnpoz So if all the periph on that segment are not getting the 169.x.x.x then its got to be switch or PF. What sucks is I cannot access the switch via browsers, so a serial connection is the only option and I am not really that expert and I set it up some time ago. hmm.. also per pf log dchp discovery is going our every 3 seconds per periph.
Well you have a problem with your network if pfsense is seeing traffic on native no tagged interface.. And sending it back out untagged... But client doesn't get it..
Is pfsense running on virtual where you could be doing something odd with the tagging of vlans?
But yes if pfsense sending an offer - and your client never sees it or doesn't accept it.. That is not a pfsense issue.
@johnpoz sorry for the late response, but you are right. was not a pfsense issue, my switch Dell PC5224 first 12 ports got fried from the storm. I got it up and running with Dell PC6248 and working fine. Thanks for guiding me in the right direction.