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

    No DHCP on VLAN interfaces

    Scheduled Pinned Locked Moved DHCP and DNS
    19 Posts 12 Posters 54.0k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator
      last edited by

      "Created a VLAN on the Parent LAN-Interface (VLAN 99) (via Interface -> VLAN)"

      what is interface vlan??  The parent interface would be an actual physical interface, em0, re1, igb0, etc..

      Yeah you have to be logged into to via attachments ;)

      parent.png
      parent.png_thumb

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      1 Reply Last reply Reply Quote 0
      • N
        Niekoesj
        last edited by

        Hmmm suddenly i appeared… i tried this already many times.. :(
        This time i rebooted my box and it appeared :)

        On all tutorials/video's i saw the DHCP on the new Interface directly appearing. But it seems that it took some extra time on my box.

        1 Reply Last reply Reply Quote 0
        • B
          begbis
          last edited by

          VLAN's interface subnet mask (CIDR notation) should also something less than 32 bit for DHCP server to start.

          1 Reply Last reply Reply Quote 5
          • S
            scattermammoth
            last edited by

            @begbis:

            VLAN's interface subnet mask (CIDR notation) should also something less than 32 bit for DHCP server to start.

            This is what did it for me, note that the default subnet CIDR is /32 (which is a single IP address).

            After I experienced the same issue – creating a vLAN (Interfaces > VLANs), assigning it to a new subinterface (Interfaces > Interface Assignments), enabling the interface and setting a static IPv4 address -- I read this post and changed the subnet to /24 on the interface configuration, saved and applied the change, and the interface finally appeared in the Services > DHCP Server config.

            1 Reply Last reply Reply Quote 2
            • S
              sharlee011
              last edited by

              @scattermammoth:

              @begbis:

              VLAN's interface subnet mask (CIDR notation) should also something less than 32 bit for DHCP server to start.

              This is what did it for me, note that the default subnet CIDR is /32 (which is a single IP address).

              After I experienced the same issue – creating a vLAN (Interfaces > VLANs), assigning it to a new subinterface (Interfaces > Interface Assignments), enabling the interface and setting a static IPv4 address -- I read this post and changed the subnet to /24 on the interface configuration, saved and applied the change, and the interface finally appeared in the Services > DHCP Server config.

              Worked for me as well. Thanks

              1 Reply Last reply Reply Quote 0
              • A
                Asad Ali
                last edited by

                If you are doing L3 routing on FW correctly, then it should work without any problem.

                Please do the trace route from your AP

                1 Reply Last reply Reply Quote 0
                • brightwolfB
                  brightwolf
                  last edited by

                  Yeah I now I am here. Very happy with my SG-1100 and now extending the usage of it with some VLANs. I have exactly the problem described here.

                  @scattermammoth > creating a vLAN (Interfaces > VLANs), assigning it to a new subinterface (Interfaces > Interface Assignments), enabling the interface and setting a static IPv4 address -- changed the subnet to /24 on the interface configuration, saved and applied the change, and the interface finally appeared in the Services > DHCP Server config.

                  I did all this, and still no interface appears on Services > DHCP server config. Even rebooted, no luck. What can still be missing here? Why is a VLAN, set to its own static IP and set to use DHCP, refusing to appear on the DHCP server config screen?

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by johnpoz

                    @brightwolf said in No DHCP on VLAN interfaces:

                    set to its own static IP and set to use DHCP

                    Huh? For you to be able to enable dhcp server, the vlan has to have a static IP..

                    Please post up your interface assignment screen, and then the interface.. So here is one of my vlans

                    0_1551274664259_vlandhcp.png

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • brightwolfB
                      brightwolf
                      last edited by brightwolf

                      I had indeed set it to DHCP, not static. When I changed that to 10.10.23.0/24, I saw an error message:
                      "The following input errors were detected: This IPv4 address is the network address and cannot be used".
                      So I changed it to 10.10.23.1/24 and it worked. Thanks! (and a bit ashamed, I am)
                      [EDIT: posting the screenshots you asked for]
                      0_1551275427717_Screenshot 2019-02-27 14.42.41.png
                      0_1551275434704_Screenshot 2019-02-27 14.44.23.png

                      1 Reply Last reply Reply Quote 0
                      • brightwolfB
                        brightwolf
                        last edited by

                        With the new setting it works:
                        0_1551275529432_Screenshot 2019-02-27 14.51.32.png
                        0_1551275533209_Screenshot 2019-02-27 14.51.49.png

                        1 Reply Last reply Reply Quote 0
                        • johnpozJ
                          johnpoz LAYER 8 Global Moderator
                          last edited by

                          Well yeah x.x.x.0/24 would be the wire or network address.. So yeah its going to give you that error.

                          An intelligent man is sometimes forced to be drunk to spend time with his fools
                          If you get confused: Listen to the Music Play
                          Please don't Chat/PM me for help, unless mod related
                          SG-4860 24.11 | Lab VMs 2.8, 24.11

                          1 Reply Last reply Reply Quote 0
                          • P
                            playforvoices
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • C chevdor referenced this topic on
                            • Austin 0A
                              Austin 0
                              last edited by

                              I found this topic thread while searching for an answer to this question. My solution wasn't exactly the same, but I thought I would note it here anyway so that if some one else has the issue they may see it. I was idiot and had my subnet set to a /32 on the interface. PFSense correctly understood that would be a subnet of 1 IP and thus did not display the interface tab under the DHCP configuration option. When I went back and changed it to /24 it showed up.

                              1 Reply Last reply Reply Quote 0
                              • L
                                lucasisrael
                                last edited by

                                Check if interface is Enable on PFSENSE > INTERFACES > vlan_interface > Enabla interface

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