[LARTC] Ip accounting, masq'ing and bandwidth sharing

[LARTC] Ip accounting, masq'ing and bandwidth sharing

[Simon Bland]

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/

Re: [LARTC] Ip accounting, masq'ing and bandwidth sharing

[Stef Coene]

> 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..
You can't control how much data you receive.  But you can try to do it.  If 
you give one connection 1kbyte/s, tcp will control his behaviour untill the 
1kilobyte/s is reached.  But you can't prevent that they send more.  
All data that you receive on ppp0 is also transmitted on eth0.  So 
controlling the outgoing bandwidth on eth0 is the same as controlling the 
incoming traffic on ppp0 (if you don't run any special services on the box).  
You can't control incoming traffic (there some work arounds), so you have to 
use eth0 to control the incoming traffic on ppp0

If you make sure you never receive that so many data that the modem can't 
handle it, you will never have big queueus in the modem.  So limiting the 
total incoming traffic on ppp0 to 99% of the link, is a good idea.  Big 
queues means a long time for a packet to travel thru the queue, so this 
create big latency.

By creating a queue for each ip in the LAN, you can make sure that each IP 
has the same chance to send/receive something.  So launching 10 parallel 
downloads is useless.

Stef 

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Re: [LARTC] Ip accounting, masq'ing and bandwidth sharing

[raptor]

from what i've read on the lartc-faq best suited for this sort of things is SFQ ... read the explanation and u will understand..

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