How hot exactly is the CPU running? There's quite an extensive thread about these boxes though. IIRC some users swapped the BIOS for something with more options available.

@m782 I actually "interviewed" someone on Reddit on a similar topic; they have installed OPNsense on ASA 5525-X and 5515-X. Here's what they told me: https://www.reddit.com/r/opnsense/comments/147ot7f/comment/jnycohl/ I hope this is close enough to what you have on hand...

@NC1 No problem with the DIY and I do like the ability to upgrade if needed. Thanks for the info!

@interrupt said in Running pfSense on a meraki MX400: i have lcdproc configured and its fully functional. i will post a pic later. Thank you in advance for that! Looking forward to it. If possible, could you also post a brief hardware overview (I can see from the screenshot that the processor is Xeon E3-1275 v2, but there no information about stock memory and storage) and Lanner motherboard model number?

@vicking my guess: it should work if no IDS/IPS or traffic limiter are used. For comparison user vicking was able to get 500/500 on a PC Engine APU6 with PPPoE and the new if_pppoe driver (not sure how much with the old one). The APU6 has a CPU benchmark of 650 (single core 250), the E3940 got 1908 (single core 675) cpu benchmark AMD GX-412 vs Intel E3940.

@NC1 yea i did try using that command but it didn't help unfortunately. Sophos wouldn't give me the updated bios file, which is what is needed to be able to activate a hidden menu which has the 60/40 option hidden behind. I just ended up ripping the SSD out and put a different one i. And that solved my issue.

Bug for the rogue gui element: https://redmine.pfsense.org/issues/16451

Hello, Not exactly the same card, but some information for you. I have the following on a pfSense 2.7.2 install: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller The interfaces are the 'onboard' interfaces in a Dell R440 server. I'll admit that the latest firmware is likely not installed on the server, so this might only be a me problem? I have found that playing with SFP modules (i.e. remove / insert) while the system is running can cause the NIC to stop transmitting / receiving traffic. The only work around I have found is to reboot the node. Mike

@Pizzamaka Thanks for this information. Apparently, some of these files can become corrupt if the system loses power. While the appliance may still operate properly, these warnings every few seconds are annoying. So....rm -rf /var/db/rrd/* clears the corrupted files and life goes on. Thanks from a newb PFsense guy.

The ice(4) driver is in kernel already in 2.8.X.

@Gradius said in Unable to use BCM57810 properly, need new drivers: https://redmine.pfsense.org/issues/16321 Mmm, that's the same patch that's in 2.8.1 though.

Thank you, Eloich for the link. I managed to upgrade the BIOS and install pfSense in 620. Logging in every now and then, to check my new setup

The X520 does indeed connect at 1G or 10G only. Can we assume you need 2.5G?

@Conjurer No worries, thank you for the reply. I was hoping you did the HWP on modification on your own and could help me achive it for my 13th ge. system since the bios from this forum will brick my machine.

I have a SG210 and I upgraded the cpu to Xeon E3-1225v3, and 16Gb of RAM. Then I install proxmox and allocated 4Gb of RAM to a VM for pfsense, with dedicated network ports and even the serial port to the LCDproc. It is happily running for the last 12 months. I have other stuff running such as Unifi controller, pi-hole and ngnix as LCX and it worked fine. Pfsense is very efficient and it allows the SG/XG to run a lot more stuff. [image: 1755451032670-screenshot-2025-08-17-101540.jpg]

Is it actually losing link? What do you see logged when that happens?

@dugeem It would be interesting to see how much PPPoE performance has improved with the new if_pppoe driver included in 2.8 CE and Plus 25.07. Previously with Netgraph/mpd5 it was limited to ~ 400 Mbps on the APU2.

Given that it's already in Intel's branch I'd expect it relatively soon. It's not like igc for example where there was no driver. There is work on going to include it and it looks like it's imminent: https://reviews.freebsd.org/D50067