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

    Now Available: pfSense® CE 2.8.1-RELEASE

    Scheduled Pinned Locked Moved Messages from the pfSense Team
    21 Posts 12 Posters 4.0k Views 17 Watching
    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.
    • GertjanG Offline
      Gertjan @Wylbur
      last edited by

      @Wylbur said in Now Available: pfSense® CE 2.8.1-RELEASE:

      . I just dislike going back through manually putting in the various IP pools and static addresses for my network.

      That's why you have to put all chances on your side.
      As already said above : make use of the very single reason why pfSense exists (in the first place) : this is not the presence of a GUI t set things up, it's the fact that you can 'backup' or 'save' one single config file, and later on, on the same system ( ! ) you can install from an USB drive, do minimal initialisation, probably mostly accepting the default) and as soon as the GUI comes up : import the config, and 'done'.
      If your connection is slow, or you have (had) many pfSense packages installed, just be patient. All packages will get installed 'fresh', and their settings will get applied before they are started.
      Be ware that race conditions can exist, like you use the OpenVPN (client or server) and to opted for FreeRadius authentification, but the pfSense FreeRadius package wasn't installed yet ...
      So, when hing have settled out, the dust is cleared, just reboot pfSense (GUI or console command) onces more.

      My update/upgrade check list :
      First : if you made any special changes to your system, document them all. Use for example the pfSense Notes packages, as this info will get stored in the config file, so it will be in your backup.
      Before you update/upgrade, go to the console or GUI, and restart the system.
      It would be perfect if you could use the console access (not SSH) and log this reboot process.
      Scan that log for any potentiel issue. This will be the perfect moment you'll your disk is full - or in bas shape (disk always die)
      Let your system running for a while, and test any functionality that you depend on.
      Then use the same console access (or SSH) to do the upgrade. If possible, have this logged to disk on your device. If an issue shows up, you have a trace. If you have trace, you can copy past here exactly what happens, so we see the exact issue, so fast answer are possible.

      Me writing all this took probably more time as you doing all this.
      Getting experiences in learning all this isn't lost time. The day a re install really counts, and it has to be done fast (as always), you know the drill.
      This was previously known as 'learning'.

      Using a plan and prepare well with reverse the Murphy's law : all your good preparation will be for nothing as everybody goes smooth.

      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 1
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.