To 2.5.1 or not ? that is the question :)
-
while tried to decide pfsense vs opsense. I choose pfsense because of stability :D
-
@yanik Me too! Well let's give the dev's time to fix this. In the meantime I am planning to do a clean install of 2.5.1 and the restore my config. If that does not work I will revert back to a clean install of 2.5 and then restore my 2.5 config. I will make some time tonight to do this and I will post my updates here.
-
We can continue here: https://forum.netgate.com/topic/162952/port-forwarding-on-openvpn-interfaces-is-broken-on-2-5-1
-
Good luck :)..
Sure devs will fix this but i hope it wont take much time. at least a patch would be nice.
-
@yanik Add me to the "Port forward works only on interface with default gateway, does not work for alternative wans" victims list...
I know, I know, "pfSense CE is free", blah, blah, blah, but it is also undeniable that pfSense CE (formerly just plain pfSense) is, today, quite far from the rock solid firewall distro of a few years back, when I used to upgrade without any trepidation.
Also, the fact that this very serious bug has been fixed in the commercial version, but not the free one (did no one at Netgate notice that the fix was relevant for CE also?!?!), makes me wonder...
-
@cellobita wow I did not know that that port forwarding on OpenVPN was a bug for the Plus version and they fixed it! Do you have source where I can read this?
-
@vjizzle It was on the bugtracker for version 2.5.1 for many weeks - I was following the link below closely - and when it was fixed someone said the issue did not occur on CE; since it was a pf issue, I'm note sure how that could not affect all versions (please keep in mind that I am not a developer or software engineer, just a tech savvy guy).
The issue tracker has been added to a few minutes ago to note that the issue is now(?) happening on CE too.
-
PS: I do fervently hope, since this is most likely the exact same issue as on the Plus version, that Netgate issues an emergency patch/version ASAP (2.5.1-p1 or something...)
-
Ok maybe unrelated but my pfSense suddenly stopped NAT-ing new sessions. For example my Citrix session to work was running fine but when I tried opening websites for the first time today I was not able to open them. DNS was resolving them fine. Restarting Unbound did not solve it. I had to reboot the firewall to make everything work again. Tonight I am definitely going back to 2.5 :(
-
@vjizzle Good luck.
I'm not the kind of consumer that Netgate wants or needs, as of 2021, so they couldn't care less about what follows, but anyway:
This is the first time in over ten years - since switching all my customers from IPCop - that I'm looking closely at the alternatives for pfSense. Sad.
-
Forgot to backup on 2.5.0 and I'm stuck on 2.5.1 with this problem...
I hope on a workaround until they release a fix. -
@dredex If it is that important you could download 2.5.0 from
https://atxfiles.pfsense.org/mirror/downloads/or
https://nyifiles.pfsense.org/mirror/downloads/ Before installing I would
check the hashes https://nyifiles.pfsense.org/mirror/downloads/ or find
some University site that has them of course all on you own risk. -
@qinn Thanks but I don't have a backup config from 2.5.0
-
You can use the current config from 2.5.1 never had trouble using a config file among versions.
-
So I some time ago installed 2.4.5.
This was upgraded to 2.5 and then to 2.5.1.
I have a firmware of 2.4.5 that I downloaded from my web GUI when I installed it.
If I use this 2.4.5 firmware on my 2.5.1 current box, will I still be able to use 2.5.1? -
@bismarck said in To 2.5.1 or not ? that is the question :):
Root mount waiting for: CAM
That message shows in dmesg on 2.5.0 as well so it's not new in 2.5.1.
@waqar-uk said in To 2.5.1 or not ? that is the question :):
I have a firmware of 2.4.5 that I downloaded from my web GUI when I installed it.
If I use this 2.4.5 firmware on my 2.5.1 current box, will I still be able to use 2.5.1?By "downloaded from my web GUI" do you mean you downloaded the 2.4.5 .iso file from Netgate? Or saved a configuration backup (.xml file)? You can always install whatever version software you want, and restore a configuration backup. You will be able to upgrade again in the future.
Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
Upvote 👍 helpful posts! -
@steveits New at least for me, was that the root partition was gone and this error message was looping on the screen for ever.
-
As I was affected by the IPV6 gateway bug that also affected the floating IPV6 rules as you couldn't specify the gateway, I had updated to the RC about a week ago. I was too nervous about using a RC build to do so earlier but finally figured, it was probably less buggy than 2.50. So now I see the 2.51... I DO have a 2.45 installer and a 2.50, along with configuration backups and will probably go back to 2.45 if 2.51 is a dud... So I just went 'what the heck' and clicked update... Watched the update process in the GUI, and the reboot went off without any issues. Logged back in, and remembered to be patient and let it reinstall packages/restart services. Waited and watched on the Dashboard. I'm running Snort, PFBlocker, Service Watchdog and OpenVPN Client Export. Everything came back up in less than 2 minutes. Checked the logs, looks ok so far. My setup is lan and two vlans, one wan.
-
So I did get to nuke my 2.5.1 install tonight. I was also experiencing stability issues with it so I just stopped troubleshooting. Got fed up with 2.5.1.
Anyway, I did a clean install of 2.5, restored my 2.5 config and waited for all the packages to install. I am using pfBlockerNG, Suricata (only on a DMZ interface), OpenVPN client export and Service Watchdog (because Unbound is randomly crashing on 2.5). After that I went to check if port forwarding is working on my OpenVPN interface...and BINGO! Port forward on OpenVPN interfaces is working fine again!
I recommend to stay away from 2.5.1. I know I am using the CE edition and maybe I complain too much but if Netgate's own hardware would be more stable and everything working fine, I would gladly spend the money and buy it since this troubleshooting is costing me a lot of time. But seeing how unstable pfSense 2.5 and 2.5.1 is on Netgate's own hardware got me seriously considering other options. For now I need to take a break from this headache and will let it run 2.5 since this is the version which ran fine for days without issues. 2.4.5 p1 ran amazingly fine as well but going back to that older version now means to deal with packages which are "old" as well. Too much of a hassle this :(
-
Went from 2.5.0 single disk ZFS to 2.5.1 this AM.
No problems that I am aware of.However, my LAN Traffic Graph is STILL blank, that happened when going to 2.50, sigh...
