All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen <meridian@tha.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple Internet Links problem
Date: Thu, 13 Dec 2001 17:23:47 +0000	[thread overview]
Message-ID: <marc-lartc-100826427026876@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100810683231420@msgid-missing>

Thanks for that. I have it working now.

Here is my much neater route table. My rules look scarey but I think thats
ok. Sorry Im still using a few tables :)

ip ro add 0.0.0.0/0 dev ppp0 proto static table main
ip ro add 0.0.0.0/0 dev eth0 proto static table eth0
ip ro add 0.0.0.0/0 via 202.2.2.17 dev eth1 proto static table eth1
ip ro add 0.0.0.0/0 via 202.3.3.129 dev eth2 proto static table eth2
ip ro add from 202.1.1.128/25 via 202.3.3.129 proto static table eth2


My question is tho, I have your route patch in my kernel, but if I do a
ifconfig eth1 down and then ifconfig eth1 up, stuff that was headed out
eth1 before the down/up now goes out the default route ppp0 until I re-add
the eth1 route. I believe that with your patch the routes should stay?

Thanks again


> On Thu, 13 Dec 2001, Stephen wrote:
> 
> > Julian I am already using a kernel patched with your routes-2.2.19 patch
> 
> 	Oh! But did you read the documents?
> 
> > here is an example of my rule and route list i am presently trying and the
> > errors i am getting. I have 202.1.1.0/25 + 2 other ips on ppp0 my main
> > static ip link. The 202.2.2 is my adsl on eth1. 202.3.3 is my cable
> > on eth2 which i try to route all my clients from 202.1.1.128/25 out of by
> > default.
> 
> 	No, there are some rules you must follow:
> 
> - remove all your default routes from table main
> 
> - all directly connected networks must be added to table main,
> it includes all host routes (/32). Don't try to introduce errors
> by using extra tables. It could work if you do them correctly.
> 
> 	As result, all direct routes (without gateway) are in
> table main and the hosts from all networks can talk directly IP
> and ARP without hiting wrong gatewayed route by mistake.
> 


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

  parent reply	other threads:[~2001-12-13 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 21:38 [LARTC] Multiple Internet Links problem Stephen
2001-12-11 21:50 ` Julian Anastasov
2001-12-12 21:53 ` Stephen
2001-12-13  0:14 ` Julian Anastasov
2001-12-13 17:23 ` Stephen [this message]
2001-12-13 18:41 ` Julian Anastasov
2001-12-14  0:35 ` 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-100826427026876@msgid-missing \
    --to=meridian@tha.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.