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

    weird internet access issue

    Scheduled Pinned Locked Moved General pfSense Questions
    45 Posts 5 Posters 9.0k 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.
    • P
      pp-ng @stephenw10
      last edited by

      @stephenw10 All I do to restore access is literally unplug the ethernet cable from the pfsense box and plug it back in, I dont even wait. Just unplug and plug back in.

      I unplug the ethernet cable that goes from the isp provided modem to the wan port of my pfsense box. it's a protectli vault if that means anything.

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

        Ok, so doing that triggers a bunch of scripts that would, among many other things, re-apply the default route. So try to see if it has actually lost the route. Then try resaving the default gateway or resaving the WAN and see if that brings it back.

        P 1 Reply Last reply Reply Quote 0
        • P
          pp-ng @stephenw10
          last edited by

          @stephenw10

          At the moment there are 9 IPv4 routes and one of them is set to default under the destination column

          So when this happens again go into Diag > Routes and see what has changed from a working state?

          What do you mean by "re-apply the default route" and "resaving the default gateway or resaving the WAN" ?

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

            Yes, check to see if the default route has gone missing from the table.

            Go to System > Routing > Gateways. Make sure WAN_DHCP is set as the default gateway and hit save. Check the route table again, that should have brought back the default route if it was removed.
            Just setting the default gateway there if it's still at the default auto might prevent this happening.

            Otherwise go to Interfaces > WAN and hit save there. See if that restores connectivity.

            Steve

            P 1 Reply Last reply Reply Quote 0
            • P
              pp-ng @stephenw10
              last edited by

              @stephenw10 Yea it is currently set to auto, I will change it to WAN_DHCP and see if the issue happens again. Otherwise I'll note down what the Diag > Routes show when the issue happens again.

              I'm not entirely concerned about restoring connectivity as I am prevent this from happening. It's getting quite old having to go through this every~39-48hrs :)

              Greatly appreciate this assistance with this, hopefully we'll figure out the root issue.

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

                Indeed, preventing it happen is the goal here but working out exactly what restores it helps us pin down the actual problem so it can be prevented.

                P 1 Reply Last reply Reply Quote 1
                • P
                  pp-ng @stephenw10
                  last edited by

                  @stephenw10 Happened again

                  The Default > Routes page looks the exact same after it happened vs when it's working.

                  I tried saving and applying on the system > routing page, didn't restore access

                  I tried saving and applying on edit gateway page for the wan_dchp - it didn't restore access

                  I tried restarting the dchp servicce, didn't restore access

                  I switched the outbound nat from manual to hybrid, didn't restore anything

                  I eventually had to go back to unplug and plug back in the ethernet cable to the pfsense because I have to start working :)

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

                    Hmm, OK.

                    The logs showed the same sendto error: 65 ?

                    That really looks like a missing default route...

                    Did you try re-saving the WAN?

                    Steve

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      pp-ng @stephenw10
                      last edited by

                      @stephenw10 Yes same sendto error: 65

                      When you say re-save WAN, do you mean go into interfaces > wan and click save?

                      I did not do that if that's what you mean. I can try that next time

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

                        Yes, try that. That does many of the same things that reconnecting the link does but not all. That may give us some insight. Try to grab the system logs just after you have done that if it works.

                        Steve

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          pp-ng @stephenw10
                          last edited by

                          @stephenw10 The gateway system logs?

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

                            Yes, the main system log. It will show the WAN settings being reapplied.

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              pp-ng @stephenw10
                              last edited by

                              @stephenw10 i'm expecting to have the issue tomorrow, besides trying to re-save the WAN - is there anything else I should try for debugging or narrowing down the issue?

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

                                You can try to manually ping the gateway monitoring IP and see what error it shows.

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  pp-ng @stephenw10
                                  last edited by

                                  @stephenw10 from diag > cmd prompt ?

                                  R 1 Reply Last reply Reply Quote 0
                                  • R
                                    rcoleman-netgate Netgate @pp-ng
                                    last edited by

                                    @pp-ng Diag -> Ping

                                    Ryan
                                    Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                                    Requesting firmware for your Netgate device? https://go.netgate.com
                                    Switching: Mikrotik, Netgear, Extreme
                                    Wireless: Aruba, Ubiquiti

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

                                      Or directly at the command line.

                                      I usually prefer to SSH in and use the command line because then I can go back and review what was done.

                                      P 1 Reply Last reply Reply Quote 1
                                      • ?
                                        A Former User
                                        last edited by

                                        @pp-ng said in weird internet access issue:

                                        Hi, I noticed that my internet access goes down once every 1 - 2 days.
                                        Under gateways, it shows offline - packetloss for my WAN

                                        Do your ISP cutting of your Internet access every xyz hours like here in Germany all 24 hours? Some thing is running full?

                                        When I restart my modem which my ISP provides, everything starts working again.

                                        Is this a pure mode or a small router with a modem?

                                        It happened again and this time I directly plugged my modem into a laptop using the same ethernet cable that I use to plug into my pfsense router. My laptop had internet access and seemed to work fine.

                                        Also for 2 days or longer or only for a moment?

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          pp-ng @stephenw10
                                          last edited by

                                          @stephenw10 so I haven't lost internet access yet, fingers crossed. not sure why because I haven't made any changes.

                                          I did notice however in the gateway system logs:

                                          Oct 12 20:02:01 dpinger 49963 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 1.1.1.1 bind_addr xxx.xxx.xxx.xxx identifier "WAN_DHCP "

                                          This would typically come before the WAN_DHCP 1.1.1.1: sendto error: 65 - but it didn't this time.

                                          So I'm still waiting for it to happen.

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

                                            That log entry is dpinger starting on the WAN and recording the values it;s using. So that usually means the WAN was reconnected or a setting was changed causing dpinger to restart.

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