All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TEQL questions
Date: Fri, 22 Feb 2002 09:22:13 +0000	[thread overview]
Message-ID: <marc-lartc-101436982111048@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101424276116149@msgid-missing>

On Thu, Feb 21, 2002 at 02:57:28PM -0800, Chris Murray wrote:
> If figured out why it didn't work after following the howto, there was no 
> mention is that you have to do a:
> 
> ip link set dev teql0 up 

ah! Fixed & added you to the 'thanks to' list.

> On both sides of the link. I am now starting my testing with two 1.5mbps
> links, and it seems to be configured correctly But now it appears that all my 
> traffic is traveling over eth2 and not equally divided between eth1 and eth2.
> I tested by opening two ftp sessions from the remote machine to and ftp server 
> on the internet and I only got 1/2 of my expected bandwith

Have you tcpdumped to verify this assertion? There are issues with packet
reordering which look just like this, but do not indicate that teql is not
working. So, could you run tcpdump on teql0, on eth1 and eth2, and check
where traffic is going? 

Thanks!

Regards,

bert


-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2002-02-22  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 21:58 [LARTC] TEQL questions Chris Murray
2002-02-21  6:36 ` Stef Coene
2002-02-21 22:57 ` Chris Murray
2002-02-22  9:22 ` bert hubert [this message]
2002-02-22 22:22 ` Chris Murray

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-101436982111048@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.