All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ADSL channel boding or Load balancing
Date: Fri, 26 Oct 2007 02:11:50 +0000	[thread overview]
Message-ID: <47214CE6.60005@riverviewtech.net> (raw)
In-Reply-To: <c2cd58b40710110817t19d6b45dpcff432934c367d22@mail.gmail.com>

On 10/25/2007 1:06 PM, the sew wrote
>                +-----------+     +---------+
> +--------+     | ...245.18 +-----+ ...77.1 |     +-------+
> | ...0.x +-----+ ...0.1    |     |    COLO +-----+ 101.x |
> +--------+     | ...245.19 +-----+ ...78.1 |     +-------+
>                +-----------+     +---------+
> 
> Currently I'm natting on 0.1 ( -o ppp+ -j MASQUERADE ) , This was 
> setup by default as I did not want 0.x to be routed. I've however 
> taken off the natting, and added a route for 0.20/32 dev ppp62 
> nexthop dev ppp32 ( the 2 vpn interfaces) at COLO and obviously same 
> nexthop routes at 0.1 for 101.x

Ok, good.  The NATing at 0.1 was part of the problem.

> testing from 0.20, I scp a tar file over to 101.20 , still goes via 
> one line at time, the route cache which I disabled, just reroute it 
> the whole time( about every 5 sec) via the diffrent uplink, but not 
> to our result we want

Hum.  I would question the routes then.

> I use sysstat to check the speeds and tcpdump verified I its from 
> 0.20 -> 101.20 ssh

Ok.

> I understand now very clearly the key part.
> 
> My problem must be the tunnel, im sure im messing up,  the equal cost 
> multipath routing , am I using the right utitily? , still iproute2 
> right, or is iptables gonna play big part here as well?

To the best of my knowledge you will still be using the "ip" command 
from iproute2.  Will you please show us your routing table and / or the 
ip route command you are using to set up your ecmp route?



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-10-26  2:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 15:17 [LARTC] ADSL channel boding or Load balancing the sew
2007-10-11 16:18 ` Grant Taylor
2007-10-11 16:21 ` Grant Taylor
2007-10-11 18:12 ` the sew
2007-10-11 18:42 ` Grant Taylor
2007-10-25  5:49 ` the sew
2007-10-25 14:38 ` Grant Taylor
2007-10-25 18:06 ` the sew
2007-10-26  2:11 ` Grant Taylor [this message]

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=47214CE6.60005@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.