From: Guy Van Den Bergh <guy.vandenbergh@pandora.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sharing bandwidth between two interfaces
Date: Thu, 05 Apr 2001 17:41:01 +0000 [thread overview]
Message-ID: <marc-lartc-98649251000646@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98620649426867@msgid-missing>
Depending on what you are trying to do, channel bonding or teql
should do the trick. But I haven't tried these things out (yet)...
One more thing: channel bonding nor teql will work when those two
interfaces are connected to different ISPs. If this is the case,
only ingress policing on your local LAN interface will work.
Btw, I don't think shaping on a loopback interface will solve this
problem...
Guy
worm@dkik.dk wrote:
> Hi,
>
>
>>> Is it correct understood that you want to limit some traffic which can go
>>> out on two different interfaces, to 64K in total?
>>
>
>> Yes, that's it. Sorry, my english isn't any good...
>
>
> Ok... If anyone knows a way to do this I would like to know too ;-) Maybe it
> is possible by shaping on a loopback interface?
>
>
> Christian
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-04-05 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 10:14 [LARTC] Sharing bandwidth between two interfaces
2001-04-02 18:21 ` Christian Worm Mortensen
2001-04-04 8:14 ` Vladimir Smelhaus
2001-04-04 10:48 `
2001-04-05 14:16 ` worm
2001-04-05 17:41 ` Guy Van Den Bergh [this message]
2001-04-05 20:42 ` Christian Worm Mortensen
2001-04-05 21:59 ` Guy Van Den Bergh
2001-04-06 6:24 ` Christian Worm Mortensen
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-98649251000646@msgid-missing \
--to=guy.vandenbergh@pandora.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox