@puneet1984 said in powerD only able to access one core: $sysctl -a | grep -i cpu1 hwpstate_intel1: <Intel Speed Shift> on cpu1 hwpstate_intel1: <Intel Speed Shift> on cpu1 hwpstate_intel1: <Intel Speed Shift> on cpu1 hwpstate_intel1: <Intel Speed Shift> on cpu1 You must have been running it when you took that sysctl output though?

Seems the PBR problem is part of a bigger one. The Alias, which has a list of entries that should be routed via PBR and is used in the ruleset as destination is miracously empty. I guess that's something to do with another patch but either way it is empty and thus routing doesn't work. Edit: sigh It's FQDNs. All aliases with FQDNs won't get correctly repopulated and are simply empty thus not working. I thought we already had that taken down... That seems very much like https://redmine.pfsense.org/issues/9296 again? But it's weirder as it seems every change currently in aliases, NAT, rules won't get applied at all and I have to go manually to filter-reload every time for it to show up. Just checked, duplicating a FQDN alias and it didn't show up in the tables. Only after manually filter-reloading it was there but empty. What's going on? Trying to reboot again after deleting all wireguard weirdness, hoping to get at least all other functions back. ... Edit2: OK that third? fourth? reboot seemed to have helped repopulate any alias at boot time correctly including DNS aliases. That way the PBRs are working again, the VPN GWs are again found. Good. Still NUT going nuts about any small change in packages, interfaces etc. But hey. Main things are again working normally...'ish. Funny enough, now that I deleted the Wireguard interface assignments and static routes, after the reboot the service is now in "started" mode again and seems to have started the tunnels (S2S and RAS) without their fixed interface binding again. Will have to see if I recreate the old settings or leave it running for now. ... Edit3: What the fruck? After the latest reboot it seems the package repository failures have righted itself (or Netgate's team has fixed it's certificate?) Either way pkg update is running again now.

@stephenw10 yes i guess you are right regarding the wait time for modem to restart.

@youcangetholdofjules [image: 1679300317423-fdd542f4-7e56-4ca0-b762-842b4e4a832a-image.png] If you have a solid "900 mbit" you will see no spreading what so ever when doing this test : https://www.waveform.com/tools/bufferbloat Or, I'll bet you will see some random spreading and even spikes while up and downloading.

@rcoleman-netgate, dear, 2.5.2 is just a stop on the way of trying to get an updated version to 2.6 functional for my scenario as 2.4 is at the moment, as you can see when upgrading to 2.6 the problem of accessing external hosts persists and yes, most likely there is something wrong in my configuration, I just want to know, if is possible, which direction to point to try to solve this issue [image: 1679287969175-30da97f7-0ff8-491a-ae2c-e6683f5e996e-image.png]

When were disabled DDNS and all IPV6 DNS servers as well on home router the problem is solved. Thanks to all for assistance!

@tman222 I cannot recommend a 1:1 clone of two different systems. I killed my installation twice with the import of the clone from my APU2 onto my I226 based. I had to crop quite a bunch of lines on the config until it worked. I can recommend Notepad++ for editing. There U also can edit the names of your interfaces like igb0-3 to igc0-4 like in my Case.

Yeah, that is a router. It might have a modem in it but if you're able to disconnect the WAN cable form there and it works in pfSense it probably doesn't. The actual modem is whatever's on the other end of that cable is the modem. You are replacing that router with pfSense so you need a switch on the pfSense LAN side to connect other devices. Steve

@viragomann RDP is allowed via the firewall. When enabling it, it seemed to do it automatically. Same issues on linux machines also.

I would highly suggest you use HA proxy and not use Squid for anything.

solved All done from the web gui Brand new install (with intel NICs) Restore old configuration (Realtek NICs) Pfsense will whinge that your interface assignments are incorrect. DO NOT REBOOT at this stage go to Interfaces | Assignments | PPPs edit the Link Interface to the Intel NIC repeat for VLANs Now Pfsense will ask to reboot - do it - now it works!

@Gertjan You wouldn't happen to have a Redmine account would you?

@stephenw10 Thanks, Steve!

@jimp said in Editing Aliases open wrong aliases: If you are on 23.01 and have applied the alias sort order fix patch in the System Patches package, then you'll need to update the system patches package again and apply one more fix from the list there. See also: https://redmine.pfsense.org/issues/14015 https://forum.netgate.com/topic/178813/problem-with-change-in-aliases-list-sorting-redmine-14015 You're a lifesaver :)

@viragomann You gem of a person! Seriously, I need to take myself outside for a vigorous uppercut - I completely overlooked that parameter! Thank you!!!!