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

    RTO Ouf of no where

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 4 Posters 1.3k 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.
    • X
      xodiacx
      last edited by

      Hi,

      I need some help please with my pfsense, I don't know who else is experiencing this but I am always getting RTO out of nowhere. Let's say I restart my router today then after few days when I try to ping via ip address or dns I will receive a RTO response. How can I troubleshoot this issue?

      pfsense 2.4.3
      amd64
      CPU: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (3100.07-MHz K8-class CPU)
      4gb ddr3 ram

      Hope someone can help me
      Thanks

      1 Reply Last reply Reply Quote 0
      • kiokomanK
        kiokoman LAYER 8
        last edited by

        how do you solve the problem? do you restart the modem or pfsense?

        ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
        Please do not use chat/PM to ask for help
        we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
        Don't forget to Upvote with the 👍 button for any post you find to be helpful.

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

          @xodiacx said in RTO Ouf of no where:

          RTO response

          I assume you mean 'response timed out' or similar?

          We're going to need examples of exactly what timed out. It sounds like it is still resolving if it's trying an failing to ping.
          Can you ping internal hosts still? Hosts on other internal subnets?
          Can you ping hosts from within pfSense on Diag > Ping or from the CLI?

          Steve

          X 1 Reply Last reply Reply Quote 0
          • X
            xodiacx @kiokoman
            last edited by

            @kiokoman by restarting the pfsense directly, after that I can ping again with no prob

            1 Reply Last reply Reply Quote 0
            • X
              xodiacx @stephenw10
              last edited by

              @stephenw10 pinging from diagnostics to google.com dns will have a reply, pinging to other internal lan ip's will have a reply also, but pinging from my unit to google.com will reply to me RTO. but if I restart my pfsense box and do a ping test again It can reply now with no problems.

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

                Check for a missing or incorrect default route in Diag > Routes.

                If it is missing or wrong go to System > Routing > Gateways and make sure the default IPv4 gateway is set to the main WAN gateway rather than automatic.

                Steve

                X 2 Replies Last reply Reply Quote 0
                • X
                  xodiacx @stephenw10
                  last edited by

                  @stephenw10 what if we have multiple gateways?

                  JKnottJ 1 Reply Last reply Reply Quote 0
                  • X
                    xodiacx @stephenw10
                    last edited by

                    @stephenw10 please see attached/uploaded image of Diag>Routespf1.png
                    pf2.png
                    pf3.png

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

                      You have a default route shown there. Is that the correct default gateway?

                      If you have multiple WAN gateways you can set a gateway group as the default gateway there but it must be a failover group, you can't configure load-balancing there.

                      Steve

                      X 1 Reply Last reply Reply Quote 0
                      • X
                        xodiacx @stephenw10
                        last edited by

                        @stephenw10 so you're saying this is a misconfigured setup that's why sometimes we can ping and then sometimes not?

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

                          I'm saying the behaviour you're describing sounds like what happens if you have the default gateway set to automatic, there is packet loss on the main gateway and it switches to some other default route thas is invalid. If you have an internal gateway for example or potentially the OpenVPN gateway you have there.
                          Setting the default gateway to the main WAN gateway would prevent that if so.

                          Steve

                          X 1 Reply Last reply Reply Quote 0
                          • X
                            xodiacx @stephenw10
                            last edited by

                            @stephenw10 ok will into this again

                            1 Reply Last reply Reply Quote 0
                            • JKnottJ
                              JKnott @xodiacx
                              last edited by

                              @xodiacx said in RTO Ouf of no where:

                              what if we have multiple gateways?

                              You can only have one default gateway, though you can have other routes out, but they have to be specified.

                              PfSense running on Qotom mini PC
                              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                              UniFi AC-Lite access point

                              I haven't lost my mind. It's around here...somewhere...

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