PfSense 2.3 LAN interface stops routing traffic - stops working after 2 or 3 day
-
@cmb:
The fix for this was merged this morning and is in the most recent available snapshot, Thu May 12 14:01:47 CDT and newer.
My test setups are around 4.5 hours run time in a scenario that never lasted more than 3-4 hours without the fix. Another user who had a circumstance that was much faster to replicate than anything I could duplicate in a lab (a matter of a handful of minutes, rather than hours) has also confirmed it's no longer happening.
Needs more runtime and more feedback from others, but initial results are good.
Those of you impacted, please upgrade to latest 2.3.1 (instructions here), remove the disabling cores workaround if you did that, and let us know how it goes.
So I followed the instructions on that page, and I get an error if I try to upgrade using the development option on the updates settings.
ERROR: Error trying to get packages list. Aborting…
pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/packagesite.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/packagesite.txz: Forbidden pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required
ERROR: Error trying to get packages list. Aborting...
pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/packagesite.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/packagesite.txz: Forbidden pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' requiredAlso, afaik the option to upgrade from local file is no longer an option?
So unless I save it to a usb, and drive over to the other location, what can I do? -
Things are looking good so far according to all the posts by others. Nice job dev team! It looks like 2.3.1 is getting close to a final release now. Only issues set for 2.3.1 release are now in feedback status…
-
So I followed the instructions on that page, and I get an error if I try to upgrade using the development option on the updates settings.
ERROR: Error trying to get packages list. Aborting…
pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/packagesite.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/packagesite.txz: Forbidden pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required
ERROR: Error trying to get packages list. Aborting...
pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-core/packagesite.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/meta.txz: Forbidden pkg: http://firmware.netgate.com/beta/packages/pfSense_v2_3_amd64-pfSense_v2_3/packagesite.txz: Forbidden pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' requiredLooks like you're on the factory image, not CE, so the snapshots aren't available there currently. I'd suggest waiting for 2.3.1-RELEASE which if all goes as planned, will be first thing next week. You could, potentially, switch to CE snapshots but you'd lose the factory image tweaks/extras.
-
Looks like you're on the factory image, not CE, so the snapshots aren't available there currently. I'd suggest waiting for 2.3.1-RELEASE which if all goes as planned, will be first thing next week. You could, potentially, switch to CE snapshots but you'd lose the factory image tweaks/extras.
Sure, that makes sense. Now I know why I don't see "Community Edition" on my UI, didn't realize there was a tweaked version on my system. In the past I've run the CE edition (obviously not on this machine).
-
If/when 2.3.1 comes out next week, if I have already botched my Factory system by syncing up with 2.3.1CE is there any way to get back on the Factory track? Or if I do a backup/format/restore would that work?
-
If/when 2.3.1 comes out next week, if I have already botched my Factory system by syncing up with 2.3.1CE is there any way to get back on the Factory track? Or if I do a backup/format/restore would that work?
It's not quite that easy. It can be done with some file edits and such but it's not a very clean switch. Overall, less effort to reinstall+restore.
-
Overall, less effort to reinstall+restore.
ok so just to confirm, I can just pave, reinstall, and restore the config.xml – no extra tweaks or edits needed? thanks again
-
jimp, could you quickly comment on what caused the issue??
-
jimp, could you quickly comment on what caused the issue??
If you mean the original problem from this thread about the traffic stopping, I don't personally have that info. Should be on the tickets and/or in the commit history. It was something in the IPsec code, IIRC.
cmb is on a plane at the moment, he might have some more insight when he's able to respond.
-
We have the IPsec code from FreeBSD -CURRENT in 2.3.x. At the time we merged it in, there was an issue that wasn't identified and fixed until later. The fix was to re-merge all of IPsec from -CURRENT.
-
Looks like you're on the factory image, not CE, so the snapshots aren't available there currently. I'd suggest waiting for 2.3.1-RELEASE which if all goes as planned, will be first thing next week. You could, potentially, switch to CE snapshots but you'd lose the factory image tweaks/extras.
First thing next week, so is that today? Do you know if it is today?
-
The process has begun but we need time to test and such, so probably not today at this rate, but we'll see what happens.
The factory images gained access to snapshots late last week so you could run a snapshot now if you want, but with the release being so close, you may as well wait another day or so for it.
-
@cmb:
We have the IPsec code from FreeBSD -CURRENT in 2.3.x. At the time we merged it in, there was an issue that wasn't identified and fixed until later. The fix was to re-merge all of IPsec from -CURRENT.
OP checking in.
Looks like everything is good to go now. It's been up for over four days and not a single issue. Thanks for taking care of this! I anxiously await 2.3.1 so I can deploy to the rest of my sites!
-
The process has begun but we need time to test and such, so probably not today at this rate, but we'll see what happens.
The factory images gained access to snapshots late last week so you could run a snapshot now if you want, but with the release being so close, you may as well wait another day or so for it.
Well tried again for the factory image snapshot, however still getting an error when trying to get the update list. Hopefully 2.3.1 release will be out soon.
-
Hi,
running 2.3.1-DEVELOPMENT (i386) on net6501-70pfSense crashes EVERY time the remote IPsec user connects and attempts to access some Web pages on a local network.
SSH seems to be more stable. Submitted the crash report via Diagnostics/Crash reportsTried to disable one CPU - has no effect on the crash.
IPSec is not usable for us at this point … -
Crashed again during work hours :-, any eta on this (first thing this week) release for the factory image? There are no snapshots available.
-
FreeBSD released a couple security advisories yesterday evening, which means we had to rebuild the images and do all the testing again, so we're still in the middle of all that.
-
FreeBSD released a couple security advisories yesterday evening, which means we had to rebuild the images and do all the testing again, so we're still in the middle of all that.
OK thanks. Any ETA though? I don't know your testing process and how long that takes.
-
If we don't find anything, release will likely be later today, but we like to err on the side of caution.
-
If we don't find anything, release will likely be later today, but we like to err on the side of caution.
Thanks, good to hear.
