From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: two WANs one LAN
Date: Wed, 21 Apr 2004 03:25:48 +0000 [thread overview]
Message-ID: <4085E9BC.175B5B45@iswest.com> (raw)
In-Reply-To: <408528B9.3070209@edgeaccess.net>
Bob Beers wrote:
> Will it be the same when I introduce the dynamic ppp0 for IFE1?
> The IPE1 will be a NAT'd public IP, but the GWE1 will be
> the P-t-P link.
If you use the correct syntax, yes. Something like
ip addr add IP/MASK peer BROADCAST dev PPP0
substituting the point-to-point remote IP for BROADCAST and the correct
device for PPP0 (IIRC. Sorry, it has been a long time. Regardless, the
keyword here is "peer".)
> Also, what steps can be taken to expedite the detection and
> route adjustment?
Flush the cache. Again, IIRC
ip route flush
but a search of the archive will turn up the correct command. If you
can arrange it, a remote computer pinging each IP and messaging you when
the ping fails can be used to trigger the flush. Otherwise, "ping -c 1
-I PPP0 IP" (alternate between the devices for each ping) internally is
about the best you can do; ping NEVER failed for me (see below) but
YMMV.
> Is it enough to decrease the sleep time in the ping_daemon?
No help at all. AFAIC, less often is better, not worse.
> Are there some /proc/sys/.../whatever that can/should be tweaked?
Nope. And nothing anywhere else, either. DGD is _very_ hard because
usually the next hop is OK, it is the one after it that is bad. I don't
think that even Julian can deal with "next in the route is OK but his
peer is dead". In my case, the net card could speak just fine to the
DSL router; it was the modem (router) that could not I/O because it was
dead. Of course, DGD knew the modem was OK so it thought the link was
alive...
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-04-21 3:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 13:42 [LARTC] Re: two WANs one LAN Bob Beers
2004-04-21 3:25 ` 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=4085E9BC.175B5B45@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.