All of lore.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trouble using "nexthop"
Date: Thu, 06 Dec 2001 15:44:44 +0000	[thread overview]
Message-ID: <marc-lartc-100765376423187@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100749309111802@msgid-missing>

On Thu, Dec 06, 2001 at 01:30:41PM +0100, bert hubert wrote:

> Do you have CONFIG_IP_ROUTE_MULTIPATH=y in your .config?

Yup,

CONFIG_IP_ROUTE_MULTIPATH=y

So I guess it has to be something really obscure, like multipath not working
with a particular netmask (one here is a /27, one a /28)?? That is, it looks
like there's really a bug in the code, not my configuration?

One of the few things I haven't tried is setting CONFIG_IP_ROUTER, since the
system in question isn't only a router and what that claims to do is not add
anything but instead turn off kernel code that usefully optimizes host
functions. But I suppose many of those using the routing functions have this
set, so maybe I'll try it next.

Whit

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-12-06 15:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 19:10 [LARTC] Trouble using "nexthop" Whit Blauvelt
2001-12-04 21:35 ` Whit Blauvelt
2001-12-04 22:23 ` Whit Blauvelt
2001-12-04 23:05 ` Julian Anastasov
2001-12-05 15:59 ` Whit Blauvelt
2001-12-05 16:12 ` Whit Blauvelt
2001-12-05 16:25 ` Julian Anastasov
2001-12-05 17:15 ` jcastellet
2001-12-05 19:48 ` Whit Blauvelt
2001-12-06  0:12 ` Whit Blauvelt
2001-12-06 12:30 ` bert hubert
2001-12-06 15:44 ` Whit Blauvelt [this message]
2001-12-06 16:09 ` Christoph Simon
2001-12-06 17:56 ` Whit Blauvelt
2001-12-20 12:46 ` Julian Anastasov

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-100765376423187@msgid-missing \
    --to=whit@transpect.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.