well done,

$response = curl_exec($ch);
$output = json_decode($response);

could be it

Apologies for the delay, but having got the issue fixed I thought it would be worth adding a note as to what the problem was rather than leving it dangling.

Thanks for the help of @stephenw10 who checked the (two different) NDI (Network Device Id) that were showing up on the sytem against the pfSense registration db, and fixed the registration there to be correct.

Somehow, most likely due to me having played with the network devices in the config and then reloaded it, the pfSense plus registration did not match the device id. Once that was fixed I could get the package database and install packages again.

Nigel.

Hmm, so removing the duplicate gre entries resolved the issue?

@JKnott said in HP Desktop w/Intel Core i5-7400:

apcupsd
Backup
frr
iperf
nmap
openvpn-client-export

Thanks - that explains why your CPU-Load is so low at high speed transfer! (no pfblocker and or IDS/IPS)

@kevin-ruffus yes

@stephenw10 Still at the top of the rule set.

I made sure to make the following change overnight.

fc6d16b2-98c7-4fa1-8dab-36fd1a8f4ea0-image.png

I know this is an old post but....this worked for me too. I bought a Beelink EQ-12 for pfSense. It uses the Intel i225-V ethernet controller. I installed the release version of pfSense and the nics were not found. I tried a recent dev snapshot (2.7.0-DEVELOPMENT-amd64-20230605-0600) and it's working.

Thanks for helping me solve my problem!

@nanobist said in OpenSSL Library Error when Creating New Certificate:

but I figure that is making things more complex than what I really need.

Yeah it does add a bit of complexity - but again + and - to any sort of setup really. There are things I really like about a virtual router, but me personally prob wouldn't go back to that setup..

In a pinch I could run a virtual router - say my pfsense box went belly up, knock on wood I could always fire up the virtual router until my replacement hardware got here ;)

Maybe you want to fire up a "lab" if you will vm - then if need be a bit of changing some ports around on the switch and bam your in business again ;) That is my DR plan, again knock on wood ;)

@yahav02
your given solution works perfectly on desktop pc and laptop. But I am unable to do this on smart phones (android and iPhone devices), as I am not aware of how to enable ssl inspection for mobile devices. please guide

I won't pretend to be a FreeBSD memory expert. 😉

However if you want that value to include only Free memory you can just edit that file so the line is:

You can include that as an auto-installing patch even if you wanted it to survive updates.

Steve

@manilx For what it's worth: Fixed by reflashing and restoring saved backup.

BTW: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-8200/reinstall-pfsense.html states that

"If there is an existing installation on this device, the Recover config.xml option will attempt to mount the existing installation drive and copy the previous configuration, including SSH keys. Choose that option first, then proceed through the install as usual."

Did not happen, it just installed as factory default. Had to reassign interfaces/IP's to get access to the web console an then restore backup.

After that smooth sailing.

Took me 15min, a lot less time than fiddling around trying to fix/locate the issue.

@jabren said in Synology Package Manager Issue:

so I’ll be adding my previous configurations one by one to see what may have caused it.

Thats a good idea. For each configuration you add back wait a day before adding the next one.

@JonathanLee Hi,
This would probably be as good too. My rule above is Any for all my interfaces. It seems to work as intended, all traffic goes to pfSense as is now. But will remember this to try in case of issues in the future. Thanks :)

@stephenw10 Possible

DPD must be enabled on both ends or it will not be enabled when the tunnel negotiates.

If the DPD response fails the existing SADs are removed and the tunnel attempts to renegotiate.

See: https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/configure-p1.html?highlight=dpd#advanced-options

Steve

Open a feature request: https://redmine.pfsense.org/

I recall some discussion of it in the past.

@stephenw10 thank you for your reply and for the link you provided.

Thank you to all of you, guys, for sharing with me your experience.

Mauro

@stephenw10 Fair enough. Appreciate it man.

@tkronic , it works much better than the old 5268AC. But I am not sure is the pfSense working better or bwg320-500. It is probably the pfSense because I actually never used the bwg320 as the router. I went directly to the pfSense. Here are the basic stat difference that I have measured.
For 5268AC, ping to 8.8.8.8 averages 3ms, pfSense is 2ms.
For 5268AC, rings lose connection usually less then 2 minutes. pfSense still happens but it is far more stable, every couple of days.
Speedtest comparison is not relevant as I upgraded from 500 to 1gb. However, I get 975mb up, and 982mb down.

My pfSense is a white-box: 2.5GbE Firewall Appliance Mini PC, 12th Gen Intel N100(up to 3.4GHz) Fanless Mini Computer Router with 4xIntel I226 Nics 8GB DDR5 Ram 128GB

The only note I will say is that rebooting pfSense does not always survive the public ip binding. Rebooting the ONT, bwg320 and pfsense all together will take a few minutes but it will always come up. My pfsense has been up for 8 days running the acme, arpwatch, notes, ntopng and openvpn. Works well for sure.

@Gertjan @TAC57 @SteveITS There seems to be some good news: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270912

"Jaap Akkerhuis 2023-06-01 12:41:18 UTC
A fix is developed by upstairs. There will be a new release within weeks with this fix. For the inpatients among us, a prerelease is made available https://github.com/NLnetLabs/unbound/issues/887#issuecomment-1570136710."