From: Paul Zirnik <tami@disconnected.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] two routes, non-permanent higher proiority
Date: Thu, 12 Apr 2007 17:26:21 +0000 [thread overview]
Message-ID: <200704121926.21775.tami@disconnected.de> (raw)
In-Reply-To: <4f6ba3b0704110716k7b68f183h37f415ddefba3af0@mail.gmail.com>
On Thursday 12 April 2007 14:45, Bob Beers wrote:
> On 4/11/07, Randy Wallace <randywallacejr@gmail.com> wrote:
>
> Hi Randy, thanks for the reply,
> I'll leave it intact, but I have a few comments/questions at the end.
>
> > I would write a script that would check for connectivity to the
> > internet over the ethernet port for internet.
> >
> > If your slackware router is always connected, and communicating, with
> > the satellite modem, though not always passing real internet traffic,
> > you could leave the interface 'up'. From there, you could write a
> > simple ping-check type script that would ping the satellite gateway,
> > which would only be visible when the dish is communicating to the NOC.
> >
> > For example:
> >
> > if
> >
> > ping -I eth0 xx.xx.xx.xx
> >
> > is successful then
> >
> > ip route del default via xx.xx.xx.xx dev ppp0
> > ip route add default via xx.xx.xx.xx dev eth0
> >
> > else
> >
> > ip route del default via xx.xx.xx.xx dev eth0
> > ip route add default via xx.xx.xx.xx dev ppp0
> >
> > otherwise, if eth0 is not always talking to the modem (ethernet), then
> > you could use ethtool to check for ethernet connectivity before trying
> > to ping, i.e.
> >
> > if
> >
> > (ethtool eth0 | grep 'Link detected: ') = 'yes'
> >
> > then
> >
> > ip addr add xx.xx.xx.xx/xx brd + dev eth0
> >
> > and whatever routes you need to get the satellite gateway.
> > then run the ping script above.
> >
> > hope i helped a little,
> >
> > -Randy
>
> This is a good plan, and I'm doing something like this already,
> but I was really hoping that there was some static way to
> set up two default routes, maybe two route tables even,
> and that the kernel would be smart enough to know if the
> satellite route was reachable, and prefer it based on some
> priority or metric setting. I think the satellite modem may be
> powered even if the dish is stowed, so the ethtool check of
> "Link detected" may be always true, so not much help.
> I suppose maybe this is what the dynamic routing protocols
> (OSPF?, or BGP?) was designed to handle? But I suppose
> a script from a cronjob would adjust the routing with only
> a -- worst case -- 60 second delay.
You can setup two or more default routes, the kernel automaticaly switches
to the next defaultroute after a timeout.
The timeout can be set via /proc/sys/net/ipv4/inet_peer_gc_maxtime
To switch back to the first route IMHO simply flush the routing cache (not
tested)
regards,
Paul
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-04-12 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 14:16 [LARTC] two routes, non-permanent higher proiority Bob Beers
2007-04-12 3:34 ` Randy Wallace
2007-04-12 12:45 ` Bob Beers
2007-04-12 17:26 ` Paul Zirnik [this message]
2007-04-12 17:37 ` Paul Zirnik
2007-04-12 18:45 ` Bob Beers
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=200704121926.21775.tami@disconnected.de \
--to=tami@disconnected.de \
--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.