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

    Can't ping WAN2 from ouside when WAN1 is the default

    Scheduled Pinned Locked Moved OpenVPN
    11 Posts 2 Posters 840 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.
    • V
      viragomann @fgenao
      last edited by

      @fgenao
      Did you allow the ICMP access with a floating rule or with one on an interface group?
      This won't work. You would have to remove such rules.

      You have to define pass rule on each WAN interface separately instead.

      F 1 Reply Last reply Reply Quote 0
      • F
        fgenao @viragomann
        last edited by

        Thanks @viragomann

        Here is what I got on the WAN2 Interface rule:
        Screenshot from 2023-10-05 11-32-32.png

        V 1 Reply Last reply Reply Quote 0
        • V
          viragomann @fgenao
          last edited by

          @fgenao
          The rule on the interface is fine, but are you sure, that it is applied to the incoming ICMP request?

          Simple test: Edit the ICMP rule, state a unique description and enable the logging. Try a ping and check the log then.

          F 1 Reply Last reply Reply Quote 0
          • F
            fgenao @viragomann
            last edited by

            @viragomann here is what I get on the log:
            Screenshot from 2023-10-05 13-37-54.png

            V 1 Reply Last reply Reply Quote 0
            • V
              viragomann @fgenao
              last edited by

              @fgenao
              Enable the displaying of the rule descriptions in the log settings to get the information.

              F 1 Reply Last reply Reply Quote 0
              • F
                fgenao @viragomann
                last edited by

                @viragomann

                678f0b95-0701-4633-a1b6-99d6043ced04-image.png

                48a63229-c580-4d1a-8f69-fc4d5688d275-image.png

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @fgenao
                  last edited by

                  @fgenao
                  So the rule in question is obviously applied. But on which rule tab is it defined? The screenshots do not show this.
                  And what is the COMGASTGW gateway? I don't expect any gateway setting on a rule for passing incoming traffic.

                  F 1 Reply Last reply Reply Quote 0
                  • F
                    fgenao @viragomann
                    last edited by

                    @viragomann

                    Rule: COMCAST Interface (WAN2)

                    Gateway WAN2: .96.85.39.206 (COMGASTGW)

                    V 1 Reply Last reply Reply Quote 0
                    • V
                      viragomann @fgenao
                      last edited by

                      @fgenao
                      As mentioned, there should not be a gateway stated in inbound rules.
                      With this pfSense redirects the packets to this gateway. This might not be, what you intend.

                      F 1 Reply Last reply Reply Quote 0
                      • F
                        fgenao @viragomann
                        last edited by

                        @viragomann

                        Thank you for your help, it is working now.

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