 Time here for more systems MPF sense 2.5 2 has been released was actually released a few days ago I've been following it on reddit and of course talking to people I know and you know doing the usual Updating internal systems that we have here and so far it's gone really smooth now let's jump into though the major features in the 2.5 2 and The first one is this one right here I know this is a bug that's plagued a lot of people and been waiting for it to get fixed Which is port forward rules only function through a default gateway interface reply to does not work in multi-wan. This has been fixed I'm thrilled because this is obviously something that hung up a lot of people on upgrading and that's if you have port forwards on multiple Different IT ISPs essentially those port forwards may not work properly and in a multi-wan environment, so we did actually have at least one client I believe that this was a big hang up for them and yes This is obviously an issue, but it has been addressed the next big issue that has been addressed is going to be wire guard now Wire guard sorry if you loaded it in 2.5 0 as a built-in function It will not transfer into 2 5 2 because it's been moved over to a package So because it's a package or add-on that you install so system and go to the package manager You can add wire guard It won't import your settings. You're gonna have to rebuild your tunnels There's no direct path for doing that but nonetheless wire guard is back for those of you that are interested in using it and I also did take down my previous videos because it's Implemented slightly differently here, so I will make new tutorials But for the most part if you had figured it out in 2.5 0 it works very much the same It's still wire guard. They've just added more features and a little bit of nuance difference and you know enhance the interface a little bit I like what they're doing here. I really like to see the way this project's been progressing. It's been great now back over to the next thing that I know a lot of people want to know about what about unbound and That is another one. I know the crashing of unbound and you can use the Watchdog system to restart it, but I see it shouldn't crash and they have made the change to temporarily move back to unbound 1.1 2x due to instability of unbound 1.1 3x and it's pretty important because Well, we don't really want DNS crashing DNS is Well the source of many problems in general we don't need more of them to be part of the crashing So I'm happy that they solve that problem and this is always some of those challenges They have over it, you know neck 8 pf sense of you know upstream products having Updates that have unaffected consequences when you integrate them as a whole but hey They did solve it and like I said temporarily downgrading that no problem now also in this list of Things they fixed here. We're a lot of dynamic DNS Options now they added a quite a few new ones and I really like that they stay up to date They offer quite a few of them on here But unfortunately, I don't really use dynamic DNS for a lot of what we do But I know a lot of home users do so I think this is particularly important in the CE edition when people just don't have access to Static IPs and they do stay on top of that So it's a lot of little fixing that was done in here and a lot more services added Now I'll leave a link to the page because there's a ton of little fixes that were done in this particular update But overall, I don't see any challenge or reason. You shouldn't update to it This kind of rounds out some of those problems that you know when you do a major version upgrade Some of the problems that may come with it seem to be pretty rounded out and stable now at the 2.5 2 But before you upgrade, let's talk real quick about the upgrade process back up Please have a backup of your configuration file prior to doing it. I Don't feel like I should say it every time because I by now I thought people would know but I still get a lot of Forum posts and things like that of I didn't back it up And I need to figure out how to recover it off the system, but please back up I must say that every time I guess next Reboot your system prior to update go ahead and restart it once to make sure it boots up fine because if you have some pending Problem, let's say a hard drive failure So it cannot read before or a SSD failure if you cannot read the drive But it has read it into memory. So the system's got this amazingly long uptime the next reboot may not reboot So if you compound that problem by also hitting upgrade then reboot, yeah, maybe an issue So I usually go through one reboot cycle cool It came back up now we'll go ahead and do the update next package updates I've reiterated this a few times This is very clear to me and the pfSense instructions But seems to be confusion sometimes when I'm looking at some of the forum posts on Reddit When you are running the current version of pfSense you should keep all your packages up to date If you decide to stay back a version on pfSense the packages still keep moving forward They are going to expect to be on the latest version now package updates may or may not require the newest version But if they do and you're a version behind now, there's a problem So it is best practice to stay on the current version of pfSense But if for some reason you are not on the current version Then you should not be updating the packages prior to getting to the new version of pfSense So this is where some people can sometimes break or crash your systems because yes pulling the latest packages when you're running versions Behind can definitely be issues I just want to bring that up because I think it adds a little bit of confusion sometimes But my overall is I think 252 is a great stable version that you should probably be jumping on and getting up to date on and new wire guard tutorials I'll be working on and of course more people be doing some write-ups and Oh using the new wire guard system now that it's available in there So I don't see any reason not to go to this version It seems to solve a lot of problems that people were having and if you read through the fixes There's actually a lot of little details But they do cover a lot of edge scenarios where people have specific use cases that may have had problems in the 25 and the 251 That should be solved in 252 and if they're not hey get out there and report the bugs because that's what lets the team know That your configuration needs to be addressed And then they start working on it. All right and links below to everything I talked about and see in the forums Thanks And thank you for making it to the end of this video if you enjoyed this content Please give it a thumbs up If you like to see more content from this channel hit the subscribe button and the bell icon To hire a sure project head over to laurance systems.com and click on the hires button right at the top To help this channel out in other ways there's a join button here for youtube and a patreon page where your support is greatly appreciated For deals discounts and offers check out our affiliate links in the descriptions of all of our videos Including a link to our shirt store where we have a wide variety of shirts and new designs come out well randomly So check back frequently And finally our forums forums.laurancesystems.com is where you can have a more in-depth discussion about this video and other tech topics covered on this channel Thank you again, and we look forward to hearing from you in the meantime check out some of our other videos