Nevermind, fixed with "System Tunables"

@gwaitsi said in help to recover config.xml:

@JeGr there is no longer docs for filer. links just take you to current netgate package list, which does not include filer.

There may be no current docs to filer, but the package exists, as I have installed it on stable and dev versions without problems.

But just add your complete filepath (File), a description, the default permission (0644 should be fine), and the content of the file. I'd set the execute mode to "do not run" to be on the safe side but it shouldn't do anything if you don't enter a script/command above it.

If a file is configured that way in Filer it gets created and reinstated after a config.xml restore just fine.

Update: I heard back from Netgate, and they suggested I restart the PHP engine from the console and then restart the webConfigurator process. I'd restarted the webConfigurator but never the PHP-FRM, so that seems to have been the issue. Now it's running on 2.4.4 with the restored backup and webCfg working.

So knock on wood I have not had any issues, well one on a old 2440 that had lost power.. But normally all the pfsense I have are on good ups, and normally stable power anyway.

But I have planned on my own 4860 to move to zfs when 2.5 comes out and take the time to upgrade to that.. Just going bring it up on zfs then.

@gklimeck said in PFsense & Unifi USG working togeather:

Ubiquity is making things proprietary and I I am sure anytime now we will see a subscription model soon.

That I don't see. Nope, there are too many thing GPL etc. that can't be just made closed source etc.

But UDMs were a real bummer for me after checking it out. Sure, controller, switch, AP AND USG in one box sound too good to be true anyways but seeing a gateway/firewalling device dumbed down to such levels was really crude. My brother is running one and first thing I did was letting him shop for a Raspi4, throwing Pi-Hole and OVPN on it and have DHCP/DNS running over the Raspi as the Controller UI and USG is THAT bad for simple DNS/DHCP things that are "normal" coming from pfSense.

@PaulRAU said in Upgrade stopped part way through due to network dropout:

SG-3100

I'm almost certain you will need an image from Netgate. You open a ticket and they will provide that very quickly. You will then burn that to a usb stick and install the image over the top of what you have and all should be good.

Repost this in the Netgate hardware sub-forum to get someones attention faster.

@stephenw10

@mmmmmmmm Problem solved. Updated to latest virtualbox version...

@jwj said in 2.5 Release Date vs Abandoned for TNSR Development:

I'll add this: When you come here with some concern or request and you get sorted a simple thank you would be a good thing. These people deserve that!

A little thumbs up (yes, the button, that pun was intended!) and a thank you can go a LONG way to make everyone putting in effort to help, leave with a good feeling and a reason/the will to help again. Couldn't agree more. :)

@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