From: Federico Montesino Pouzols <p5087@quintero.fie.us.es>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple interfaces thru one qdisc
Date: Fri, 01 Jun 2001 12:48:11 +0000 [thread overview]
Message-ID: <marc-lartc-99140012025113@msgid-missing> (raw)
On Fri, Jun 01, 2001 at 09:42:04AM -0300, Ethy H. Brito wrote:
> On Fri, 1 Jun 2001, MONTESINO POUZOLS FEDERICO wrote:
>
> >
> > I am not sure, but, perhaps, the teql discipline may be a
> > solution. With teql you could make a new interface (teql0 or something
> > like that) consisting of the two ppps. Look at the HOWTO, there are some
> > examples of teql, search also through this list archive.
>
> If teql behaves as explained in Linux2.4 Adv HOWTO it is a round-robin
> device. It would do what I need if all ppp lines go to the same client which
> is not the case. Could you confirm that it is a simple RR device?
As far as I know (I have read about it, but not tested) it _is_
Round-Robin.
I think that, perhaps, you can impose the queue discipline on
tql0 (that masters both ppps), and then set different routes using
ppp0 and ppp1. I wonder if the teql qdisc will shape the ppp0 and
ppp1 sending rate. I doubt it.
Please, if there is anybody who knows teql well, confirm this
point. Maybe this behaviour can be changed.
>
> Ethy H. Brito /"\
> InterNexo Ltda. \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML
> +(12) 341-6860 X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
> Sao Jose dos Campos / \
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-06-01 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 12:48 Federico Montesino Pouzols [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-31 12:36 [LARTC] Multiple interfaces thru one qdisc Ethy H. Brito
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-99140012025113@msgid-missing \
--to=p5087@quintero.fie.us.es \
--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.