patchouly wrote:I have set up a server at home for my forum. The router I am running (a Linksys WRT54GL, flashed with DD-WRT) seems to be keeping up with the current demand, but as we grow, I know I'm going to have to upgrade. I don't want to go full out with a Cisco yet, so, do any of you guys have a recommendation about which router out there can handle the traffic from a forum?
My own forum has nearly 3 million posts on it, and it's running off a Linksys router/firewall. You really don't need a fancy Cisco router for that sort of thing. Remember that forums actually don't generate that much network traffic. The data being exchanged is mostly text, not images or videos which suck up huge amounts of bandwidth.
The real problem, as EXreaction pointed out, is from security and possibly your ISP.
1) Your ISP might not allow you to self-host (mine does, but not everyone's ISP does), which means that they might force you to stop doing this or face a loss of service.
2) From a security standpoint, a hardware router/firewall might get the job done but such units have been compromised before (first security tip: don't tell everyone in the world exactly which model you're using). To be safe, you should assume that someone is capable of hijacking your firewall and gaining access to your LAN. This means that you'll want ports closed off on your server, unnecessary services stopped, a firewall in place, decent password security, etc. If you set up your server as if some malicious person may already have access to your LAN
, then the security risk associated with self-hosting through that router is decreased. If, on the other hand, you run an insecure server with all sorts of open ports and public shares and you trust that the router will keep the bad guys away, you might be asking for trouble.
I self-host, but the server is fairly tight. I'm running Linux on it, the firewall only allows a few select services through, there are passwords on every account, the SSH service is restricted to a single IP address (and requires keypair authentication rather than plaintext passwords), etc.