@anaerin And it looks like that fixed everything. Thank-you very much for all your help.

I looked things over and it does appear to just be NCP that needs taken out. I created https://redmine.pfsense.org/issues/14201 to take care of that.

According to the bugtracker you can turn off these excess messages. See https://redmine.pfsense.org/issues/14163 Go to System / Advanced / System Tunables. Add an entry for net.netlink.debug.nl_generic_debug_level and set it to 7. [image: 1680102265433-02e236b6-03e3-42d0-888e-e3f1790d77ea-image.png]

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.

@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... [image: 1676053240727-screenshot-2023-02-10-at-12.19.41-pm-resized.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.