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

    WAN does not renew after reboot

    Scheduled Pinned Locked Moved General pfSense Questions
    51 Posts 7 Posters 10.7k 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
      Patch @stephenw10
      last edited by

      @stephenw10 said in WAN does not renew after reboot:

      Do you only have one WAN? If so try disabling the gateway montoring action for it.

      Yes one lan. I will disable monitoring to see if that help.
      Testing will be a challange as the failure is not frequent (about 1 / month atm).

      @stephenw10 said in WAN does not renew after reboot:

      Are you running Snort or Suricata in in-line mode?

      Neither.
      Have loaded pfBlockerNG-devel but notice no change since and not actually configured it.
      no other packages have been loaded

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

        Hmm, well unclear why it's logging a hotplug event then. But disabling monitoring action is a good test anyway.

        1 Reply Last reply Reply Quote 0
        • RyanMR
          RyanM @stephenw10
          last edited by

          @stephenw10 said in WAN does not renew after reboot:

          How exactly is it connected? Just to the main router or via some wifi bridge/extension?

          Right now I just have the WAN plugged into a switch on my network at this location. When I ship it home, it will be connected directly to the ethernet cable coming from the fiber optic "modem".

          @bingo600 good idea on disconnect/reconnect WAN after boot. I may see if that is a temporary work-around.

          @stephenw10 said in WAN does not renew after reboot:

          @RyanM When you generated that log was it only pfSense that was rebooted? The upstream router was not? Yet it still hadn't linked by that point?

          Steve

          Correct, I did not reboot the modem/router. I just booted pfSense.

          @Gertjan fascinating write-up on the timing of when dhclient is initialized and when my interfaces are "up".

          I am going to try adding that shellcmd package and the suggested command here after boot to see if it helps it pull an IP on this network. And I understand the behavior may be different at the other location, but I would at least like to see it work here first...

          1 Reply Last reply Reply Quote 0
          • RyanMR
            RyanM
            last edited by

            I used a different cable and am now seeing "1000baseT <full-duplex>" for WAN. I also moved the router to be on a switch connected directly to the Google WiFi that is acting as the router. Now my pfSense router is pulling an IP for the WAN when it boots. I think I am good. Will hopefully be able to ship this box home and get friend to plug it in and get internet at home working again.

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

              Nice result! 👍

              1 Reply Last reply Reply Quote 0
              • RyanMR
                RyanM
                last edited by

                Did a test where I plugged pfSense router directly into cable modem and was able to connect on mobile phone using VPN. I think I am in business. Thanks for the help.

                1 Reply Last reply Reply Quote 0
                • H
                  hoegge
                  last edited by

                  This is still an issue. On both my pfSense boxes, they do not take a WAN address by DHCP if the pfSense box is up before the Fiber modem connection, which is always the case after a power outage. That means you have to drive to the location to press the renew DHCP button. This cannot be right and is a real problem

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

                    @hoegge
                    That was discussed here recently. Also there were solutions or workarounds given: https://forum.netgate.com/topic/177429/3100-tries-to-configure-wan-before-fiber-modem-has-uplink/3

                    H 2 Replies Last reply Reply Quote 1
                    • H
                      hoegge @viragomann
                      last edited by

                      @viragomann Thanks a lot - I'll try that. Still don't understand, why netgate has not made the client continue retrying, if it has no lease. Must be a common problem, and e.g. in my case, I have to drive 200 km to fix it :-(

                      1 Reply Last reply Reply Quote 0
                      • H
                        hoegge @viragomann
                        last edited by

                        @viragomann Ah - looks as if this will be fixed in an upcoming release according to https://redmine.pfsense.org/issues/13671#note-2

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

                          It's a timing issue. The client cannot run on an interface that has no link so if it detects that it stops. When the NIC sees a link it triggers the client to start and it pulls a lease.
                          However during boot linkup events are suppressed because they are otherwise run repeatedly as each interface is configured. If your upstream device happens to have a boot delay that means the link comes up between the interface being configured and bootup completing you can hit this problem. It's not a huge window. Most users never see it.
                          It is a problem though and the patch on that bug report prevents it. Or just set the boot wait time higher to avoid it.

                          Steve

                          H 1 Reply Last reply Reply Quote 0
                          • H
                            hoegge @stephenw10
                            last edited by

                            @stephenw10 Thanks - I'll apply the patch - a delay is not really a robust solution, since you never know, what boots when and how fast.

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

                              Please leave feedback on that bug report if it works for you.

                              1 Reply Last reply Reply Quote 0
                              • P Patch referenced this topic on
                              • P Patch referenced this topic on
                              • G guardian referenced this topic on
                              • G guardian referenced this topic on
                              • First post
                                Last post
                              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.