[USG Flex H] - Block rule to broadcast IP

Options
Maverick87
Maverick87 Posts: 176 image  Master Member
5 Answers First Comment Friend Collector

Hello everyone,
I've an IoT device (on 192.168.0.0/24 LAN) that needs to communicate with the broadcast IP (192.168.0.255) on port 59387, but seems that the rule are blocked.

image.png

Why? What I'm wrong?
What is the rule that I need to add to unblock it?

Thank you

Accepted Solution

  • Zyxel_Judy
    Zyxel_Judy Posts: 2,588 image  Zyxel Employee
    Zyxel Certified Network Engineer Level 2 - Nebula Zyxel Certified Network Engineer Level 2 - Switch Zyxel Certified Network Engineer Level 2 - Security Zyxel Certified Network Engineer Level 1 - Nebula
    edited July 15 Answer ✓
    Options

    Hi @Maverick87 ,

    We need to have these kinds of logs appear because it shows the traffic hits the Policy Control rule "Deny Any to Any" (the last/default policy), which applies to traffic in both the LAN and WAN directions.

    In case you don't want to have the block logs from LAN to broadcast IP, you can add a policy (LAN → Broadcast) with logging disabled before the last implicit default deny policy to achieve the desired filtering. The steps as below:

    1. Navigate to Security Policy > Policy Control in the Web GUI.
    2. Create a new policy rule positioned near the bottom of your rule list (directly above the implicit default-deny rule).
    3. Set the parameters as follows:
    • Source: Any (or the specific local zones/subnets, e.g., LAN)
    • Destination: Create and select an address object for the broadcast address
    • Action: Deny/ Reject
    • Log: No Log

    4. Save the rule.

    Zyxel_Judy

All Replies

  • PeterUK
    PeterUK Posts: 4,552 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    edited July 10
    Options

    A broadcast for like UDP to the USG will Always (from what I can tell) be blocked so you have like
    LAN IP/subnet 192.168.0.0/24
    a switch to USG with devices at 192.168.0.31 and 192.168.0.100
    when a broadcast happens from like 192.168.0.31 the switch on the same VLAN broadcast to all ports which 192.168.0.100 will see but also the USG at like 192.168.0.1

    I guess really the USG could filter these broadcast out to not show in the logs

  • Maverick87
    Maverick87 Posts: 176 image  Master Member
    5 Answers First Comment Friend Collector
    Options

    Hi @PeterUK,

    Thank you, so is not an "error", the communication is not really blocked and I can ignore it?

    Thank you

  • PeterUK
    PeterUK Posts: 4,552 image  Guru Member
    250 Answers 2500 Comments Friend Collector Eighth Anniversary
    Options

    yes you can ignore it

  • Maverick87
    Maverick87 Posts: 176 image  Master Member
    5 Answers First Comment Friend Collector
    Options

    Hi @PeterUK,
    I've opened an Idea to hide/remove this entry log (writes uselessly inside the log, taking up space for other more interesting logs).

  • Zyxel_Judy
    Zyxel_Judy Posts: 2,588 image  Zyxel Employee
    Zyxel Certified Network Engineer Level 2 - Nebula Zyxel Certified Network Engineer Level 2 - Switch Zyxel Certified Network Engineer Level 2 - Security Zyxel Certified Network Engineer Level 1 - Nebula
    edited July 15 Answer ✓
    Options

    Hi @Maverick87 ,

    We need to have these kinds of logs appear because it shows the traffic hits the Policy Control rule "Deny Any to Any" (the last/default policy), which applies to traffic in both the LAN and WAN directions.

    In case you don't want to have the block logs from LAN to broadcast IP, you can add a policy (LAN → Broadcast) with logging disabled before the last implicit default deny policy to achieve the desired filtering. The steps as below:

    1. Navigate to Security Policy > Policy Control in the Web GUI.
    2. Create a new policy rule positioned near the bottom of your rule list (directly above the implicit default-deny rule).
    3. Set the parameters as follows:
    • Source: Any (or the specific local zones/subnets, e.g., LAN)
    • Destination: Create and select an address object for the broadcast address
    • Action: Deny/ Reject
    • Log: No Log

    4. Save the rule.

    Zyxel_Judy

  • Maverick87
    Maverick87 Posts: 176 image  Master Member
    5 Answers First Comment Friend Collector
    Options

    Hi @Zyxel_Judy,
    Thank you

    I've created the rule and all works.
    One point: the rule needs to be created with To: ZyWall zone

    Thank you