From: "Rio Martin." <rio@martin.mu>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: How to deal with burstable bandwidth from ISP ?
Date: Tue, 29 Jul 2003 08:57:53 +0000 [thread overview]
Message-ID: <marc-lartc-105946895425961@msgid-missing> (raw)
On Tuesday 29 July 2003 15:34, Stef Coene wrote:
> Then it's better to create a separate class for it and put your ssh traffic
> in it.
okay, i 'll do it your way ..
> > I am still learning about fw mark to shape both incoming and outgoing
> > bandwidth from my network.
> Incoming traffic can be tricky. You need the imq device or a dedicated
> shaper for it so you can shape on 2 nic's.
for marking outgoing from local network, i put those rules in POSTROUTING.
i just want to know how about marking for downstream connection (from internet
to my local network), where should i put this rule ? Note that i use
different router for incoming and outgoing connection (multipath routing)..
> Then you have a problem. You can not configure this with htb because you
> don't know the ISP bandwidth. However, you can create a setup for 1024
> kbps. You will loose some precision because you are not the bottleneck
> anymore, but you will able to shape your link.
Just a thought in my mind, script work ? latency check ?
i need to figure this out, because all local ISP seems to be applied this kind
of rule to make price for Internet bandwidth more cheaper ..
And sadly i must take this ISP service because i cannot afford higher and
clear channel bandwidth ratio.
Regards,
Rio Martin.
--
Hell hath no fury like a bureaucrat scorned.
-- Milton Friedman
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-07-29 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 8:57 Rio Martin. [this message]
2003-07-29 17:28 ` [LARTC] Re: How to deal with burstable bandwidth from ISP ? Stef Coene
2003-07-31 2:23 ` Rio Martin.
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-105946895425961@msgid-missing \
--to=rio@martin.mu \
--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