No DHCP on VLAN interfaces

[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