DHCP Server failing for some reason



  • Hello,

    Using Pfsense 2.1.5 running DHCP on our guest network.  Was working after initial setup, but now is failing for some reason.  Here are the recent log entries

    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Sending on Socket/fallback/fallback-net
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Sending on BPF/em2_vlan40/00:30:18:c2:bd:33/192.168.40.0/24
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Listening on BPF/em2_vlan40/00:30:18:c2:bd:33/192.168.40.0/24
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Wrote 2 leases to leases file.
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: All rights reserved.
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Copyright 2004-2014 Internet Systems Consortium.
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Internet Systems Consortium DHCP Server 4.2.6
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: All rights reserved.
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Copyright 2004-2014 Internet Systems Consortium.
    Jul 8 16:06:08 rtr-mel-cr-001 dhcpd: Internet Systems Consortium DHCP Server 4.2.6

    I executed the followingsteps from these 2 posts, but neither worked for me.

    https://forum.pfsense.org/index.php?topic=34829.0

    https://forum.pfsense.org/index.php?topic=64337.0

    Can someone help me understand why this is failing?

    Cheers



  • Well, on the basis of the information given it could be pretty much anything. The log file shows no obvious errors I can see. How do you know it's failing? Have you checked to see  whether the DHCP service is running? Is this happening to just one or two clients or is every client connecting to the network failing to pick up an address? If it was working to start with, was anything changed between then and now? Have you checked your firewall rules to be sure you haven't blocked DHCP traffic from reaching your LAN? Could there be an issue with the client machine(s)?

    With no other information to hand, vague suggestions are about all I can offer.



  • You might be right, muswellhillbilly.  My ignorance with some of this is easily shown.  For my own reference, could you give me an explanation of what "dhcpd: Sending on Socket/fallback/fallback-net" indicates?  I have 3 APs that are the same model, firmware, etc. All have the same SSIDs.  I bounce from the closest two APs to the one that has the weakest signal, which I end up staying on.  This happens with my MacBook Pro and iPhone.  Since it works with at least ONE of the APs, leads me to consider that the issue might be within the network and not with Pfsense.  I'll let you know what I find out. I really appreciate you brainstorming with me and putting me on the right track.



  • You were right.  We took some switches down last week and some changes I made to the running config apparently didn't make it to the startup config file.  This included VLAN configuration for certain ports.  After re-adding the VLAN configs, DHCP is now working.  Your insight was much appreciated.



  • Those are the normal logs when dhcpd starts. Just showing what it's binding in the one particular line you pointed out.

    If it were receiving any DHCP requests that it couldn't service, it would log that and why.