All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple Internet Links problem
Date: Thu, 13 Dec 2001 18:41:44 +0000	[thread overview]
Message-ID: <marc-lartc-100826864207240@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100810683231420@msgid-missing>


	Hello,

On Fri, 14 Dec 2001, Stephen wrote:

> 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

	I still don't understand your setup ...

> 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?

	I can confirm a problem with static routes that remain in dead state
but I don't understand your question. Is this the same problem you are
talking about?

> Thanks again

Regards

--
Julian Anastasov <ja@ssi.bg>


_______________________________________________
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 18:41 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
2001-12-13 18:41 ` Julian Anastasov [this message]
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-100826864207240@msgid-missing \
    --to=ja@ssi.bg \
    --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.