All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] even bandwith for users on 2 newtworks
Date: Sun, 15 Jan 2006 23:25:16 +0000	[thread overview]
Message-ID: <43CAD9DC.3000708@gmx.net> (raw)
In-Reply-To: <43cab7ca69c72@wp.pl>

Flemming Frandsen schrieb:
> Hariett Jones wrote:
> 
>> I want server to share bandwith from eth0 evenly for users on eth1
>> and wlan0. How can i make it ? Is it possible ? As far as i know htb
>> splits outgoing bandwith on one device only.
> 
> This is the most braindead defect of Linux (IMHO): You can't, because
> you can only shape outgoing traffic on an interface.

Yes, you can. Easily. And you don't need IMQ/IFB.

eth1->eth0 and wlan0->eth0 are easy. Classical outgoing shaping.
eth0->eth1 and eth0->wlan0 are similar. Outgoing shaping on eth1 and
wlan0 each with a limit of half the incoming bandwidth of eth0.

I had to learn that Linux can perform most of the tasks people claim
are impossible. Some involve a lot of iproute2 trickery and even the
standard Howtos may tell you the problems can't be solved.

However, there are some cases where IMQ/IFB is useful. I don't want
to bash these intermediary devices, they're just abused too many
times.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-01-15 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 20:59 [LARTC] even bandwith for users on 2 newtworks Hariett Jones
2006-01-15 21:42 ` Flemming Frandsen
2006-01-15 23:25 ` Carl-Daniel Hailfinger [this message]
2006-01-16 11:45 ` Flemming Frandsen
2006-01-16 13:01 ` Alexey Toptygin
2006-01-16 21:25 ` Flemming Frandsen
2006-01-16 21:41 ` Peter Surda
2006-01-17  0:06 ` Carl-Daniel Hailfinger
2006-01-17 13:27 ` Flemming Frandsen

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=43CAD9DC.3000708@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.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.