All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Bland <angel@khaosse.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Ip accounting, masq'ing and bandwidth sharing
Date: Mon, 05 Aug 2002 06:59:53 +0000	[thread overview]
Message-ID: <marc-lartc-102853077629151@msgid-missing> (raw)

I'll cut to the chase of what I'm trying to do..

I've set up my system with a 56k dial-up connection on the gateway, and 3 
machines on the LAN. I'm using a set of iptables to handle the firewall 
and Masq'ing, and ipac-ng to do the accounting on a per ip basis for each 
machine on the LAN's usage.

All that's pretty trivial.. What I want to do next is be able to guarentee 
bandwidth to each machine on the LAN, so that 1 person trying to pull 
large amounts of data doesn't totally lock the others off being able to do 
whatever they want to use it for..

From what I've read this can be done by applying a set of queues on the 
eth0 side of the gateway machine, but that doesn't seem to make sense (how 
do the queues there prevent the modem from being choked by the incoming 
data?

What I'd like is either an explanation of how queueing on eth0 works for 
what I'm doing, or a set of rules/explanations of how to set up an 
appropriate set of queues on the ppp interface that handle the masq'ing 
settings..

Hope that makes sense..

Thanks. :)

-- 
Freedom is just chaos with better lighting. 

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

             reply	other threads:[~2002-08-05  6:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  6:59 Simon Bland [this message]
2002-08-05 17:59 ` [LARTC] Ip accounting, masq'ing and bandwidth sharing Stef Coene
2002-08-06 18:22 ` raptor

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-102853077629151@msgid-missing \
    --to=angel@khaosse.net \
    --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.