@pst so the NAS has multiple interfaces?

Normally the response from VLAN20 would be the VLAN20 gateway, which is pfSense, and pfSense would route the reply to the correct network.

I made a block rule for IGMP with no logging and my logs are clean again. I am missing the knowledge to have an opinion on this situation.

@stephenw10 said in Are we close to an RC release?:

Can't replicate the manual verification issue. It works as expected hen upgrading to the public RC for me.

There's no way to accidentally verify it at the console. There's no easy way to do it at all.

Interesting. Since the upgrade exceeded my 300 seconds defined interval, perhaps it just skipped it since the system was still being upgraded due to the other issue you just submitted to Redmine. Thanks for checking on it though!

Yup interface bound is definitely more secure. The floating states have surprised a few people in the past. I'm sure there will be some obscure setups that are unknowingly relying on them though. Even though they are almost certainly bad configurations 😉

24.03.b.20240322.1708 resolved this

1712246840439-screenshot-2024-04-04-090152.png

System installs and boots and functions

@rtorres lol As helpful as it is, and I love going to redmine and digging into stuff, I've learned long ago not to use it as a barometer for release date.

@behemyth said in DNS homepage display error:

I used to have those in my environment with longer uptimes than that. Unfortunately I get audited and I'm not allowed to use EOS/EOL gear at all, so most of them got replaced with 9400/9500's in VSS years ago.

When I worked at GM, we had a yearly exercise that required simulating dozens of every type of network failure that you can think of on the MFG floor, so the uptimes would never be more than one year. Stuff like simulated WAN circuit outages, switch port failures, etc. They didn't do that in the corporate offices though.

@stephenw10 The current 24.3.b.20240322.1708 upgraded without the looping.

Looks like it's still possible to hit this if you try hard enough. Fix is incoming.

OK that's correct. We'll dig into it.

Issue has been resolved.

You will need to go select previous Branch, Run pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade and immediately reboot.

Afterwards, select the new beta upgrade and hit confirm. I am now on the 24.03 beta. Thank you!

@tedquade said in upgrade from 23.09.1 to 23.04 fiails:

@rtorres With the dropdown set to 23.09.1 I ran the command, did a reboot then selected 24.03 and proceeded with the upgrade.

Ted

Oh my good lord, this fixed my issue... thank you!

FYI, it's still there even with this afternoon's build; however, if the initial timeout has exceeded, then it does not show up after the next logon. It's not something that 99% of people will ever see as I'm sure most don't perform another post-install reboot anyway.

Yup there was an issue with this mornings build and we removed the branch whilst we correct it. New builds are running now.

@yon-0 I ended up backing up my config & reinstalling. Installed the community version w/ zfs. Reloaded my config & then updated to the latest pfSense Plus build. No issues now. Apparently, the updater began requiring the ability to spin up zfs space for boot images. My install was too old. So just reinstall.

@ahking19 Seeing average of 15-18% on busy uplinks.

nvm fixed. (ignore)