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

    SG-2100 MULTI-WAN CONFIGURATIONS

    Scheduled Pinned Locked Moved General pfSense Questions
    40 Posts 4 Posters 6.1k 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.
    • S
      SteveITS Galactic Empire @skbnet
      last edited by

      @skbnet What is set as the gateway monitoring IP for that interface? It’s probably not responding to pings. (Also, make it different than WAN)

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      S 1 Reply Last reply Reply Quote 0
      • S
        skbnet @SteveITS
        last edited by

        @steveits When I disable gateway monitoring, I can see gateway status "Online" instead of "Offline, Packetloss". When I add google dns or my ISP gateway IP as a monitoring IP, it again shows "Offline, Packetloss"

        I can live without monitoring IP for the secondary WAN but don't you think this will create problem when I configure load balancing/failover?

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by stephenw10

          Yes, you need to have reliable gateway monitoring for failover.

          If you can connect out to the internet via OPT1 you should be able to set, say, 8.8.8.8 as a monitoring IP there and see replies.
          I assume you can ping 8.8.8.8 from a client behind the firewall when the main WAN is disconnected? Assuming you have setup some policy routing or failover system route.

          Can you ping the OPT1 gateway IP from a client behind the firewall?

          Check the firewall states in Diag > States. Do you see the monitoring pings on the OPT1 interface.

          We are probably going to need some screenshots to review here.

          Steve

          S 1 Reply Last reply Reply Quote 0
          • S
            skbnet @stephenw10
            last edited by

            @stephenw10 I can ping 8.8.8.8 from a client behind the firewall when the main WAN is disconnected.
            I can also ping the OPT1 gateway IP from a client behind the firewall. But when I put 8.8.8.8 as monitoring IP, I get the same "Offline, Packetloss" status.
            I checked the states in Diag > States nad state for monitoring pings on the OPT1 is 0:0.
            Should I hard reset and configure everything again?

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Are you policy routing traffic from the client via the OPT1 gateway when you do that?

              Can you ping from the firewall itself either at the command line or from Diag > Ping?

              S 1 Reply Last reply Reply Quote 0
              • S
                skbnet @stephenw10
                last edited by

                @stephenw10 When I am trying to ping 8.8.8.8, I am disabling the primary WAN so that all my traffic goes via OPT1.
                Yes, I can ping from the firewall itself from Diag > Ping via OPT1.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Hmm, do you see the dpinger service running?

                  You should see a state on the OPT1 interface for the gateway monitoring pings even if it doesn't reply.

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    skbnet @stephenw10
                    last edited by

                    @stephenw10 Sorry, I have no idea about the dpinger service. Can you tell me how to check it?

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Shown in Status > Services. You can try restarting it there too.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        skbnet @stephenw10
                        last edited by

                        @stephenw10 Yes, dpinger service was running and restarted it. But still the same problem.

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Mmm, I think we're going to need to see screenshots.

                          Something odd going on.

                          What states to you see on OPT1?

                          What states do you see for the monitoring IP you set on any interface?

                          S 2 Replies Last reply Reply Quote 0
                          • S
                            skbnet @stephenw10
                            last edited by

                            @stephenw10 OPT1 state.jpg WAN state.jpg
                            Screenshots attached for reference.

                            1 Reply Last reply Reply Quote 0
                            • S
                              skbnet @stephenw10
                              last edited by

                              @stephenw10 I solved this puzzle. There is no issue with SG-2100. It was the firewall setting of the upstream router which was blocking the monitoring. I changed those settings in the upstream router and now the interface status of OPT1 is "Online" with 8.8.8.8 as the monitoring IP.

                              Thanks a lot for your guidance.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Ah, good catch. 👍

                                I was just going to suggest something must be blocking it upstream. Odd that you were able to ping 8.8.8.8 from a client on LAN though.

                                Steve

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