All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problem with ip route . VERY SLOW
Date: Tue, 25 Oct 2005 06:59:27 +0000	[thread overview]
Message-ID: <435DD7CF.F4691818@iswest.com> (raw)
In-Reply-To: <001901c5d884$aeb61b60$b500a8c0@NOVIS.COM>

Franck LEPRETTE wrote:

> I remember that I have 3 interfaces and I wonder my self if it's possible
> that there are too many interfaces on the computer; or there are
> restrictions with iproutes2 etc...?

No, there are not too many interfaces.  I have run 4 all at once.  Three
were ethernet (DSL) and 1 ppp (Modem).

Yes, there are iproute2 issues.
1) The LARTC HOWTO is wrong.
2) Your routing tables seem to have only 2 entries; you probably need 3.
3) Similar IP addresses can be a problem.  192.168.0.0/24 is too similar
to 192.168.100.0/24.  Worse, private IPs are a pain.  (All that is my
opinion, not necessarily fact.)
4) There shouldn't be a default route.  Instead, there should be a
default route for each external interface such that packets received on
one get replied on the same one.  This link is apparently dead
http://selab.edu.ms/twiki/bin/view/Networking/MultihomedLinuxNetworking
so read this instead
http://yesican.chsoft.biz/lartc/MultihomedLinuxNetworking.html

Post your configuration files.  Do not just describe them.  Give us an
explanation of the setup, possibly including some "ASCII art".

Here's a link where you will find other's successes:
http://yesican.chsoft.biz/lartc/index.html

Read EXAMPLES and MULTIPATH and follow the links.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-10-25  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 10:21 [LARTC] Problem with ip route . VERY SLOW Franck LEPRETTE
2005-10-24 12:39 ` Franck LEPRETTE
2005-10-24 18:14 ` Franck LEPRETTE
2005-10-25  6:59 ` gypsy [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=435DD7CF.F4691818@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.