All of lore.kernel.org
 help / color / mirror / Atom feed
From: STiNG of DEATH <nsmail06@coldfusion.4mg.com>
To: lartc@vger.kernel.org
Subject: [LARTC] IP Masquerade and bandwidth management
Date: Sat, 07 Jul 2001 12:53:36 +0000	[thread overview]
Message-ID: <marc-lartc-99451034603588@msgid-missing> (raw)

Hi all.

Sorry for asking such a simple question, but if I had a LAN of machines
with private IP addresses (192.168.0.x), a cable connection, and a Linux
machine doing NAT using iptables, what would be the best way of going
about setting bandwidth limits for certain machines on the LAN?

I assume that packets would have to be marked as they were forwarded by
netfilter (the iptables forwarding table) based on their
source/destination inside the LAN and then a set of class based
bandwidth management rules as per section 9 of the Advanced Routing
HOWTO. Is this the correct approach?

Also, this is probably a bit obscure, but is it possible to discriminate
between the type of data being carried by a protocol when doing
bandwidth management? For example, giving HTML files transferred over
http a larger share of bandwidth than, say, MP3 files over the same
protocol? Obviously this would involve sending all traffic through some
kind of proxy which would then determine which connections were carrying
what kind of file. This probably sounds quite absurd, but is it
something that has ever been considered?

Thanks for your time. Great document.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

                 reply	other threads:[~2001-07-07 12:53 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=marc-lartc-99451034603588@msgid-missing \
    --to=nsmail06@coldfusion.4mg.com \
    --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.