From: "Adam" <adam@techcommune.org>
To: netfilter@lists.netfilter.org
Subject: Looking for fair bandwidth management advice.
Date: Sun, 2 Mar 2003 10:49:57 -0500 [thread overview]
Message-ID: <001601c2e0d3$61e6eb80$0b00a8c0@Mustang> (raw)
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Hello, this is my first post to the netfilter list. Here is my issue:
My internet connection is 28.8 from my home (painfull, but I won't get into why it has to be this way). I run a linux iptables NAT/firewall to allow net access to machines on my network. However, whenever one machine uses the full link speed (downloading a file), it pretty much cuts the rest of the machines off. Latency goes over 1 second and packet loss is pretty severe for the other machines. I notice on faster links, filling the upload and download streams does not send other connections off into timeout land, but it does add latency to them though.
I did read the bandwidth management section of the Linux Advanced Routing & Traffic HOWTO. Stochastic Fairness Queueing seams to fit what I'm looking for. However, I'm no TCP/IP expert, so I am looking for advice on how you would go about working with this setup. Thanks --Adam.
[-- Attachment #2: Type: text/html, Size: 1486 bytes --]
reply other threads:[~2003-03-02 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001601c2e0d3$61e6eb80$0b00a8c0@Mustang' \
--to=adam@techcommune.org \
--cc=netfilter@lists.netfilter.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