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

    DHCP will not run on logical interfaces

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 636 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.
    • T Offline
      tomcos
      last edited by

      Hey Team,

      Been troubleshooting for a bit now, confident it's not a configuration issue.  The DHCP server is not listening on the VLAN interfaces I've created.

      I can replicate the issue without a doubt.  The LAN interface will reply to discovers.  All of the VLAN interfaces are ignoring them.  I see the discovers hitting the gateway, but there is no offer being sent back.  Had to revert a migration because of this.

      I've seen multiple threads regarding this all over the forum.  Would definitely be willing to troubleshoot or provide logs if needed.

      The 3 VLANs are running over a LACP bond that is trunked to a Cisco 3560-CX.  While I'm not familiar enough in the PFSense CLI to provide data on my own, I'm fairly certain the dhcpd is not listening over anything other than the default LAN interface that is created day 1.

      In the other threads I've seen on the forum over the past few hours, the red herring seems to be the VLAN tagging and I really don't think this is the case here.  The FW is the gateway to these subnets and sits on the same L2 as the hosts.  All the tagging is working as expected, as the gateway is seeing the hosts.  When static IPs are used, all route/switch/policy works as expected.

      Any suggestions would be great.
      -T

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        Did you enable DHCP Server on those interfaces?

        Have you stopped and started the DHCP server in System > Services? Should not be necessary but sometimes it needs a kick. Don't restart it. stop it and start it.

        I can assure you that DHCP Server works just fine on VLAN tagged interfaces. I have seen newly-added interfaces not get picked up on occasion.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • T Offline
          tomcos
          last edited by

          Restart is all I did, not stop and start.  Let me get a maintenance ready and I'll give it a shot.  Thanks for the quick reply!
          -Tom

          1 Reply Last reply Reply Quote 0
          • T Offline
            tomcos
            last edited by

            Wanted to follow up.  That did the trick!  No restart, hard stop hard start.  Thanks for the help!

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