Bob,
On Wed, 29 Mar 2000, Bob Kruger wrote:
> >
> > > I know that I can write a batch script to check every 30 or so second to
> > > see if the a ppp0 connection is made, and if so, then if there is a
> > > gateway to the connection, and if not, reestablish it. I would rather
> > > have this done by pppd.
> >
> > See /etc/ppp/ip-up. It is called by pppd when the connection
> > comes up with the arguments:
> > ifname=$1 # interface name (e.g. ppp0)
> > ttydevice=$2 # device name (e.g. (/dev/ttyS0)
> > speed=$3 # speed (as reported by stty
> > localip=$4 # local (your) ip
> > remoteip=$5 # remote ip
> >
> > If you have multiple PPPs, it gets more complex, but in your
> > case, I'd just have the "route add [mumble]" in this file, and not even
> > check the args (you probably don't care).
>
> Thank you all for for answering. Your info on using ip-up is useful, but it does
> not address the problem.
>
> Perhaps I am not wording this properly. I have absolutely no problem making a
> connection with the server using pppd, and absolutely no problem with including
> the route command in the bash script I use to connect to the server to initially
> set the routing. The problem occurs if the connection is lost and pppd redials
> automatically.
>
> When dialing the server, one of my ppp options is "persist". This will force the
> system to redial if the connection is lost. Note - pppd never exits - it just
> redials. Unfortunately, the routing information IS lost, and I have to manualy
> reenter after the system has redialed on its own.
Hmm. Oh, well. I've never used the persist option, so I
didn't know this limitation. Not that it does you any good, but I'd
suggest that this is a bug in pppd, given the file name of "ip-up", and
all that it implies.
Would you be game for hacking pppd to change this behavior? If
not, I'd give it a whirl.
Danny
--
To unsubscribe: mail ">majordomo@ale.org with "unsubscribe ale" in message body.