• 2 Posts
  • 8 Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle
  • You could get similar (and in some ways faster as routing is better with fast single cores) performance with an X10SLL-F, Xeon E3-1271V3, 16GB of RAM and an Intel X520 10G NIC.

    Power draw will be higher with a maximum around 110 watts vs 55 for the DEC 850 v2 but that is only under full load, the real world load will be around 45 watts vs 30 watts.

    You can easily increase the ram in the Supermicro motherboard, as well as put in multiple 10G NIC’s or even faster. Throw a couple mirrored SSD’s (the Intel D3-S4510’s are amazing) and drop it into a case with a psu and you can be up and running for around 300 to 400 through eBay, the mobo and cpu is running 80 bucks together.

    NVME drive in a router isn’t worth much, outside of boot time and logs it just sits there. Even a HDD is fine for that, a SATA SSD will boot in about 30 seconds after POST. I’m using the X10SLL-F with an E3-1226 v3, 16GB of RAM, and a pair of D3-S4510’s that are underprovioned. I do not have native IPv6 and use a Wireguard tunnel to Route64, multiple vLAN’s, run CrowdSec with Intrusion Detection and UnboundDNS beyond the base system on a 1Gbps fiber connection WAN with 10Gbps fiber backbone LAN.

    OpnSense is truthfully meant to be managed through the GUI or the API. If you want to control through a CLI you may find building a system on FreeBSD with packages is better. The tools used are mostly things in the FreeBSD pkg system and can be recreated, the OpnSense setup is mainly a GUI, an API, and some middleware that makes everything work. I’ve been using OpnSense since 15.7, I tried multiple others before then including running Openwrt on a WRT54G IMHO the DEC850 is way overpriced so unless you are running this for a business you will probably be better suited with some used server hardware






  • No problem.

    Be sure to set a cron job for updating the DNS Blocklists, running scrubs, smart tests, and trim if you are using a ssd.

    I am working on a way to do snapshots for the system as well for super simple restores that are automatically created. Before an update you WILL want to have a snapshot available. Once snapshots are automated I will probably start doing automatic updates. It basically creates a system similar to how an immutable OS works, if something goofs you can simply roll back to a previous working state and pause updates. I previously had a script I setup via a cron job but the system removed the job during an update.