Pfsense Blocking WAP 255 broadcast

Basically I have the logs filled with this:

https://preview.redd.it/4el36bzpzdsa1.png?width=553&format=png&auto=webp&v=enabled&s=ab8f9f5fdb431bc63046868520e1519f3875c331

​

Hasnt effected the wifi as far as I can tell, but these message are annoying.

​

Here is the rules:

​

https://preview.redd.it/kzsmxl5yzdsa1.png?width=1156&format=png&auto=webp&v=enabled&s=5fe3b58e533bbceeb8b17ddc946feda77a04a665

​

I have another vlan setup similarly and it doesnt do this, so not sure where im going wrong.

Posted Apr 7, 2023, 4:07 AM UTC

19
chrisschrimsher•

Since it’s broadcast traffic, it’s not needed for it to cross the firewall, so you’re right - functionally it shouldn’t affect anything at all. To suppress the messages, you could create a block rule for that traffic. It’s already being blocked, but the implicit rule logs matching traffic.

3
SamSausages268TB on Unraid & OpenZFS, EPYC 7343•

I do the same with some 255 traffic. I made a rule called “suppress log spam”, so they wouldn’t show up in the log.

3
leadwind•

I call them stfu rules.

4
JuniperMS•

Do you have TP-Link Omada access points? Typically that port is used to discover devices. I’d suspect you don’t see this issue in your other clan because the controller and device are within the same subnet.

https://community.tp-link.com/en/business/kb/detail/362

2
Stygian_rain•

Yes using omada ap. I have 3 wifi vlans. None of them are on the same network as the wired lan.

So should I make a rule to allow that udp 29810???

1
JuniperMS•

Whatever network the uplink is on for the AP, that’s where you should see those messages.

1
Stygian_rain•

Im a network noob. Uplink??

1
JuniperMS•

The link going to the access point. Yes, I’d recommend reviewing the required ports for Omada and allowing the traffic.

2
kphillips-netgateMODNetgate - Happy Little Packets•

Block messages for broadcast traffic are expected. Broadcast traffic is never intended to leave a broadcast domain (aka the subnet it originated). The block messages are simply the firewall dropping that traffic because it shouldn't be leaving that interfaces.

1