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

    Rules for allowing limited ICMP on IPv4/v6 from WAN

    Scheduled Pinned Locked Moved Firewalling
    6 Posts 3 Posters 624 Views 2 Watching
    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.
    • provelsP Online
      provels
      last edited by provels

      Greetings. Could someone advise if Ihave these rules setup correctly? The v4 rule is just for troubleshooting from outside and the v6 is for making IPv6 work. Did some reading and i think they're right, but thought I'd check. Thanks for any assist.
      ce86a627-49f0-4d33-9894-4b843189f1ec-image.png

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        You wouldn't need to set echorep or unreach as those would never arrive unsolicited -- only associated with an existing state, which would already pass them. I suspect the same is also true of paramprob and timex. You probably only need to explicitly allow echoreq if you intend to allow remote hosts to ping you.

        pf is pretty good about state tracking and associating ICMP messages with related connections already for things like unreachable messages.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        provelsP 2 Replies Last reply Reply Quote 2
        • provelsP Online
          provels @jimp
          last edited by

          @jimp Thanks very much. Appreciate all you do.

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          1 Reply Last reply Reply Quote 0
          • provelsP Online
            provels @jimp
            last edited by

            @jimp PS - Is the LAN Net OK for IPv6 dest? Thanks again.

            Peder

            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

            IsaacFLI 1 Reply Last reply Reply Quote 0
            • IsaacFLI Offline
              IsaacFL @provels
              last edited by

              @provels said in Rules for allowing limited ICMP on IPv4/v6 from WAN:

              Is the LAN Net OK for IPv6 dest? Thanks again.

              LAN Net is fine as long as that is the only subnet you have. I created an Alias for my whole /56 i received from my ISP and these are the rules I have:

              Annotation 2020-02-13 174132.png

              This was based on "RFC 4890 Recommendations for Filtering ICMPv6 Messages in Firewalls" paragraph 4.3.1. Traffic That Must Not Be Dropped.

              I had not considered what @jimp said, that the pfsense takes care of some of these for you already.

              I don't remember why I added the WAN address rule, but maybe it was trace-route? Or just so I could ping the router externally and see it was up?

              The WAN address is an address external from my /56.

              provelsP 1 Reply Last reply Reply Quote 0
              • provelsP Online
                provels @IsaacFL
                last edited by

                @IsaacFL Thanks. Now that you mention it, I believe the the RFC was where I had found the info I used as well but had forgotten (buffer overflow, I guess...). Thanks again, all.

                Peder

                MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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