From: "Tóth Nándor" <nug@sch.bme.hu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Good pratice with a Linux Gateway / Traffic Shapping
Date: Wed, 12 Jan 2005 14:06:11 +0000 [thread overview]
Message-ID: <41E52ED3.4010209@sch.bme.hu> (raw)
In-Reply-To: <BBAABEC31B76D44FA122230711D1B64104E00F@email-srv.sqliaison.com>
Hi!
I am not very experienced, but maybe i can help you.
TechSupport wrote:
> Hi,
> I am the network administrator of my company, I know quite well Windows networking and a few about Linux and its amazing routing and QOS capabilities.
> Right now, we have a bustable T1, which mean that the bill increase with out T1 use.
> I have decided to find a way to shape the traffic so I can stay at a raisonable speed of 256 kb/s (Up/down) on my T1.
> I have linux gateway with 2 nics behind a PIX firewall.
> Right know, the gateway and the pix are configured in a way so I can have a network segment inside my internal network.
> The Linux version is suse PRO 9.2
> My questions are (yes, they are several questions)
>
>>what is the best method to use to shape the traffic on my linux gateway ?
I think you should use HTB method.
http://luxik.cdi.cz/~devik/qos/htb/
Limit the incoming and/or outgoing bandwith, maybe make some subclasses
to have garantied bandwith for web, mail, etc.
You should attach an SFQ qdisc to the most popular classes.
> I know that there is several possibilities, like wondershaper script , htb.init script and even l7-filter but I still confused about the right procedure that I have to use.
>
>>most probably, I have to customize my script so it can reflect what I want, I know also that I have to learn pretty much on those different shaping methods, but is there some good books/ internet site where I can find some usefull information about that ? I also looking for some guides that could help me to begin the project.
>>also, is there a way to make the shaping different for particular ips or protocols ? I know that I can mark some packets but still confused how to make all the stuff work.
>
> The linux world is so huge that I am pretty lost ... so different method, so many considerations, patches to apply, stuff like that. I want to learn and master my network, and working hard is not a problem. The problem is maybe when a newby starts to enter the linux world, it is quite confusing ... Anyway, I am ready to work hard on this project and I hope I can count on the linux community to give me a little help.
> I know that those questions are maybe already been asked by other people in the same situation. So I will try to create a guide as the project will evolve and make it available on the net for everybody.
> I really need some advices here because I know that it is possible.
> Any help will be apreciated.
This site helped me a lot, to understand:
http://www.knowplace.org/shaper/
I didn't use any prepared scripts but write my own using iptables and tc
basic commands. If you are a network administrator i recommend this to
you too, because this is the way to really understand what you do.
--
Udv,
Nandor
Ps. Welcome to the linux community!
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-12 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 13:48 [LARTC] Good pratice with a Linux Gateway / Traffic Shapping TechSupport
2005-01-12 14:06 ` Tóth Nándor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41E52ED3.4010209@sch.bme.hu \
--to=nug@sch.bme.hu \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox