throttling network access

On Mon, 23 Jun 2003 21:54:32 +0000, Bob Tennent wrote:

> My son accesses the network via my IP-masquerading Linux box. He uses
> something called e-mule which results in continuous heavy loading of
> our cable connection to the internet. How, apart from cutting him off
> completely, can I throttle his access so I can get some packets in or
> out?
>
> Bob T.
What is your current network setup?

On Mon, 23 Jun 2003 21:54:32 +0000, Bob Tennent wrote:

> My son accesses the network via my IP-masquerading Linux box. He uses
> something called e-mule which results in continuous heavy loading of
> our cable connection to the internet. How, apart from cutting him off
> completely, can I throttle his access so I can get some packets in or
> out?
>
> Bob T.
If the traffic you wish to limit is through one NIC, simply use something
such as:
tc qdisc add dev eth# root tbf rate 207Kbit buffer 5Kb/8 limit 10Kb
(207Kbit is 80% of 256Kbit in this example, so set according to your needs)

My son accesses the network via my IP-masquerading Linux box. He uses
something called e-mule which results in continuous heavy loading of
our cable connection to the internet. How, apart from cutting him off
completely, can I throttle his access so I can get some packets in or
out?

Bob T.

On Mon, 23 Jun 2003 19:51:46 +0000, nunya wrote:

>> My son accesses the network via my IP-masquerading Linux box. He uses
>> something called e-mule which results in continuous heavy loading of
>> our cable connection to the internet. How, apart from cutting him off
>> completely, can I throttle his access so I can get some packets in or
>> out?

> What is your current network setup?

Linux box with 2 NICs, one to a cable modem, the other to a hub into
which two other computers connect. The Linux box uses IP-masquerading to
forward packets to/from the other computers from/to the internet.

Bob T.

On Mon, 23 Jun 2003 19:54:42 +0000, nunya wrote:

>> My son accesses the network via my IP-masquerading Linux box. He
>> uses something called e-mule which results in continuous heavy
>> loading of our cable connection to the internet. How, apart from
>> cutting him off completely, can I throttle his access so I can get
>> some packets in or out?

> If the traffic you wish to limit is through one NIC, simply use something
> such as:

> tc qdisc add dev eth# root tbf rate 207Kbit buffer 5Kb/8 limit 10Kb

I'm glad it's so simple :+) (Why isn't there a man page for tc?)

Would it be possible not to limit the bandwidth at all times but to give
non-forwarded packets higher priority, a kind of "nice" for networking?

Bob T.

Bob Tennent <BobT@cs.queensu.ca> wrote:
> On Mon, 23 Jun 2003 19:54:42 +0000, nunya wrote:

> >> My son accesses the network via my IP-masquerading Linux box. He
> >> uses something called e-mule which results in continuous heavy
> >> loading of our cable connection to the internet. How, apart from
> >> cutting him off completely, can I throttle his access so I can get
> >> some packets in or out?
>
> > If the traffic you wish to limit is through one NIC, simply use something
> > such as:

> > tc qdisc add dev eth# root tbf rate 207Kbit buffer 5Kb/8 limit 10Kb

> I'm glad it's so simple :+) (Why isn't there a man page for tc?)

> Would it be possible not to limit the bandwidth at all times but to give
> non-forwarded packets higher priority, a kind of "nice" for networking?
> Bob T.

i don't have any idea of your linux cpu speed, but just acting as the
gateway is going to slow it down, maybe that is really most of your
problem.

if so, a cheapie NAT router would put all hosts on the same lan, but
you lose some flexibility in controlling the kiddies' access to the
wan. --Loren

On Tue, 24 Jun 2003 11:15:09 GMT, lcoe wrote:

>> >> My son accesses the network via my IP-masquerading Linux box. He
>> >> uses something called e-mule which results in continuous heavy
>> >> loading of our cable connection to the internet. How, apart from
>> >> cutting him off completely, can I throttle his access so I can get
>> >> some packets in or out?

> i don't have any idea of your linux cpu speed, but just acting as the
> gateway is going to slow it down, maybe that is really most of your
> problem.

No evidence of that from top: typically 98% idle.

Bob T.