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

    Pfense Internet stop working. Only works after reboot

    General pfSense Questions
    5
    16
    2.1k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      That all looks normal.

      How many IPv4 gateways do you have defined in System > Routing > Gateways?

      If there is more than 1 make sure the default is set to the WAN gateway.

      Steve

      B 1 Reply Last reply Reply Quote 0
      • B
        Bangui91 @stephenw10
        last edited by

        @stephenw10
        I am using orange Livebox as my internet provider, then pfsense router after that I have my TPlink router connect to lan line.
        If you don't my I can give you my anydesk so you can remote connect to my pc

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

          I'm sorry I can't do that currently.

          Go to Status > Gateways.
          How many gateways are shown? Can we see a screenshot?

          Steve

          B 1 Reply Last reply Reply Quote 0
          • B
            Bangui91 @stephenw10
            last edited by

            @stephenw10

            here is what I can see :

            Aug 25 20:15:36 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:36 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:37 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:37 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:38 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:38 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:39 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:39 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:40 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:40 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:41 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:41 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:42 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:42 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:43 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:43 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:44 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:45 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:45 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:46 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:46 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65
            Aug 25 20:15:47 dpinger 39071 WAN_DHCP 192.168.254.130: sendto error: 65

            B GertjanG 2 Replies Last reply Reply Quote 0
            • B
              Bangui91 @Bangui91
              last edited by

              @bangui91

              Aug 25 20:20:03 dpinger 52155 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 192.168.254.130 bind_addr 192.168.254.13 identifier "WAN_DHCP "
              Aug 25 23:56:17 dpinger 91512 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 192.168.254.130 bind_addr 192.168.254.13 identifier "WAN_DHCP "
              Aug 25 23:56:19 dpinger 21129 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 192.168.254.130 bind_addr 192.168.254.13 identifier "WAN_DHCP "
              Aug 26 00:03:31 dpinger 1574 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 192.168.254.130 bind_addr 192.168.254.13 identifier "WAN_DHCP "

              B 1 Reply Last reply Reply Quote 0
              • B
                Bangui91 @Bangui91
                last edited by

                @bangui91
                685a7447-03ae-4e5f-8d18-62d3f539f036-image.png

                ee71c85d-9b1f-437a-87c7-ffe13f6339d8-image.png

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

                  So just one gateway then.

                  That error indicates the host (the gateway here) is unreachable:
                  https://docs.netgate.com/pfsense/en/latest/troubleshooting/gateway-errors.html#sendto-error-65

                  That should never happen since the gateway is in the same subnet as the WAN interface.
                  So it may have lost its IP? Or maybe you have another device handing out dhcp leases?

                  You probably need to wait until it's broken and then check the WAN interface status and the ARP table.

                  Steve

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    Bangui91 @stephenw10
                    last edited by

                    @stephenw10

                    there is any fix for that?

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

                      We need to know what the problem is before trying to fix it.

                      Check the WAN interface status when it fails. Check the ARP table. Check the system log.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • GertjanG
                        Gertjan @Bangui91
                        last edited by Gertjan

                        @bangui91 said in Pfense Internet stop working. Only works after reboot:

                        WAN_DHCP 192.168.254.130: sendto error: 65

                        Hummm.
                        A Livebox from Orange. That's what i'm using also, here @work.
                        These boxes have a default LAN I of 192.168.1.1 using 192.1681.1.0/24 as their LAN network.

                        I changed it LAN network to 192.168.10.0/24 as I didn't want the change the default LAN I had before (in my company).

                        603dad8d-61b0-448c-bcc1-867b5b605e70-image.png

                        This way : nothing (literally) is needed to make pfSense work : it 's plug and play.

                        b46751d9-6a14-40db-b133-a4b6bbdf191e-image.png

                        My pfSense gets an IP from the Livebox, just like any other network device.

                        This :

                        @bangui91 said in Pfense Internet stop working. Only works after reboot:

                        dpinger 52155 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 192.168.254.130 bind_addr 192.168.254.13 identifier "WAN_DHCP "

                        Who is this "192.168.254.13" ???
                        Don't tell my it's the IP of your Livebox ....

                        Btw : The IP to pinged shouldn't even be the IP of your LIvebox. You should puck an IPv4 somewhat further upstream. You can find in the Livebox the gateway it uses, you could use that one for dpinger. Right now your testing the cable between your pfSEnse and the Livebox.

                        I advise you to shut down the IPv6 part of pfSense. The IPv6 network capabilitiesyour Livebox (Orange) is offering is totally useless for you.

                        Ditch the TPLink.
                        Managing a router-after-router-after-router is .... is most probably not what you want.

                        1. You use pfSense because its your choice.
                        2. The Livebox because this @=&é*$ Orange obliges us to do so, as I'm using proprietary VDSL right now myself, fibre coming up at the end of the month).

                        edit : precisions :

                        When you open the box of a new Livebox, it has pre set a LAN network of 192.168.1.0/24, the Livebox uses 192.168.1.1.
                        When you install a new pfSEnse it has pre set a LAN network of 192.168.1.0/24, pfSense uses 192.168.1.1.

                        Simpliy said : this gives a routing conflict, as you can't route 192.168.1.x to 192.168.1.y.

                        Make your choice :
                        Change the network "192.168.1.1" on your Livebox (make it, for example 192.168.2.0/24)
                        Or
                        Change the network "192.168.1.1" on your pfSense (make it, for example 192.168.2.0/24).
                        There is nothing more to do for a working set up.

                        No "help me" PM's please. Use the forum, the community will thank you.
                        Edit : and where are the logs ??

                        1 Reply Last reply Reply Quote 0
                        • J
                          jc1976 @Bangui91
                          last edited by

                          @bangui91

                          first go into the bios and disable hyperthreading.

                          secondly, list your network adapters. are they all intel or do you have realtek?
                          Everyone hates realtek because for the longest time, BSD was shipped with broken drivers.. pfsense version 2.5 finally included working drivers for realteks, however unlike intels that just 'install and work out of the box', you have to direct pfsense to use the new realtek drivers. i've seen the commands, it's very simple. just have to search for the instructions on what to do.. again, it's very simple and as a noob myself, i wouldn't be concerned.

                          third, you should list the packages you have installed for the seasoned vets to go through.. someone here will know

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