No DHCP on VLAN interfaces

[telserv]

Found my mistake.  I had created the VLANs under INTERFACE | ASSIGN |  VLAN,
but had failed to create them under **INTERFACE | ASSIGN | INTERFACE ASSIGNMENTS. **

It was this second assignment that allowed me to enter an IP address, which then allowed DHCP to be configured on that VLAN.

I also found out that if I logged in to read johnpoz reply,  I would have seen those screen prints.  The screen prints do not show if I only click on the link in the notification email.  Thanks to jahonix for bringing that to my attention.

Thank you to johnpoz and jahonix for guiding me back to reality.  Problem Solved.

[Niekoesj]

Hi All!

I'am quite new here and face the same problem!
I have exactly followed the steps from the screenshot, but i still don't see any other/new interfaces appearing.

For sure:

• Created a VLAN on the Parent LAN-Interface (VLAN 99) (via Interface -> VLAN)
• I Added a new interface named "Guests" based on the just created VLAN99
• Enabled the Interface and set IPV4 (static) address 192.168.179.1/24
• SAVED the config and reloaded

But once i go to the DHCP Service page, i only see the "LAN"-tab, but not the newly created "Guests" interface.

In your screenshots i also see the "WAN" for example.. i only have LAN.

What am i missing? is there another setting which prevents the creation of the "Guest" tab in the DHCP server settings?

[johnpoz]

"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 ;)

[Niekoesj]

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.

[begbis]

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

[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.

[sharlee011]

@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

[Asad Ali]

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

Please do the trace route from your AP

[brightwolf]

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?

[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

[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]

[brightwolf]

With the new setting it works:

[johnpoz]

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

[playforvoices]

This post is deleted!

[Austin 0]

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.

[lucasisrael]

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