@all There's no need for a compat list for PCengines boards, as both ALIX and APU1 are "dead" (out of production and support) and you don't get them anymore besides very very old stock lying around in some dusty little shop. Only APU2-4 (that are essentially the same SOC-wise) are current and actively sold and supported by PCengines. And as APU2 is a 64bit APU it runs the latest version of pfSense without problems.

Also if you still want to shop age-old hardware (why?!) be aware, that there's no hardware anymore for replacement or repairs as the SOCs they used (APU1, Alix) aren't built anymore. That's also why APU1 had such a short lifetime (besides other shortcomings and stability issues) as replacement parts for the SOC weren't available anymore. So just do yourself a favor and leave old hardware alone ;)

Open a ticket with the Netgate support (free & fast) here: https://go.netgate.com to get the SG-1100 factory Image and reinstall:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

-Rico

@no1scary said in IP issue after initial setup:

I believe the issue was switch related.

I just want to note that TP-Link is not usually a VLAN guru.
I don’t like to see it in our systems....
The Cisco SG300 / 350 series is affordable and usable in SOHO

Hi all,
I've run into this problem as well and appreciate the suggested fixes. The fixes suggested, by themselves, however did not fix my package hang problem. I was, however, able to find additional information, when augmented to these fixes, solved the hang problem in package manager. The root of the problem for me was that everytime I restored a backup configuration, the package manager would hang when trying to reinstall or update packages. The cause of the problem was due to a known problem with the squid package. Unless the squid service is stopped (disabled) prior to a package reinstall, the package manager will hang on a squid reinstall. My guess is that squid may not be the only package service where this may happen. To fix the problem, I performed the following steps:

Stop (disable) all package services to be reinstalled or updated. Open command prompt from the Diagnostics Menu item. Execute the following command to see which process has the database locked:
“ fstat /var/db/pkg/local.sqlite ” Confirm process is locking database by executing the following command:
“ procstat -c (process number) ” Look for partial listing (e.g., child processes) by executing the following command:
“ pstree (disply if any partial listing) ” Kill processes, starting with child processes, by executing the following command:
“ kill (process number) ”. Repeat steps 1 through 5 until until there are no longer any processes locking the database. Ensure that the package database directory exists by executing the following command:
“ /bin/mkdir -p /var/db/pkg/ /root/var/db/pkg/ ” Force an update of the package repository data by executing the following command:
“ /usr/local/sbin/pkg-static update -f ” Force a reinstall of the pfSense® base package and kernel by executing the following command:
“ /usr/local/sbin/pkg-static install -yf pkg pfSense pfSense-kernel-pfSense ” Refresh the php.ini and other files to ensure they are loading the correct modules by executing the following command:
“ /etc/rc.php_ini_setup ” If any additional packages were installed, reinstall them manually using the GUI if possible, or by using pkg-static install from the command line using the following command:
“ /usr/local/sbin/pkg-static install -yf <additional-package> <another-additional-package> ”

I was using the keyboard I plugged into it..which allowed CTL-ALT-DEL but actually using the keyboard on the computer I am using the terminal worked.

@rustydreamcast said in Box recommendation needed:

Would these generic J1900 boxes on AliExpress be up to the job ?

In a not so near future the J1900 would prob. not be supported by pfSense , due to the missing AES-NI instructions.

Pick a (64bit) CPU that supports AES-NI

/Bingo

@Gertjan

This was a purely academic excercise (for now).

What i would like to see is a "Tick box" on the "Restore" page , that says : Strip (exclude install of) packages, from the restored config.

Not the package config , just the physical package entry in the xml.

That would IMHO solve a lot of trouble, and especially now. Since Netgate already have given the possibility to to use the previous repos (2.4.4 Deprecated).

But you are right , as I'm getting the hang of the xml file , i could just strip the physical package section my self.

But a tickbox would be much more elegant.

/Bingo

I just had this happen again and re-found this thread and realized I never posted the solution. Ctrl-Shift-F5 fixed it for me this time. I think last time the SVG was 0K for whatever reason and I just copied it from another working one. In case anyone else comes across this.

Has anybody gotten node exporter to work on 2.4.5 and have steps? Would love to scrape pfsense with prometheus. Thx!

https://forum.netgate.com/topic/154403/squidguard-update-fails-after-upgrading-pfsense-2-4-5-release-p1/52

hope it gets fixed in the next update

@Rico yep thanks 4 update...

Yes, you can do that. The official Netgate/pfSense documentation for the import and installation of an existing configuration into a fresh install of pfSense is here: https://docs.netgate.com/pfsense/en/latest/backup/automatically-restore-during-install.html.

Thank YOU !

Shrug, it seems to be working...

Ok. All of this time I've been trying to configure the virtualbox network options.
I ve been trying to connect pfsense from my Wireless on my ubuntu.
Trying 192.168.1.1 ... 10.0.2.0 ... everything.

the virtualbox net: 10.0.2.0
host machine: 192.168.1.1 DHCP: 192.168.1.100
sub adress: 192.169.1.101 top: 254

I've tried:
First Nat Network and second Only Host
First Bridge Network and second Bridge Network
First Bridge Second Inline inbound .. or whatever

What can i do. Is there any method except usb boot? in linux?

I can confirmed this also happens with FreeNAS USB installers.

@NogBadTheBad said in admin login with ssh fails in restored configuration:

Try removing your ssh known hosts file on the device you are running ssh from, the ssh key has changed.
[...]

I do get prompted for password, and then you can see the "Authentication error" in the log file - so this past the ssh fingerprint detection.

@jlh said in Install freezes with USB on 3I525D:

@fireodo no problem.

I got it running by installing on the notebook and putting the ssd back into the LEX (64Bit:-). As a windows user I didn’t know this was possible. But still I’d like to know why the LEX freezes.

Perhaps some BIOS settings concerning the USB Ports where you plug in the stick ... just guessing.