From: Eric Leblond <eric@regit.org>
To: lartc@vger.kernel.org
Subject: [LARTC] teql and gre tunnel
Date: Wed, 07 May 2003 23:25:47 +0000 [thread overview]
Message-ID: <marc-lartc-105234990307145@msgid-missing> (raw)
Hi everybody,
I want to do the following setup :
| | Tun1 - Link 1 | Tun1 | |
Router A | teql | INTERNET Link - | | teql |router B
| | Tun2 - Link 2 | Tun2 | |
This should permit to agregate Link 1 and Link 2 (less the cost of the
encapsulation). The two tunnels are GRE ip tunnel.
It seems to work fine in theory : I manage to send packet on the teql
from one of the node (debian sid with kernel 2.4.20-686).
But I've got a problem to put a teql qdisc on the tunnel on one of the
node. When doing :
tc qdisc add dev tun1 root teql0
I only manage to have an RTnetlink message.
But when doing :
tc qdisc add dev eth0 root teql0
It works fine.
The second router is debian woody based with a from sid backported tc
and a 2.4.20 home made kernel.
Is there a special requirement to have this working ?
BR,
--
Eric Leblond <eric@regit.org>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-05-07 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-105234990307145@msgid-missing \
--to=eric@regit.org \
--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