All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath Routing in same subnet - Please take a look
Date: Sat, 07 May 2005 03:41:55 +0000	[thread overview]
Message-ID: <427C3903.BCDBC258@iswest.com> (raw)
In-Reply-To: <427B454C.2010806@rapidtec.de>

Christian Schmid wrote:
> 
> Hello.

> 80.237.244.0/26 dev eth1  proto kernel  scope link  src 80.237.244.52
> default
>          nexthop via 80.237.244.1  dev eth1 weight 100
>          nexthop via 80.237.244.33  dev eth1 weight 100

Do not use weight parameters exceeding a single digit!
 
> I have read postings on the net but all of them are using huge scripts because they are on different
> networks. My problem seems to be a much easier problem but I just cant get this to work..... :(
> 
> Please help.
> 
> Best regards,
> Chris

I'm no expert, but my suggestion is to use 2 NICs and connect one to
each uplink or at least add 2 entries into /etc/iproute2/rt_tables.  I
think you'll find a similar situation answered in the ML within the last
10 days or so, but I can't recall the subject of the thread.  Nor can I
find anything specifying exactly what rt_tables needs to contain :/

You can review what I've gleaned from this ML at 
http://yesican.chsoft.biz/lartc

The most urgent things for you to know:
1) The LARTC HOWTO is wrong
2) You must apply Julian's patch
3) You _really_ need to read nano.txt
4) All of the intelligible success stories WRT multipath are either on
yesican or are linked to from there.

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

  reply	other threads:[~2005-05-07  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 10:22 [LARTC] Multipath Routing in same subnet - Please take a look Christian Schmid
2005-05-07  3:41 ` gypsy [this message]
2005-05-07  4:25 ` Alexander Samad
2005-05-09 23:40 ` Andy Furniss

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=427C3903.BCDBC258@iswest.com \
    --to=gypsy@iswest.com \
    --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.