Pfsense 2.3.1 boot without internet access?



  • When i setup a new pfsense to be deployed. I have a config file that has 90% of the config in it, this config also includes the wrong WAN IP for my bench area. When i restore a config it hangs booting at the following.

    Waiting for Internet Connection to update pkg metadata and finish package re installation
    Updating pfsense-core repository catalog
    Unable to update repository pfsense-core
    

    It shouldn't be able to access the internet at this point because the WAN IP is incorrect. When i ship it to the remote site it will be correct, but I like to make sure everything is setup correctly at our lab before shipping. The older version this wasn't a issue.

    I upgraded the pfsense to 2.3.1 p5 before restoring the config.



  • This does eventually boot fully after about 20-30mins.



  • +1 to fix this. I run into this all the time, and it's very annoying!



  • This is problematic for me too.



  • @djamp42:

    When i setup a new pfsense to be deployed. I have a config file that has 90% of the config in it, this config also includes the wrong WAN IP for my bench area. When i restore a config it hangs booting at the following.

    Waiting for Internet Connection to update pkg metadata and finish package re installation
    Updating pfsense-core repository catalog
    Unable to update repository pfsense-core
    

    It shouldn't be able to access the internet at this point because the WAN IP is incorrect. When i ship it to the remote site it will be correct, but I like to make sure everything is setup correctly at our lab before shipping. The older version this wasn't a issue.

    I upgraded the pfsense to 2.3.1 p5 before restoring the config.

    Maybe i misunderstand your situation,
    but what if you edit the config file and replace the "Wrong WAN IP" with 0.0.0.0
    If DHCP is active on the WAN side, the pfSense box gets instantly a new IP at the shipped location.

    Correct me if i'm wrong ?

    Grtz
    DeLorean





  • Thanks for the ticket, i'll check again next week, but i believe it also hangs without any packages.



  • @DeLorean:

    Maybe i misunderstand your situation,
    but what if you edit the config file and replace the "Wrong WAN IP" with 0.0.0.0
    If DHCP is active on the WAN side, the pfSense box gets instantly a new IP at the shipped location.

    Correct me if i'm wrong ?

    Grtz
    DeLorean

    I'm not using DHCP, i need to set a static WAN IP that will only work at the remote location.



  • I can confirm this happens without any packages in the restore config file.

    I also noticed another bug, when Restoring a config file with interface mis-match, it asks you to set the interfaces when you restore the config. This is normal, the system will reboot and it asks again, Do you want to setup Vlans? ect. This is a huge issue doing anything remotely as now you basically lost access until you get back to the console.