[olug] Community Colo Project

[Phil Brutsche]

IMO QoS is a no-brainer. It is trivial to set of WFQ (weighted fair
queueing) which is a must-have if for no other reason than to keep one
host from hogging all the bandwidth, in either direction.

It is also trivial to tell the router to prioritize interactive SSH
traffic vs non-interactive SSH traffic (think sftp or scp): I know that
OpenSSH properly set the TCP ToS bits for low-latency vs bulk traffic.
Putty might as well, I would need to check.

Another useful feature: a traffic shaper to limit our bandwidth to no
more than 25Mbps on a 20Mbps commit, or no more than 15Mbps on a 10Mbps
commitment, or whatever we want to do.

If whatever router we use doesn't support proper QoS I would say we made
a poor choice in router.

Ryan Stille wrote:
> I assume you'll want some kind of bandwidth shaper on there, so no one's 
> site gets killed when someone else is doing remote backups or 
> whatever?   And having the ability to prioritize traffic would be 
> important, too.  That way you can still get on and get a shell no matter 
> whats going on with bandwidth.
> 
> I believe pfSense can do all this.  MRTG can be used to track how much 
> bandwidth everyone uses, not necessarily for billing but to see if 
> someone is consistently using more traffic than everyone else.
> 
> Without having well defined bandwidth rules up front, I could see a lot 
> of people getting unhappy quickly.

-- 

Phil Brutsche
phil at brutsche.us