Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    pfSense 2.4.4 DHCP Relay issue

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 2 Posters 696 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mcarson75
      last edited by

      I am using Windows Server as my DHCP server for several subnets, and have had pfSense setup as a relay. All was working fine. I just upgraded to pfSense 2.4.4 and since then I have noticed that I have had issues with devices not being able to get IP addresses. Android devices for example will come back and say it could not obtain an IP address. I initially tried to restart the DHCP server service on the Windows server but that didn't make any difference. However, I restarted pfSense and it began working. It was okay for a couple of hours and then I started having the same issues again. The next time I just reset the dhcrelay service on pfSense and it began working again.

      I really don't know much about the DHCP Relay or how it works. Has anyone seen the same issue or have any suggestions? I will probably put a CRON job in to restart the dhcrelay service every hour, but that seems like a bandaid and not a fix.

      1 Reply Last reply Reply Quote 0
      • A
        acaronmd
        last edited by

        Just want to say that I also have this issue on 2.4.4. I've checked the logs to find this

        Nov 13 09:43:51 dhcrelay Disabling output on BPF/vmx1.2202/00:50:56:94:4b:66
        Nov 13 09:43:51 dhcrelay Disabling input on BPF/vmx1.2202/00:50:56:94:4b:66
        Nov 13 09:43:51 dhcrelay receive_packet failed on vmx1.2202: Device not configured

        repeated for each interface setup for DHCP Relay. Restarting the service fixes it, but I'd rather not take mcarson75's solution of setting up a cron job to fix this.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.