@chpalmer said in Strange behavior with gateway:

???

When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365
That's unexpected.

@coxhaus I no longer care either because the source code does not seem compilable for the average use. I used to have fun with compiling many years ago as a former smoothwall user.

While it may be preferable not to give the source away, the fact that pfsense if forked from an open source project (monowall) two decades ago may still require this. (I am not a legal expert on open source licensing.)

To bring this back to the title of the topic, this is solely about the release of an iso of the full compiled v2.8.0 for direct installs, not asking for anything more.

@jc1976 said in Squid on 2.8:

upgrade an issue developed between suricata, pfblocker, and unbound. when i disable the two packages, all works fine

Let's consider :
If you leave the 'unbound' (the resolver) settings to "all default", the way you found them when you first installed pfSense.
You remove / don't install the extra stuff = suricata and pfblocker.
Then : no issues what so ever.
Right ?

This means your issue isn't "pfSense 2.8.0" or the upgrade. Its an 'ordinary' package settings issue - call the admin 😊

Tell you boss that suricata can only filter non TLS traffic **, something that doesn't exist anymore. Check for yourself : who visits http (port 80) sites these day ? Who collects mail using port 110 ? Who sends mail using port 25 ?
Imho : suricata, for what it's worth, can't do much these days, it can 'see' the data payload in the packets. Everything is TLS these days.

** It is possible to do TLS filtering, but that demands a 'proxy' setup, making you a real expert.

pfBlockerng is blocking you, DNS or something else ? That's any easy one, and rather simple do debug.

I had same issue for a long time.

Then I tried pkg update -f and got an error for SunnyVally repository
I figured that I had a old version of zenarmor installed that matches the FreeBSD 14 and not 15.
Upgraded the zenarmor to the latest version.

Haven't had any of the error messages for some time now. hopefully that was it.

Maybe this can be helpfull to someone.

@stephenw10 Unfortunately I am going to have to wait till I can bring down the network to test. If I take it down now and it doesn't come back up I will be having some hell to pay from the family...lol. 😃

@Wolfgangthegreat
...and to @comet424

I wasn't able to perform the 2.8.0 update this weekend, but when I got to the school this morning, it worked perfectly!

I appreciate the support from both of you, and from Netgate.

The backup/standby pfSense instance is back in place and ready in case I have a hardware failure, or a failure of the gray matter between my ears!

My best to all of you.

@Wolfgangthegreat For example (this is checked by default):
8544523b-d69b-4088-b221-d2532912455c-image.png

There was a backend issue that's now fixed.

Yup, there was a backend issue. Should be good now.

The repo seems to be back online today Jul 19th, I was able to complete the fresh install.

Hmm, but they are policy based tunnels? And 300 Phase 1 configs not a total of 300 Phase 2 configs for example?

I'm not aware of any issue in 2.8 that might present like that for IPSec.

and then it worked...

@PiAxel said in update from 25.07 beta to 25.07 RC:

The last version doesn't work for me!

??

How do you know that the latest version doesn't work for you, before installing that latest version ?

( 😊 )

@jc1976 can you check if you hit the same issue as: Squid: "Undefined symbol "_ZTVNSt3__117bad_function_callE" after upgrade to 2.8?

@NetworkNerd Just in case you haven't tried this yet. The new Netgate online installer does provide you the option to set up the WAN interface connection details such as PPPoE etc as part of the process. I'm not a fan of the choice to remove offline installers by any means but at least they do provide this functionality.

may be I go the issue we just nee dot reboot the firewall and select the old kernel and boot the firewall after boot it will reboot again and you can access the latest version of firewall which 2.8.0 I tried and it work for me.

@stephenw10 I a not using squid guard so I have to enable and check, I enabled the squid proxy server and squid guard proxy filter they both are running fine without any errors.
Thanks for the help and quick response

For future reference you should always be able to upgrade to the newest offered version in one step. We test upgrades from the previous two versions.

@stephenw10 said in Kernel Panic when Upgrading to 2.8.0 beta:

Hmm, interesting if it's really disabled in the BIOS pfSense shouldn't see it at all. Something not working right there.

Reply

Correct. Under the list of devices in the BIOS on the NUC, WiFi is not checked.

...well, after some false starts (like loading 2.7.2 and running into different interface names on the new hardware (i,e. igc0 vs igb0, etc..) which did not allow th eloading of my VLANS etc... I ended up editing the backup config file, replacing "igb" for "igc", and loading 2.8.0... all is working great now on the new hardware.... I will wait until I can upgrade from 2.8.0 to Plus... reason to go to Plus is to contribute $ to the project, as I have been using pfSense for free for years now... am recently retired and delving into IT and learning as I go... Thanks for all the replies and suggestions !