I'm planning to implement a linux based firewall/router with at least 6 x 1Gb NIC's (network with ~300 computers/server with >=8 VLANs)

Can anybody recommend hardware best practices (reference to discussions/documents?) for such a design?

I have several books about linux firewalls but those are primarily oriented on the iptables++ rules, but there is nothing about hardware recommendations regarding processor choice (number of cores, speed, cache, vendor) RAM, disk/storage performance/configuration and other considerations while choosing NIC's.

  • 2
    Is this a network firewall or/and application firewall?
    – Matrix
    Feb 23, 2013 at 15:10
  • Somewhat off topic but I recommend looking into MikroTik (RB1100 AHx2). Super powerful, super cheap. I don't work for MikroTik - just a very happy user.
    Feb 23, 2013 at 17:36
  • just make sure that the hardware can keep up with the bandwidth you expect to push through it
    – tylerl
    Feb 23, 2013 at 18:13

4 Answers 4


Remember first of all that a failure of your firewall will have an impact on your entire network. From that perspective, you should either purchase extremely reliable server-grade hardware with redundant and hot-swap wear parts — or build a pair of machines, and use a protocol like CARP to control failover between them.

That said, the first critical choice regards network interface cards. Performance varies widely. I have been a fan of the Intel PRO series NIC's for ages. They are expensive, but they perform. Simple choice.

The next choice regards CPU. The number of CPU cycles per packet will depend highly on your firewall rules. If we're talking about the simplest possibility of a dozen rules with some state-keeping, the cheapest Core i5 will probably get the job done. But if you're approaching a hundred rule evaluations per packet, or plan to run proxies, network intrusion detection, heavy logging, or other such things, you will need more CPU power. How much more? The answer is to prototype and benchmark.

  • 1
    Network card is indeed the first critical choice. Pay the extra money and get the Intel cards. Broadcom is terrible in production environments.
    – Ivan
    Oct 21, 2016 at 21:02

A good general sizing guide from PfSense although your mileage may vary depending on what firewall distribution/software you end up using.

 Throughput: Mbps   Hardware requirements   
    1-10 Mbps           No less than 500 MHz CPU Single Core    
    1-40 Mbps           No less than 1000 MHz CPU Single Core   
    1-100 Mbps          No less than 1000 MHz CPU Single Core   
    1-350 Mbps          No less than 2.4 GHz CPU Dual/Quad Core 
    50-650 Mbps         No less than 2.4 GHz CPU Dual/Octa Core
    750 + Mbps          No less than 3.5 GHz Quad/Octa Core.    
    Until 10 Gbps       No less than 3.5 GHz Quad/Octa Core.

For a network firewall, any new Intel dual-core hardware (Core i3) will do, even at 6x 1 Gbit/s. For an application firewall, I'd recommend a quad core (Core i5). 4 GB RAM will be enough for both uses. Disk storage doesn't matter, but you need at least 5 GB. For network cards I'd recommend Intel or Broadcom NIC that support interrupt coalescence on Linux. I don't recommend buying from a HW vendor like IBM, HP, Dell as you will overpay. Just buy the components and assemble it yourself if the shop won't assemble it for you.

  • Second for the Intel NIC recommendation.
    – ruief
    Feb 24, 2013 at 20:52

About ram, You can look here How much memory is consumed by the Linux kernel per TCP/IP network connection? And ram is cheap. I agree with Matrix, that i3 cpu will enough. NIC cards need server type. You can google difference between desktop ones.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .