Yup NMI is almost 100% a hardware fault. In the 0.1% cases where is seems to be OK with other OSes it's something specific that FreeBSD is hitting and there's nothing you can do about it anyway. So swap it out. Steve

No

@suplantor Just making assumptions but... Shouldn't the Silicom drivers work? Not sure which model you have, but start with the link below and drill down to your card. Drivers available for multiple OSs including FreeBSD. https://www.silicom-usa.com/cats/server-adapters/networking-bypass-adapters/

@stephenw10 Thanks :) Work now

@stephenw10 Thanks Steve, yep the VLAN biz will all be handled at the switch, the pfSense facing port is a trunk and from there just as you cautioned, each port will need be placed in an access mode for the proper VLAN it needs to join, that's a manual task and care will be the key playbook! Thank you ~B

Go Ryzen 3200g, gigabyte b450 ds3h, 16gb ddr4, 128-256gb ssd, dual intel lan. Works like a champ for me

Short answer: you can't. To do so would require compiling from source and creating all the required components for that specific board. ARM is not like x86, there isn't a generic installer for all ARM devices. Steve

@aasimenator a Six core Xeon wouldn't be able to handle 10GbE? higher cpu frequency would be better also a 6 year old cpu is far less performant then a recent one ... i would even dare to say that a current-gen i3 cpu would perform better with pfsense than that xeon you are using

Go to Diag > Command Prompt and execute mount -p. You should see something like: /dev/diskid/DISK-9E18E959s2a / ufs rw,noatime 1 1 devfs /dev devfs rw 0 0 /dev/diskid/DISK-9E18E959s1 /boot/u-boot msdosfs rw,noatime 0 0 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 devfs /var/dhcpd/dev devfs rw 0 0 You can see on that SG-3100 the root filesystem / is mounted 'noatime'. If yours is not go to Diag > Edit File an open /etc/fstab. Edit the / line to include noatime. So it would probably just be rw. Change it to rw,noatime. Note that breaking the fstab with a typo will probably make the system unbootable until it's corrected so.... Reboot to apply that change. Run mount -p again to be sure. @Gertjan said in pfSense custom build hardware with Realtek port dilemma: edit : wtf : @stephenw10 : more then 18 K posts ... Yeah it's a problem. I'm trying to cut down! Steve

Steve, thanks a lot for your elaborated answer. Actually I'm running Intel's NIC on LAN side and now I know I made the right choice.

Can you spoof the MAC addresses back to their original values? All 6 interfaces are shown? bce0-5? Steve

Probably not. Fortigate used special purpose chips (usually ASICs) in their devices to get the throughput they need and those are not accessible without their code. The 90D appears no different: Combines a RISC-based CPU with Fortinet’s proprietary SPU content and network processors for unmatched performance So you might get the management plane running pfSense if that part is x86 but you won't get any of switch ports available and performance will be..... limited! Or it may just not be possible at all. Steve

How does it fail when you try to use it? Does the card work in the Optiplex if you boot some other OS? Steve

If you are looking to have a go at compiling pfSense, or anything, you would not likely be using the same hardware. pfSense requires relatively low powered hardware to run but you probably want something much more powerful to compile on unless you don't mind waiting. Also pfSense itself does not contain any compile tools so compiling and running on the same hardware would require some sort of dual boot setup with FreeBSD. Steve

Hmm, curious. I'm not aware of any hardware that won't run 2.5.... yet. Do you have the backtrace or console output leading up to the panic?

No, there is a huge difference between those drivers. I doubt it could ever run on 2.4.X Steve

I seem to be having some instability issues with my APU2C. It was running OK for over a week. This morning the orange lights on each NIC were not flashing and all connected clients were receiving a self-assigned IP address. The only way to resolve this was to reboot I had a look through the logs but couldn't find anything. My grafana dashboard shows that something odd started to occur around midnight: [image: 1573587644386-screen-shot-2019-11-13-at-06.39.40-resized.png] CPU temperature on average is about 53 degrees Celsius and it is running the latest BIOS v4.10.0.2||spoiler||

Just want to let you guys know: I have the Qotom Q575G6 with Multi WAN Gigabit and Suricata running. IPsec VPN brings the CPU up to 40% usage. I'm really happy with this device. It's running flawless and very fast.

ZFS seems the most vigorous FS available in pfS, that's why I moved over from UFS to ZFS. The (re)install is a breeze, with a current config file at hand. My APU2C4 has ECC and to me this and the ZFS FS seems max what I can do against sudden power surges, that being said, I would always use the "halt" command before I pull the power cord ;) @bouke Kudos for pointing out the flaky mSATA issue link, didn't knew that.