Date: Wed, 17 Mar 2010 10:12:39 +0100 From: Gilles WAGNER <gillesw@gmail.com> To: freebsd-net@freebsd.org Subject: Fwd: Choosing CPU for router Message-ID: <a952d5981003170212t1fe7b917x786c4d96cc1b1dad@mail.gmail.com> In-Reply-To: <a952d5981003170207m1b8309cdn9e442bfa9521c51b@mail.gmail.com> References: <C7C53AE3.2441C%jon.otterholm@ide.resurscentrum.se> <585602e11003160552v483ea17bh4ca3f4228c3f3723@mail.gmail.com> <4BA02D0F.9060807@modulus.org> <a952d5981003170207m1b8309cdn9e442bfa9521c51b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/3/17 Andrew Snow <andrew@modulus.org> Matthias Gamsjager wrote: > >> Way over the top for simple fw and dhcpd. but how much traffic will >> be involved? >> Investing in a good nics will return more then a pricey cpu and >> motherboard (eec mem is good idea for 24/7 tho). >> > > > Agreed. > > The Supermicro Atom miniserver is more than enough CPU grunt for this sort > of routing/ipfw task. The main reason to go Xeon is if you need ECC RAM, > and even then you can get away with just using the cheapest CPU available. > > > - Andrew > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > Hi, That's what I would choose : 2 or more atom miniserver and pfsync. But I don't know how well it can work with ipfw. Gilles
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a952d5981003170212t1fe7b917x786c4d96cc1b1dad>