Seconded. If I were you rather look at the services you need to offer using your connection and bandwidth manage according to that. If VOIP is important etc. Also look at blocking adverts, windows updates.
Maybe give pfSense a try? Simon Vass Technical Manager E-Tech Uganda Ltd http://www.etech.ug Tel: +256 (0) 312260620 or (0) 312260621 email: [email protected] skype: e-techservicedesk ----- Original Message ----- From: "Kyle Spencer" <[email protected]> To: "Linux Users Group Uganda" <[email protected]>, "Paul Bagyenda" <[email protected]> Sent: Tuesday, May 25, 2010 6:05:21 PM GMT +03:00 Iraq Subject: Re: [LUG] Squid Completely agree w/ Paul. Put your bosses in the "user" pool and let them swim in the same water as everyone else. ----- Original message ----- > Stephen, > > Might I suggest that generally it is not a good idea to give the bosses >faster > access than you give their minions. Do that and before you know it the > Internet > access budget starts getting cut and/or you keep getting forced to carry more > users with the same or less bandwidth. > > Where I am a "boss", I don't ask for this. It tends to distort > decision-making. > > Find out what's eating the bandwidth. Perhaps block torrents, youtube and such > during work hours, relay all outgoing mail via your ISP's SMTP server, etc.. > Lots of firewall, Linux config and squid recipes for this out there. > > P. > > On May 25, 2010, at 21:31, Kyle Spencer wrote: > > > Correction: example assumes 10-15 "bosses." > > > > ----- Original message ----- > > > This example assumes a 1Mbps link, 100ish total (not necessarily > > > network-active) users, and about 5 "bosses." > > > > > > It will give servers in the 192.168.0/24 range 256Kbps of bandwidth, > > > general > > > users in 192.168.1/24 512Kbps w/ 3KB/s down max w/ 50KB burst, and bosses > > > in > > > the 192.168.2/24 range 256Kbps total w/ 5KB/s down max w/ 50KB burst. > > > > > > Note that squid only manages HTTP traffic, so this won't stop bittorrent > > > users or traffic of other protocols. To manage /all traffic/ you may want > > > to look into systems like Dummynet. > > > > > > Anyway, add the following to the bottom of your squid.conf and subnet your > > > network accordingly (or modify this example according to your existing > > > topology): > > > > > > acl servers src 192.168.0.0/24 > > > acl users src 192.168.1.0/24 > > > acl bosses src 192.168.2.0/24 > > > delay_pools 3 > > > delay_class 1 1 > > > delay_class 2 2 > > > delay_class 3 2 > > > delay_parameters 1 32768/32768 > > > delay_parameters 2 65536/65536 3072/51200 > > > delay_parameters 3 32768/32768 5120/51200 > > > delay_access 1 allow servers > > > delay_access 2 allow users > > > delay_access 3 allow bosses > > > > > > Reload/restart Squid and you're good to go. > > > > > > Regards, > > > Kyle > > > > > > ----- Original message ----- > > > > Hello all, i want to allocate bandwidth to some users(Bosses) so that > > > > even if the link is slow, they are not affected. I was hoping to use > > > > squid to do this but i not succeed. I have a red hat box as my > > > > gateway. > > > > Thanks in advance > > > > > > > > -- > > > > Stephen Kabali > > > > Datacenter Administrator > > > > Uganda Industrial Research Institute (UIRI) > > > > [email protected] > > > > www.uiri.org > > > > _______________________________________________ > > > > LUG mailing list > > > > [email protected] > > > > http://kym.net/mailman/listinfo/lug > > > > > > > > LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > > > > > > > All Archives can be found at > > > > http://www.mail-archive.com/[email protected]/ > > > > > > > > The above comments and data are owned by whoever posted them (including > > > > attachments if any). The List's Host is not responsible for them in any > > > > way. --------------------------------------- > > > > > > > > > > _______________________________________________ > > > LUG mailing list > > > [email protected] > > > http://kym.net/mailman/listinfo/lug > > > > > > LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > > > > > All Archives can be found at http://www.mail-archive.com/[email protected]/ > > > > > > The above comments and data are owned by whoever posted them (including > > > attachments if any). The List's Host is not responsible for them in any > > > way. > > > --------------------------------------- > > > > > > > _______________________________________________ > > LUG mailing list > > [email protected] > > http://kym.net/mailman/listinfo/lug > > > > LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > > > All Archives can be found at http://www.mail-archive.com/[email protected]/ > > > > The above comments and data are owned by whoever posted them (including > > attachments if any). The List's Host is not responsible for them in any way. > > --------------------------------------- > > _______________________________________________ > LUG mailing list > [email protected] > http://kym.net/mailman/listinfo/lug > > LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > All Archives can be found at http://www.mail-archive.com/[email protected]/ > > The above comments and data are owned by whoever posted them (including > attachments if any). The List's Host is not responsible for them in any way. > --------------------------------------- > _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ All Archives can be found at http://www.mail-archive.com/[email protected]/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. --------------------------------------- _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ All Archives can be found at http://www.mail-archive.com/[email protected]/ The above comments and data are owned by whoever posted them (including attachments if any). The List's Host is not responsible for them in any way. ---------------------------------------
