I applied the 46b159032fef8c78783aa1a749d2238cfed7ac0d commit patch and can add my own confirmation to the group that the generated DNS access lists are working as expected.

I want to personally thank you @jimp for the work you put into this. :D I'm sure you've been busy with more higher-priority work related to the 23.01 release with how monumental of a change it really is. Changing both the PHP major version platform and language differences at the same time as re-basing work with skipping the entire FreeBSD 13.x series and going straight to the FreeBSD 14 code branch. That's no small feat to change both of those in a single release target, so bravo!

You'd have to reinstall 2.6 and restore a configuration file from 2.6 as well.

You cannot downgrade in-place and the newer configuration format may not be compatible with the older version.

Looks like it was from a recent sqlite change:

https://github.com/vergoh/vnstat/issues/243

https://redmine.pfsense.org/issues/14096

Looks like it isn't loading the ZFS kernel module since it says ZFS is an unknown filesystem.

Might be one you need to break out at a loader prompt and load the module manually, and then add it to loader.conf.local once you boot.

It did change somewhere between the 1st and 8th builds. I started a Redmine issue here:

https://redmine.pfsense.org/issues/14086

There are quite a few missing, it went from >800 modules to ~80.

@jimp

Thanks for this clarifying answer !

CE 2.7.0 snapshots aren't running right now as we're trying to do another merge with main for source and ports and so on. Once things are building smoothly again those will be re-enabled. When that happens you can just upgrade to the latest snapshot to get the package update.

@winger46146

No slow down here with 2.7. Speeds impressive and hanging in the 1.2-1.5 range on my Comcast multigig ISP.

@bmeeks That's because I am running pfSense 2.7 on my laptop in VirtualBox via WIFI and would not able to access LAN WebGUI so I can see what others are speaking of in diagnosing members issues, whether I am at home, friend's home or coffee shop. The LAN IP is static as my MacBook pro doesn't have an Ethernet port without buying a Thunderbold-3/USB-C to Ethernet adapter. Routing is possible, just not through pfSense in the traditional sense. Here is the dashboard...

Screenshot 2023-02-10 at 12.19.41 PM.png

@sergei_shablovsky said in Starting freeradius package so long (19min) ?:

Hi, pfSense Gurus!

Why starting freeradius package so long ?
(pfSense 2.7.0-DEVELOPMENT)

Starting CRON... done. .... Starting package freeradius3... done. [around 19min STUCK here] ....

Thank You so much!
Have a nice day!

[SOLVED] After last update 20230206 problem gone out. But need to Reinstall all packages... :(

You'll need to watch the console to see where it's pausing. Most likely it's waiting on a package to start or something else to initialize.

Cron tasks are in the background and would not affect the boot process in that way.

No, the NIC models only affect state sync, not DHCP sync. And even then the state sync isn't affected anymore since we moved back away from interface-bound states.

@louis2

I'm getting this message in log as well. Everything seems to be working though in terms of that interface, LAN, internet, etc.

debugnet_any_ifnet_update: Bad dn_init result from igc1 (ifp 0xfffff80001de7800), ignoring.

First of all, great that it started working!!

Right now, I need to figure out why it's still showing the TP-Link router login page even though I set up DMZ, changed the management port and management IP.
I think it might have something to do with the way how TP-Link is handling DMZ.

I don't see why it shouldn't... DMZ means all ports are open, not that the TP-Link "dissapears". It is still the gateway that pfSense "sees" and it's still doing NAT.

@bmeeks Thanks!

That worked. For some reason, when I initially told the setup to create a new certificate, it just created a private key and not the certificate. Jan 24 build however worked!

UEFI would achieve the same goal with much less impact. Especially if you can increase the resolution in the BIOS.

@nollipfsense

Did so. Now some of the participants in the bridged LAN aren't getting through and to the internet. Something is amiss with their parameters, etc. Plan is to take the bridge down, boot and start over with configuring the bridge.

3 out of 5 NIC's working fine. Just 2.... some times.....

The sleep it's referring to there is a sleeping thread rather than a system power state.

Yes comparing multiple crash reports is the next step here. If they are consistent it's probably a bug somewhere.

Steve

@nazar-pc https://redmine.pfsense.org/versions/70

I don't know if they're going for 100% resolution of bugs but I think that's the best we've got.

That appears to be a panic in the Realtek driver, so I'd start there. There is a package with a different driver (realtek-re-kmod-197.00) but it's anyone's guess if it helps on your hardware.

As for the performance loss, that is likely from the extra debug options we have enabled on development snapshots, though it's also possible it's related to the Realtek drivers.

@steveits This worked like a charm!!! I was getting worried when I wasn't getting any response back from the box after 20 mins. But this ran and completed without issues!!!!!

Cheers to netgate!

Nothing changed anywhere near booting or video in the FreeBSD src repo between then (or even slightly before/after), and I don't see anything relevant in the other repos either, so it's odd that it seemed to happen around then.

I followed the instructions in the link if you’re trying to update from a previous 2.7 development version.

It worked great.

The last two steps say go in Debug mode and check….

How do you get into Debug mode?

@steveits
Thanks for your help.
I guess I will try another token and if it still has problems I'll go with 2.7 for the foreseeable future.

@jimp said in 2.7 Avahi missing interfaces:

The WAN interface is automatically excluded from Avahi because Avahi should not be run on a WAN.

Though these days with any interface being capable of acting in any role that doesn't make as much sense as it did in the past, it's primarily an anti-foot-shooting measure to make sure someone isn't exposing private data on a public link.

Should probably edit the Interface Action description to remove confusion.
avahi.png

@jimp

I did not see this problem any more in the past two weeks. It must have been some issue which have been fixed in the builds since than.

Louis

pfSsh.php is fine on PHP 8.1, the problem is in that code.

You can't blindly access multi-level arrays without initializing them properly anymore in PHP.

https://docs.netgate.com/pfsense/en/latest/development/php-config-arrays.html

You'll need to download and attach one of the crash dump files (e.g. textdump.tar.0, rename it to textdump.tar) or at least extract the text files from it and post their contents. The firewall should be offering to let you do this from the dashboard when you log back in after a crash.

The two most important parts are ddb.txt and msgbuf.txt which will have a lot more detail about the crash and why it happened.

@roach32 I believe it's there to aid the developers and recommend leaving it alone Be patience, we're close to a release candidate soon.