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

    DHCP relay over IPSEC VPN?

    Scheduled Pinned Locked Moved DHCP and DNS
    27 Posts 10 Posters 8.9k 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.
    • J
      jlw52761 @maestrx
      last edited by

      @maestrx I do know what the difference between an L2 and L3 switch are. The L3 switch would perform the relay function, which depending on the manufacturer may or may not work well. I know on the Cisco Catalyst switches, it worked without any issues.

      E 1 Reply Last reply Reply Quote 0
      • E
        Ethereal @jlw52761
        last edited by

        @jlw52761 IP helper would work only on the SVI / Layer 3 Interface for the network.
        DHCP is L2. The IP helper must be configured on the Layer 3 interface/SVI which would also be the gateway/router for that network. That SVI must be able to "talk" / reach the DHCP server.

        J 1 Reply Last reply Reply Quote 0
        • J
          jlw52761 @Ethereal
          last edited by

          @Ethereal Yes, absolutely correct. Are you magically wanting pfSense to do this without any L2 connectivity?

          E 1 Reply Last reply Reply Quote 0
          • E
            Ethereal @jlw52761
            last edited by

            @jlw52761 i clicked on the wrong user. I was replying to one reply above.

            J 1 Reply Last reply Reply Quote 0
            • J
              jlw52761 @Ethereal
              last edited by

              @Ethereal understandable, sorry for the snarky response.

              O 1 Reply Last reply Reply Quote 0
              • O
                othomas @jlw52761
                last edited by

                Just another hand up here for this to be a feature in pfSense - our usecase is also iPXE bootstaping. I was assuming in my original planning that this was work, and now I find it doesn't. Having to rethink 😠

                1 Reply Last reply Reply Quote 0
                • I
                  itBJA
                  last edited by

                  Hello together.
                  Seems almost 2 years later still an issue.
                  I tried out the fix with the route, only change is, that I can now ping the remote-side from the diagnostic menu.
                  DHCP Relay still not working.
                  On the remote side the is no switch, it a virtualized network without any further setting possible.
                  The issue might also be:
                  You can have only one setting for DHCP-Relay.
                  So if you have VLANs on the remote-side that need to communicate with the same DHCP-Server on the central side, the packets won't come from the respective VLAN-interface, and will be routed into the wrong scope of the DHCP.
                  What also is weird, the local DHCP in the PFSense also isn't working, or so to speak only serving the LAN-Interface, not the VLAN-interfaces althoug activated on every interface.

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