DHCP Discovery blocked

Andy142

Hi All,

I'm having an issue where cameras/devices connected to VLAN 22 (OPT6) can't communicate to the DHCP server.

From the firewall log:

Interface OPT6 linked to VLAN 22.
Access ports set on switch for VLAN 22.
pfSense on trunked port including VLAN 22.

Static IPv4 on OPT6 : 172.16.1.100/24
DHCP setup on OPT6: 172.16.1.150-172.16.1.170

Rules for OPT6:

As soon as a device is plugged in it shows in the DHCP leases as offline, I can't ping/access the webpage of the cameras. I also get the top picture in the firewall log.

I have plugged in my desktop to the VLAN, it gets a DHCP address but can't access DNS (gets blocked by the firewall) even though I have an allow all rule.

From the desktop I can access one of the cameras on the same subnet directly that does show active on the DHCP leases. But not the other two.

Any help would be appreciated.

Gertjan

@Andy142 said in DHCP Discovery blocked:

but can't access DNS (gets blocked by the firewall)

Was it logged as such ? (DNS traffic neing blocked).
Not by this firewall rule :

This rule says all IPv4 traffic. "DNS" is part of "All".

Is unbound, the resolver, listing on the OPT6 interface ?

strange enough : no states neither bytes are using this rule ... this interface ?
So, where do you want your traffic going ? And where is is going in reality ^^ ?
A VLAN issue open up now ...

@Andy142 said in DHCP Discovery blocked:

But not the other two.

They are listed in the leases list, and their lease is still valid.
So they have an IP.
Always keep in mind : Having an IP doesn't mean that a device should (has to) 'answer' to any request, on any port, for any protocol. It should be set up to do this.
Even replying to ping (ICMP) is optional, not mandatory.

Andy142

Thanks for your reply.

I have solved the issue, which as usual with these forums, was operator induced.

Previously I had installed Tailscale and set some firewall rules for it using the "tailscale network" dropdown for source.
It threw an error saying this macro wasn't defined but the firewall was passing traffic so I figured I'll work that one out at a later date.

Each time I was applying my firewall rules I assumed the rules were getting set, but due to the mentioned error the firewall wasn't updating. This was only evident when i looked at the monitor for the rules update. Doh!

Sorry for wasting your time.