We fixed it.

I have 1 with a 32 bit install and that is exactly how it looks…

Perhaps you don't have interfaces available to add? Configure a vlan, or a openvpn server, and check the page again?

Yeah!  Recovered!    Thank you kindly.  I was banging my head against the wall because dropping into Single User mode mounts read-only, and even trying to run the /etc/rc.remount_rw script was failing.      Didn't realize I could cut out the boot process at any time using Ctrl-C. I'm back in business.

Current snapshots are OK here. Looks like somehow you are missing the pfSense PHP module, or it has failed to load.

Hello to all. I revert to this older post of mine, for an unclosed issue. Today, after a long bike trip in Corsica, I performed the update of my SG-1000 to 2.4.0 It worked. Before and after, I saved the entire configuration (not skipping packages nor RRD data). In System>Advanced>Firewall & NAT, Firewall Optimization Options is still on "Normal". From my earlier update to 2.4.0beta, I had received the following remark: (Filter Reload: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [19]: table <bogonsv6> persist file "/etc/bogonsv6" @ 2017-10-23 15:49:41) Can I now safely erase that remark and forget about it ? TIA.

try bouncing the LAN interface from the console (ifconfig if down; ifconfig if up) and then restarting php-fpm if you get a 502 error

OK, this issue is solved.  I looked further at the error, and needed to apply further debugging techniques. If disabling sdp would not work, go further back. So I disabled the FireWire driver adding this line to /boot/device.hints hint.fwohci.0.disabled="1" Rebooted and firewall came up fine with 2.4.0 kernel just fine.

Appears issue has been resolved in the RC for 2.4.1 so far if anyone runs into this.

I updated from the last version.. 2.3.x … okay, yes this is the reason, I use old keys.. thanks!

The only common filesystem between Linux and FreeBSD that might work realistically is ZFS but ZFS multi-OS multiboot is not for the faint of heart.

A bit of history:  Back in 1980 the IBM PC came with MSDOS on 160K floppies.  No room for TZ files.  So MSDOS set its time directly from the CMOS clock.  So generally you'd set that to local or "wall clock" time.  When folks started porting the UTC based *nix to the PC, provision was made to deal will wall clock CMOS time so as to be able to dual boot nicely.  For FreeBSD, the presence or absence of /etc/wall_cmos_clock was used to tell the kernel if the CMOS time was local or UTC.  See FreeBSD's adjkerntz(8).  Can't tell you how Linux does it, but presumably it has it's own method to coexist with DOS. Checking  my pFsense install ( fresh 2.3.x on an APU2) I don't see /etc/wall_cmos_clock, so presumably the pFsense default is to have the CMOS set to UTC.  But perhaps the OP put pFsense originally on a box with local time in cmos and does have that file. Now I haven't yet migrated my servers from FreeBSD 10 to 11, so don't know if FreeBSD made changes to the process.  But possibly it has changed and pFsense 2.4 picked that up, and maybe that config is confusing the NTP Widget.  Although why the NTP widget is looking at anything other than a NTP query and displaying UTC (NTP doesn't deal with local times at all) is beyond me.  But given OP's NTP peer status his system is probably running time correctly.  It would be worth looking at the system log after a boot to see if the "ntpdate" was jumping the time by 4 hours (assuming pFsense overrides the limiter).  That would be a good indication of confusion between what the kernel thinks is in the CMOS and what actually is.

Thats awsome…  Working very well now.  Now I just have to get used to looking for a blue internet tab instead of a red one...

Thanks!

Thanks for the help. Couple of thoughts,  trying to be helpful:- If this is a new feature should it be added to the Features Notes?    Should any "call out"  perhaps leave a note in the log file? Thanks again, J

Question already asked and known since 2.4.0 went into pre production (when it was beta). Answer : No, you can't. And Yes, if you can do it. You have to sift out a bunch of style sheet files and html - maybe even some PHP - but you can make what ever you want it to look like. Because it's hard coded. Be ware : the next upgrade might remove all your edits. Btw : When set up correctly, you'll never (or close) see this login page again …. And only the admin uses ans sees it. Btw : maybe the login screen will be included into theme settings in the future. Btw : I'm not running 2.4.0 live right know, hope to do so this weekend (I ran out of USB sticks).

Hey Gektor, I finally got a chance to try this again in my lab environment. I can confirm that pfSense 2.4 release properly detects and can use the passed-through NIC for me. However, I will note that things are a little wonky, I suspect the pass-through is confusing the Broadcom driver, as it doesn't put the interfaces up on boot. (However, manually putting them up and running dhclient worked for me.) I did not test very extensively, so I imagine they won't come up when booting after install either (I did my testing from the recovery shell.) Looking at your screenshot, it looks like you're having some similar driver problems (which is different from my original issue.) Your Intel NIC is seen by pfSense, but it fails to initialize properly. Do they appear in your ifconfig output? If so, you might manually putting them up manually (ifconfig <device-name>up) and configure them (dhclient <device-name>) to see if they work. However, based on the fact that it kept using en0 for each port, I suspect they won't appear. My gut says that the PCIe passthrough is confusing the Intel driver. Hopefully it is something the FreeBSD developers are aware of and it will be fixed in FreeBSD 11.2. I don't have enough time to investigate my specific issue further. Since you have an error in your logs, you might be able to find out more about the root cause of yours. (EDIT: Removed brain fart involving FreeBSD versions.)</device-name></device-name>