Now Available: pfSense® CE 2.8.1-RELEASE
-
@randombits said in Now Available: pfSense
CE 2.8.1-RELEASE:I'll stop the watchdog for the time being, it's never been a problem before.
As I read the code (with my humble knowledge) the killing of the openvpn process was konflicting with watchdogtrying to restart the process (that was dead in his eyes). IMHO
-
@fireodo
It appears something like that, I've removed the Watchdog anyway and I'll see how it goes. -
Any news for the Zabbix Proxy 7 package?
-
@sandrinho1976 said in Now Available: pfSense
CE 2.8.1-RELEASE:Any news for the Zabbix Proxy 7 package?
Is this what you're looking for?
-
Hey Mates, Just completed an upgrade to 2.8.1 from 2.8.0 all is working fine, no crushes despite ignoring the instructions to first remove all packages before doing the upgrade.
I went with my way, and all is perfect. If you haven't please do the necessary.
Africa is up-to-date.............
-
This post is deleted! -
Has anyone updated from CE 2.7.2 to 2.8.1?
I'm asking because the upgrade to 2.8.0 for me failed and recovery required re-installing 2.7.1 (ISO), and then upgrade to 2.7.2 (which I've been running for a while now).
Since I have two systems, I can upgrade the one and keep the other as a backup.... I just dislike going back through manually putting in the various IP pools and static addresses for my network.
Regards,
Wylbur -
@Wylbur worked fine form me
I suspect the easiest is to- backup your pfsense configuration
- Connect your backup pfsense routers want to your main units lan (so you can crash the backup unit and your internet continues to function
- Download pfsense iso v2.70 v2.71 v2.72 from https://atxfiles.netgate.com/mirror/downloads/
- download the free pfsense installer (internet connection during install required) from https://shop.netgate.com/products/netgate-installer
- Try installing various versions of pfsense to confirm which are compatable with your hardware
- restore your configuration to your preferred working pfsense version
-
@Wylbur worked fine form me
I suspect the easiest for you is to- backup your pfsense configuration
- Connect your backup pfsense router WAN to your main units LAN (so you can crash the backup unit and your internet continues to function)
- Download pfsense iso v2.70 v2.71 v2.72 from https://atxfiles.netgate.com/mirror/downloads/
- download the free pfsense installer (internet connection during install required) from https://shop.netgate.com/products/netgate-installer
- Try installing various versions of pfsense to confirm which are compatible with your hardware
restore your configuration to your preferred working pfsense version
(re-entered as editing prior posts is not working atm)
-
@Patch Thanx. I'll find time to set up to do this. I just wanted to not be a guinea pig for this update. Last time it took me a few hours to re-install and configure both fire wal/gateway servers.
-
@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.
