From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Frottle + Bridge + IMQ
Date: Thu, 24 Jun 2004 23:05:32 +0000 [thread overview]
Message-ID: <40DB5E3C.8050401@wildgooses.com> (raw)
In-Reply-To: <4631.212.104.100.39.1088112904.squirrel@oldmail.it-academy.bg>
>To be able to serve them in a
>predetermined, controlled fashion I want to put all traffic that goes
>out of eighter LAN NIC into IMQ device and impose QoS policy on top of
>it. This will allow to use in the most efficient manner all available
>WAN bandwidth.
>
Perhaps I misunderstand, but for outoing on the WAN interface you can
attach stuff directly. For incoming you can use iptables to direct it
to the IMQ device.
Are you saying that using iptables on the WAN interface to direct stuff
to IMQ then causes problems if you use iptables on the wireless
interface (to direct to frottle)? I would have thought you have a clear
partition on when to use each redirection?
If not, then with some limitations you can of course attach qdiscs to
the outbound on each of the wireless and wired interfaces. This makes
it harder to limit inoming bandwidth, but may be sufficient in some
circumstances.
If you have simple incoming requirements you could also look at GRED
which can be attached to the incoming interface, and has multiple
queues. See
http://www.opalsoft.net/qos/DS-27.htm
For iptables patches you really want to post to the iptables guys I
should think?
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-24 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 21:35 [LARTC] Frottle + Bridge + IMQ Marin Stavrev
2004-06-24 23:05 ` Ed Wildgoose [this message]
2004-06-25 7:22 ` Marin Stavrev
2004-06-25 8:12 ` Ed Wildgoose
2004-06-30 15:28 ` ThE LinuX_KiD
2004-06-30 19:05 ` Marin Stavrev
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=40DB5E3C.8050401@wildgooses.com \
--to=lists@wildgooses.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.