pfSense Plus 21.05-RELEASE Now Available

johnpoz

Exactly - I do not have any sort of support contract.

Just go here and create an account.

https://go.netgate.com/support/signup

Then create a ticket requesting firmware or maybe software upgrade prob would of been better. There are drop down options for what the ticket is for, etc. I will have to remember that for next time. Last couple of requests I have used firmware access - and just in the body of the ticket state what want - install image for whatever version your looking for, etc.

example - here was my ticket requesting 21.05

You can view your netgate id and serial number in the web gui

viktor_g

@maxk-0 said in pfSense Plus 21.05-RELEASE Now Available:

Bug #11466 is still open for SG-3100. Is there a target release when this will be resolved?

You can fix it by applying patch https://redmine.pfsense.org/issues/11466#note-32

Ramosel

@johnpoz said in pfSense Plus 21.05-RELEASE Now Available:

Thanks - already got 21.05 image from support. Just in case. 5 minute total time of submit ticket to when I had link to image file for "just in case" use..

John... they must not like you anymore... 5 minutes... pffftt! j/k

I didn't get to things until late this afternoon and even "after hours" (7:17pm Texas time) my response time was less than 2 minutes. You just can't complain about that.

Rick

MaxK 0

@viktor_g Thanks. I saw that patch/workaround too but would like to know if/when a fix will be incorporated into the next release.

johnpoz

@ramosel said in pfSense Plus 21.05-RELEASE Now Available:

response time was less than 2 minutes

haha - yeah they pretty much johnny on the spot for sure.. Now when 2.5/21.02 first dropped - there was a bit of delay.. It was like 28 minutes ;)

KOM

Upgraded my SG-1100 this morning. Everything went well during upgrade. After reboot, Unbound was stopped and I had to manually start it. Probably due to Unbound being down, pfB said it was out of sync and a manual force reload was required to fix it. No issues otherwise.

bmeeks

Just to give a data point with a positive experience (since it is mostly the users who have problems that post about them, and that can skew the perception of how stable an upgrade might be).

I updated a plain-vanilla SG-5100 to 21.05 from 21.02.1 without issue. Plain-vanilla means no site-to-site VPN, no multi-WAN, and no shapers/limiters. Only installed packages are Snort, apcupsd, and the OpenVPN Client Export package.

defunct78

Upgraded a SG-1100 successfully. Took about 10 minutes and everything came back just fine.

brians

Update a 4560 remotely last night but my VPN tunnel did not come back. Fortunately I have other means to gain access to domain controller via my map tools. I noticed that unbound service was not started so I manually did which resolved issue. Since I use a host name to resolve IPSec endpoints this explains. I have noticed on many upgrades that dnsresolver needs to be manually started after upgrade.

Next one I do I’ll set override dns for pfsense to google first.

CSstefan

After upgrading my sshuttle connections stopped working.

SebM

5100 upgraded from 21.02.2 to 21.05 with no apparent issues.
My always-on OpenVPN client connection came back up with no issue.
It was quick.
Happy :)

NGUSER6947

@sebm said in pfSense Plus 21.05-RELEASE Now Available:

21.02.2 to 21.05

I did mine yesterday (21.02.2 to 21.05, SG-1100), took exactly 10 minutes, zero issues.

Nice job, Netgate team! Thank you.

Adrianoebm

@nguser6947 said in pfSense Plus 21.05-RELEASE Now Available:

@sebm said in pfSense Plus 21.05-RELEASE Now Available:

21.02.2 to 21.05

I did mine yesterday (21.02.2 to 21.05, SG-1100), took exactly 10 minutes, zero issues.

Nice job, Netgate team! Thank you.

Are you sure that it is zero issues?
We have seven here, our CPU is 100% almost time and sometimes i can´t access the web GUI anyway, the solution is to take off the power cord.

NOCling

Looks like this:
Link

brians

@adrianoebm I seen that on a 3100 months ago when I restored configuration from a different device. I think the issue may have been packages trying to install that were not compatible but I ended up resetting it and not using it.

I would suggest backing up the configuration and skip packages, then do a restore and see if that resolves.