From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Best way to manage a 128Kb/s pipe - help
Date: Tue, 05 Feb 2002 18:52:01 +0000 [thread overview]
Message-ID: <marc-lartc-101293518430307@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101293375625909@msgid-missing>
On Tuesday 05 February 2002 19:27, Steven Thompson wrote:
> Hi All
>
> I have a 128Kbs internet connection used for in-coming and out-going
> traffic.
>
> What tools do I need to manage the following services:
> http, ssh (scp), ftp, streaming audio, smtp, instant messenger.
Start reading the HOWTO :
http://ds9a.nl/2.4Routing/HOWTO/cvs/2.4routing/output/2.4routing-9.html
>
> Q1. What is the best kernel to use at the moment and what other tools need
> to be installed.
I use kernel 2.4.9 and latest iproute2.
>
> Internet -------- eth0 | Linux fw | eth1 ----------- internal LAN
>
> The Linux firewall will running the following : Squid, Posfix mail server
> and NATing for internal LAN.
>
>
> Q2. How do divide the 128Kbs pipe so the following criteria is met:
You can use HTB or CBQ and even add SFQ qdiscs and as filter u32 or fw.
>
> All ssh sessions (no scp) - Min 10Kbs, but can burst to 128Kbs if
> available
> All scp or rsync uploads or downloads - Max 64Kbs , but can burst to
> 128Kbs if available (not sure what's best)
> All icmp & udp DNS requests - Min 10Kbs , but can burst to 128Kbs if
> available (not sure what's best)
> All smtp incoming and out going - Max 64Kbs , but can burst to 128Kbs if
> available (not sure what's best)
> All http surfing and downloads - Max 64Kbs , but can burst to 128Kbs if
> available (not sure what's best)
> All ftp downloads and uploads - Max 64Kbs , but can burst to 128Kbs if
> available (not sure what's best)
> All steaming audio and video gets what left over, but can burst to 128Kbs
> if available (not sure what's best)
>
> Q3 I know squid can be set-up to limit bandwidth to a certain group or
> subnet ( i.e. 192.168.0.0/24 = max 64Kbs),
> but as far as I know it can't be set up to burst to 128Kbs if it was
> available. - Is the best option for HTTP limiting.
Question ?
>
>
> Q4. What is the best real time bandwidth usage tool. (i.e. I measure all
> incoming and out-going traffic on the
> Internet interface (eth0) using "IPTRAF" which works great but is
> there a real-time web interface or a better tool
> than "Iptraf"
I wrote a perl script : monitor.pl (can be found on www.docum.org).
Stef
--
stef.coene@docum.org
More QOS info : http://www.docum.org/
Title : "Using Linux as bandwidth manager"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-02-05 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 18:27 [LARTC] Best way to manage a 128Kb/s pipe - help Steven Thompson
2002-02-05 18:52 ` Stef Coene [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=marc-lartc-101293518430307@msgid-missing \
--to=stef.coene@docum.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.