All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multipath Routing in same subnet - Please take a look
Date: Mon, 09 May 2005 23:40:21 +0000	[thread overview]
Message-ID: <427FF4E5.50505@dsl.pipex.com> (raw)
In-Reply-To: <427B454C.2010806@rapidtec.de>

Christian Schmid wrote:

>         nexthop via 80.237.244.1  dev eth1 weight 100
>         nexthop via 80.237.244.33  dev eth1 weight 100
> 
> 
> 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..... :(

Saw this on netdev, solution disable IP_ROUTE_MULTIPATH_CACHED

http://news.gmane.org/find-root.php?group=gmane.linux.network&article%774

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

      parent reply	other threads:[~2005-05-09 23:40 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
2005-05-07  4:25 ` Alexander Samad
2005-05-09 23:40 ` Andy Furniss [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=427FF4E5.50505@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.