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!

Thank you, I will keep an eye on it and gather the necessary info if it happens again.  As of right now, I have not had a problem since yesterday around noon, but will monitor the situation. As a side note, when my Web GUI freezes in my situation, I don't get a "502 Bad Gateway" error, the web page doesn't load and the cursor just keeps spinning.  That doesn't mean it's not the same issue though. Thanks again, jimp.

I would be very glad to learn how you have successfuly configured transparent HTTP (S) proxy along with AD (which I translate as "authentication")

It is not a bug. Host addresses that are defined as a monitor IP address have a specific host route out the interface they are defined on. Same thing with DNS servers in System > General if you define a gateway there. This is necessary for Multi-WAN, which is a feature people seem to like.

Hi, I have the same issue. Frustrating: at the end of the upgrade process it sais "You can find instructions on how to convert it" but not where  :-[ I'm going to give these instructions a go and let you know if it worked: https://doc.pfsense.org/index.php/Upgrading_64-bit_NanoBSD_2.3_to_2.4

@CubedRoot: jimp, I have attached the text files in this reply. I have not yet reinstalled, as I am right now booting the unit to the kernel.old to get it running. Exactly the same problem (failed with same error after upgrade, works with kernel.old) Motherboard : ASRock D1800M (Celeron Processor J1800) NIC (not working after upgrade and new kernel)  : Intel EXPI9301CTBLK (PCIe), SYBA SY-PEX24028 Dual Port (PCIe, Realtek Chipset 8111E) NIC (working after upgrade and new kernel) : Realtek RTL8111GR (integrated)

Problem solved with your sugestion ;)

Thank you - should have looked more thoroughly thru the forum.

After activating ipv6 on one more interface and touching WAN config the NAT error is gone. Even after reverting the changes. I think pfsense should boot twice after upgrading.

Since this from May I doubt he is still working on this problem ;)