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>

I reinstalled pfSense on my apu2d4 to get ZFS and it went without pretty smooth (me not being seasoned messed about a bit, as expected). When the installer asks about pratitioning, 'Auto (ZFS)' is an option. I found this walk-through's screenshots somewhat useful: https://www.ceos3c.com/2017/09/15/pfsense-2-4-installation-step-step-overview/

Good luck!

Hi all

Thanks for all the reply,

I see its not just me who is having issue i see booting from USB, I will give 2.0 a try and Rufus, al keep you posted

the bios is on a 15 to 17 year board it has the AMD FX 64 in it, i love this old style bios brings back so many memories

Happy Nassing/Pf sensing and all that good stuff :)

Devlopment 2.3.5.a to 2.4 stable version ?

Are both 64Bit? Or is one 32Bit? Then you may have to install fresh and full.

I have 2 pfsence running development version and i want to upgrade them into 2.4.X stable version.

You may be able to do a backup and configuration backup too and then please do a fresh install and play back that
config backup, it is done with a mSATA in ca. 5 minutes!

When i choose stable version in System/Update System/Update there is no 2.4.X update.

Then it is perhaps not able to realize.

Is it possible to do this ?

Perhaps someone from the staff should be answering this question right.

I decided to reinstall 2.3.4 on the SSD and then load my last 2.3.4 config on it.  Rebooting after config uploaded it seem to hang at the same spot
Trying to mount root from ufs:/dev/ufsid/a33d3ef3…... [rw]….
After leaving that message alone for ~5 minutes it booted up in 2.3.4 with my config functioning.  I upgraded the install to 2.4.0 and got an failed upgrade in the GUI.  The pfsense router rebooted and 2.4.0 was present and functioning.

My best guess is I need to wait longer after the Trying to mount ...... msg appeared.  I thought it was hanging.  Maybe original fresh install of 2.4.0 would have worked if I just waited but it seemed to be stuck at that msg forever <g>.  Thanks to both of you for responding.</g>

Ok, I'm sure it'll be fast enough.

Thanks for the help!.

worked! Thx a lot!