You&#x27;re really going to have a hard time finding something that satisfies your 3 requirements (open source, high-speed and capable of what a Juniper Netscreen can do). OpenBSD can be tuned to operate really well, hit maybe 80 or 90% feature parity with those Netscreens, but the performance won&#x27;t even come close to what a Netscreen can do -- Juniper fabs their own ASICs and a general von Neumann x86 won&#x27;t come close to being able to packet switching at those speeds.<p>You might be able to get close in performance with your high-end Altera&#x27;s and Xilinx&#x27;s gear, but that certainly won&#x27;t be cheap and AFAIK the FPGA synthesis tools are still closed source -- so you&#x27;re not going to get an &#x27;open source&#x27; from top-to-bottom solution at all 3 levels (Silicon, firmware, OS and packet switching). It&#x27;s arguably more trust-worthy than buying Juniper&#x2F;Cisco which has complete control of the stack, from silicon to software, but you&#x27;ll be paying through the nose either way.<p>The standard Intel e1000&#x27;s running OpenBSD and libpacket might be the best trade-off you&#x27;re going to get in price&#x2F;performance (again, if you make the concession that Intel isn&#x27;t backdooring on: a) the firmware and&#x2F;or drivers for the e1000s, or b) somewhere along the controller bus path -&gt; PHY on the processor). This whitepaper [1] re: OmniPath + Xeon&#x2F;PHI architecture boasts brilliant numbers (page 7 for an architecture summary, column 2 for the network switching summary, page 8 for the benchmark numbers). Again, not open-source at the hardware level, but the drivers, libraries and OS can all be audited. And at those rates of transmission, I&#x27;m guessing you could use physical probing along each component to see if any deep-packet tomfoolery is occurring, as the latency increase would be detectable, and you can&#x27;t just add an extra login password at that level.<p>Tyan&#x27;s OpenPOWER compliant stack will run on BSD and other than the processor (which uses an IBM POWER8) pretty much uses jellybean components-- so you get what I&#x27;m going to coin as &quot;security through vendor diversity&quot; from now.[2]<p>It comes down to how tightly your tin-foil hat has been sized I suppose. The upside is right now there&#x27;s a huge open-source hardware revolution going on. OpenCores&#x27; Virtex based RISC stuff is available and that&#x27;s top-to-bottom open source, and if you were really motivated and had the engineering know-how, ASIC runs can be done for under a million.<p>[1] <a href="https:&#x2F;&#x2F;ramcloud.atlassian.net&#x2F;wiki&#x2F;download&#x2F;attachments&#x2F;22478857&#x2F;20150902-IntelOmniPath-WhitePaper_2015-08-26-Intel-OPA-FINAL.pdf?version=1&amp;modificationDate=1441327130864&amp;api=v2" rel="nofollow">https:&#x2F;&#x2F;ramcloud.atlassian.net&#x2F;wiki&#x2F;download&#x2F;attachments&#x2F;224...</a><p>[2] <a href="http:&#x2F;&#x2F;www.tyan.com&#x2F;campaign&#x2F;openpower&#x2F;index.html" rel="nofollow">http:&#x2F;&#x2F;www.tyan.com&#x2F;campaign&#x2F;openpower&#x2F;index.html</a>