Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Blocking WAN multicast and drop log

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 434 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      MUST-UPON-TURN
      last edited by

      I am getting frustrated with my ISP as they are allowing multicast data from others on their network so my firewall logs are filled up with these blocks. How can I setup a firewall rule for the WAN interface that will block all these attempts and then not log them?

      I tried setting source = network (xxx.xxx.xxx.1/24) and then destination WAN Net and This Firewall but both seem to still are logging. :(

      1 Reply Last reply Reply Quote 0
      • M
        mcury
        last edited by

        You could create an alias with the multicast blocks:
        https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml

        After that, you create a firewall rule in your WAN interface, setting this alias as destination, and mark the not log option.

        And also I would like to recommend you to change the ISP... that is not good

        dead on arrival, nowhere to be found.

        1 Reply Last reply Reply Quote 0
        • M
          MUST-UPON-TURN
          last edited by

          Thank you @mcury I will give that a try. Unfortunately this is the best ISP around, I have never had this happen at other locations with same ISP. I called them about it but the support rep was like "is service impacted, if not then whats the problem." :(

          M 1 Reply Last reply Reply Quote 0
          • M
            mcury @MUST-UPON-TURN
            last edited by

            @MUST-UPON-TURN Hm, maybe there is a bad switch around? Providers go to the last mile only.. The infra inside could be the culprit..

            dead on arrival, nowhere to be found.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.