If you can find one that uses a supported driver (I don't think there are any at the moment), then it would almost certainly not reach anywhere near line rate. How close you get depends entirely on the hardware, though. What is your use case? Almost certainly you'd be better off with something geared more toward high performance at that level, like TNSR.

Mmm, well probably have to wait for someone who's actually tried that or find a thread discussing it. Probably is about as far as I can say there. Steve

I'll second @provels suggestion - I think the i340-T4 provides great bang for the buck. I bought two of these on Amazon (at different times) over the last year and both have worked great (in fact one of them is currently being used in a pfSense box). https://www.amazon.com/Intel-Ethernet-Adapter-I340-T4-packaging/dp/B003A7LKOU/ If it were me, given the price here and looking at the seller reputation, I'd probably roll the dice on this. But the choice is ultimately is yours. I do recall that one of the i340 I received was actually an OEM IBM version, but again, it has worked just fine. If you are set on 10Gbit NIC's, I'd also take a look at Chelsio cards which are very well supported in pfSense/FreeBSD. One can find good deals on the T520. I've used both the T520-SO-CR and T540-SO-CR with pfSense without any troubles. Hope this helps.

First check the BIOS can see any temperature values. Usually they will display at least CPU temp, often some other thermal zones where sensors exist. If those are all enabled they are usually passed to the OS via ACPI but it maybe another crappy BIOS that has DSDT values tested, and marked as, Windows only. In which case just make sure you're on the latest BIOS. Fixing that is almost certainly more effort that it's worth. The last time this came up: https://forum.netgate.com/topic/137205/temperature-readings This is also Zen micro-architecture CPU so the same applies. It may require amdsmn which only appeared in FreeBSD 12. Steve Steve

@oldfart I would contact our sales team so they could discuss the best possible hardware for your scenario: Phone: +1 (512) 646-4100 Email: sales@netgate.com

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