From: "Adrian C." <drupix@gmail.com>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: SSL Certificate signing problem
Date: Mon, 11 Oct 2004 07:35:36 +0200 [thread overview]
Message-ID: <60a746890410102235fa2198a@mail.gmail.com> (raw)
In-Reply-To: <60a746890410100055478e79cf@mail.gmail.com>
Problem solved. I have written a looong script ;)
On Sun, 10 Oct 2004 10:55:52 +0300, Adrian C. <drupix@gmail.com> wrote:
> One more thing, if i try a load-balancing with ip route will it know
> to failover if one of the routes fails?
>
>
>
>
> On Sat, 09 Oct 2004 21:07:19 -0400, Kevin J. Cummings
> <cummings@kjchome.homeip.net> wrote:
> > Adrian C. wrote:
> > > If i assign metric 1 to 1st gway and 2 to 2nd it never falls back from
> > > gateway with best metric. Even if it goes down it still sticks to it.
> > > Something is terribly wrong. I am running Slackware 10.
> >
> > I just went back and re-read what "Unix Networking" and "Linux Network
> > Administrator's Guide" have to say about Metrics and I'm wrong.
> > They apply to Routing daemons (like RIP and gated) and help pick the
> > "fastest" gateways (apparently, the metric is supposed to indicate a
> > number of "hops" from here to there....)
> >
> > However, what if, you create a process which does nothing else but check
> > the status of interface 1. Set up a default route through interface 1
> > with a default metric (of say "2"). When the interface goes down, have
> > the process "bring up" the second route by adding it to the routing
> > table with a metric of "1". Now the second interface is the "cheapest".
> > Your process should now continue to monitor the state of interface 1,
> > and when it comes back up, you need to figure out how to "dismantle"
> > the second interface. It could be just as simple as swaping the metrics
> > so that interface 1 is now the "fastest" route.
> >
> > Like I said before, I'm not a networking expert, and I don't understand
> > all the dependancies of already open connections over the various
> > routes, but it seems like a pretty simple way to do things. OTOH, isn't
> > this essentially what RIP and gated would do for you? Inotice that
> > Fedora Core 2 has a "routed" package. Perhaps that has replaced
> > RIP/gated in todays world (my documentation is 10-14 years old)?
> >
> > Disclaimer: I don't use RIP or gated (anymore) I have a single default
> > interface (cable modem). The last I tried to use RIP/gated, I was on a
> > corperate network over a 9600 baud modem, and the "RIP storms"
> > eventually consumed the entire bandwidth of the modem rendering the
> > connection unusable.
> >
> >
> >
> > --
> > Kevin J. Cummings
> > kjchome@rcn.com
> > cummings@kjchome.homeip.net
> > cummings@kjc386.framingham.ma.us
> >
>
prev parent reply other threads:[~2004-10-11 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 18:26 SSL Certificate signing problem Tony Gogoi
2004-10-09 23:42 ` Adrian C.
2004-10-10 0:20 ` Kevin J. Cummings
2004-10-10 0:24 ` Adrian C.
2004-10-10 1:07 ` Kevin J. Cummings
2004-10-10 7:55 ` Adrian C.
2004-10-11 5:35 ` Adrian C. [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=60a746890410102235fa2198a@mail.gmail.com \
--to=drupix@gmail.com \
--cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).