-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 shane wrote: > We were considering building a box... however, spikes in usage (like > sheduled Windows <shudder> Updates) seem to swamp our current router. >
Are you *sure* this is the problem? If so how do you know? Windows update can be cached in a proxy, so again a proxy may be the better solution. A proxy does not need to reside on the firewall/border device. > I thought having having some more RAM would prevent the dying at high demand > times. > > I'm looking at something like: > http://www.cisco.com/en/US/products/hw/routers/ps380/products_data_sheet0900a > ecd8028a976.html > Unless you need the features of this router, I do not see the need. My experience is that a proxy goes a lot further than a higher priced router. Preventing direct access to the internet is usually a good idea (actually a default deny on outbound connections is a better idea). I have also found that "power users" who rdesktop to their home machines place considerable demands on the internet connection. Since most of my clients have mail servers on site (either exchange, SBS, or a linux solution), none of their workstations actually needs to connect to the internet directly. They send email through the local mail server, and connect to the web via a proxy. With the proxy filtering out a bunch of MIME types, we can have an office of ~120 users connected to a single business DSL line. I am beginning to like to IPCop to replace solutions such as the cisco product you linked to. The thing I like best is that at a glance I can see network utilization, as well as what connections are active. There are also no restrictions on the number of VPN connections, no arbitrary limitations on connections/users (ie. no licenses or CALs needed). > S. > > On Tue, 04 Apr 2006 10:02:39 -0600, Gustin Johnson wrote > I use either IP Cop or a homebrew Debian install for firewall/routing > duties. I doubt that the router is the issue, but bandwidth utilization > likely is. I am a fan of squid (well proxies in general), as they > can cut bandwidth utilization as well as filter certain MIME types, > so that streaming media does not bring your internet connection to > its knees. > > For most of my clients, streaming music and sites like google video, > youtube, tsn, cnn, cbc, bbc, basically anything with audio or video > (there are a ton). > > Do you have any method of monitoring your current solution (SNMP for > example)? > > Why the RAM requirement? You should not need that kind of RAM for an > appliance. > > shane wrote: >>>> Hi All, >>>> >>>> I wonder what the group would suggest for a router that meets the >> following >>>> specs: >>>> >>>> --up to 20 ethernet clients >>>> --port forwarding >>>> --NAT >>>> --Firewall >>>> --Easy configuration/use, http control panel >>>> -- VPN, QOS, Traffic Shaping, etc not required >>>> --128 MB ram + >>>> >>>> My current router seems to get swamped at certain times of day. >>>> >>>> Thoughts? >>>> >>>> Shane >>>> >>>> >>>> _______________________________________________ >>>> clug-talk mailing list >>>> [email protected] >>>> http://clug.ca/mailman/listinfo/clug-talk_clug.ca >>>> Mailing List Guidelines (http://clug.ca/ml_guidelines.php) >>>> **Please remove these lines when replying >> _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEMq0swRXgH3rKGfMRAgxxAKCdi00vXg6iKFW48jPFyPZaAnAcSwCfRbvT AxmM9pFPfg2YZ+8fh4VIEcA= =aKql -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
