|reply to Squiddy |
Re: Bandwidth shaping only on port 80. Penalize heavy http.
Thanks for pointing that out.
Yes, I could have gone via the squid way, but my users are too noob or non tech to add proxy to their browsers and again take it off when they go back home. Though thats not impossible to implement but too many people and rearrangement of network involved. If it could be done without disturbing the existing setup ? That's why I said something similar to netequalizer or arbitrator.
said by maxtor:You missed an important part of Squiddy's solution. Instead of configuring each users browser he suggests to create a transparent proxy by intercepting the port 80 web traffic in the Linux firewall of the gateway server and redirecting it through squid.
Yes, I could have gone via the squid way, but my users are too noob or non tech to add proxy to their browsers and again take it off when they go back home.
His solution has a number of benefits for your situation:
- adding squid is reducing bandwidth usage by serving popular content from its cache instead of fetching it repeatedly from the Internet.
- no client (workstation) side configuration changes (that could be subverted by knowledgeable users).
- using application specific (http traffic) delay_pool in squid allows finer control over bandwidth usage then qos at the network transport layer (and it appeared as if you didn't want to use qos anyway).
- all needed software is included with most Linux distributions so there is no need to hunt for additional software.
Regarding squid delay pools: HOWTO .
Regarding squid as transparent proxy: HOWTO .
You can find many more examples if you google the subject.
Got some spare cpu cycles ? Join Team Helix or Team Starfire!
Exactly, this is exactly what I do on my home network. Transparent mode is very useful since it is, as the name implies, completely transparent to the clients. Squid caching is amazing and tremendously increases the speed of the network as well as errata update downloads.