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

    "Default Deny" from My Computer to Multicast Log Entries [SOLVED]

    Scheduled Pinned Locked Moved Firewalling
    10 Posts 3 Posters 1.6k 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.
    • beremonavabiB
      beremonavabi
      last edited by beremonavabi

      I keep getting these "Default Deny" entries in my firewall and I don't understand why/how they're being denied:

      	Dec 2 07:44:50	LAN	Default deny rule IPv6 (1000000105)	  [fe80::e174:d029:ec98:d337]:52993	  [ff02::1:3]:5355	UDP
      Dec 2 07:44:50	LAN	Default deny rule IPv6 (1000000105)	  [fe80::e174:d029:ec98:d337]:51969	  [ff02::1:3]:5355	UDP
      Dec 2 07:44:50	LAN	Default deny rule IPv6 (1000000105)	  [fe80::e174:d029:ec98:d337]:51969	  [ff02::1:3]:5355	UDP
      Dec 2 07:44:50	LAN	Default deny rule IPv6 (1000000105)	  [fe80::e174:d029:ec98:d337]:52993	  [ff02::1:3]:5355	UDP
      

      I'm pretty sure that's blocking IPv6 multicasts from my own computer on the LAN to other things on my LAN. I have no blocking Firewall rules of my own on my LAN at all, so these have got to be coming from the default deny rules (as stated). But, I don't see anything with pfctl -s rules that would explain this. The only things showing there with that label are the expected:

      block drop in log inet6 all label "Default deny rule IPv6"
      block drop out log inet6 all label "Default deny rule IPv6"

      Here are my LAN firewall rules:

      0_1543769061064_20181201 -- pfSense 2_4_4 Firewall Rules LAN.jpg

      Is that multicast address not considered to be part of LAN net?

      SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by NogBadTheBad

        fe80:: != LAN net add a firewall rule

        0_1543788432065_Screenshot 2018-12-02 at 22.06.41.png

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

        1 Reply Last reply Reply Quote 1
        • beremonavabiB
          beremonavabi
          last edited by beremonavabi

          Thanks.

          [I've deleted a whole bunch of stuff here because it was wrong and huge]

          EDIT: I've added a rule just like yours and I still get the default denies in my Firewall log.

          SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

          beremonavabiB 1 Reply Last reply Reply Quote 0
          • beremonavabiB
            beremonavabi @beremonavabi
            last edited by beremonavabi

            @beremonavabi

            Since I can't figure out why this is still happening, I'll put in some screenshots just in case my eyes are playing tricks with me on what I'm seeing and what I've done. The Firewall rule is on my LAN and should cover everything with a link local address on my LAN being sent to the link local multicast address on the LAN. As far as I can see, that's what those default denies are saying. Yet, that rule isn't even firing (evaluations, packets, bytes, states, and state creations are all 0 -- and I've reset my States):

            0_1543807242870_20181202 -- pfSense 2_4_4 Firewall Rules LAN.jpg

            0_1543807256947_20181202 -- pfSense 2_4_4 Default Deny Multicast.jpg

            SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

            1 Reply Last reply Reply Quote 0
            • NogBadTheBadN
              NogBadTheBad
              last edited by

              Try killing the firewall states.

              Andy

              1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

              1 Reply Last reply Reply Quote 0
              • beremonavabiB
                beremonavabi
                last edited by

                I had reset my states and also rebooted pfSense, but that didn't help. I updated to 2.4.4_1 and it all seems to be working properly now, though.

                SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

                1 Reply Last reply Reply Quote 0
                • beremonavabiB
                  beremonavabi
                  last edited by beremonavabi

                  I didn't check in 2.4.4, but in 2.4.4_1, I see the following with pfctl -s rules:

                  ...
                  pass quick on igb0 inet6 proto udp from fe80::/10 to ff02::/16 port = dhcpv6-client keep state label "allow access to DHCPv6 server"
                  pass quick on igb0 inet6 proto udp from fe80::/10 to ff02::/16 port = dhcpv6-server keep state label "allow access to DHCPv6 server"
                  ...
                  

                  It's specific to "port = dhcpv6-server", so I don't know if 2.4.4_1 automatically fixes this. I'll disable my rule for a bit and see what happens.

                  EDIT: I don't think those default rules will fix this since the dhcpv6 ports are 546 and 547, while I was getting these default denies on ports 5355 and 27036.

                  SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

                  beremonavabiB 1 Reply Last reply Reply Quote 0
                  • beremonavabiB
                    beremonavabi @beremonavabi
                    last edited by

                    @beremonavabi

                    Nope. That manual rule is definitely needed.

                    SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

                    1 Reply Last reply Reply Quote 0
                    • NogBadTheBadN
                      NogBadTheBad
                      last edited by

                      port 5355 is multicast DNS

                      https://en.wikipedia.org/wiki/Multicast_DNS

                      Andy

                      1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

                      1 Reply Last reply Reply Quote 0
                      • sigiS
                        sigi
                        last edited by

                        BTW: Please inform yourself about "what is IPv6 link local addressing" and when is it needed. And then multicast: Even when you allow this: Multicast over L3 is another story. When this thread only is about "do not log rules" it is ok too.

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