On Tuesday, September 21, 1999 8:34 PM, Hassan Aurag
[SMTP:[EMAIL PROTECTED]] wrote:
Hassan:
> I have used something like:
> ipup /etc/ppp/ip-up
> ipgoingdown /etc/ppp/ip-goindown
> ipdown /etc/ppp/ip-down
>
> ip-up and ip-down are RedHat 6.0's stock files. They call also their
> *.local equivalent in which i set up my network. Since my connection
> ip is not registered I use justlinux.com to register my dynamic ip.
> And then ipgoingdown deletes it ...
>
> What happens is that when I tail /var/log/messages it will complain
> when executing ip-up because it did not get its arguments.
>
> The usual RedHat netcfg way of doing this is by calling usernet
> which starts ppp0 and gives the returned 6 arguments back to ip-up.
It
> seems diald doesn't do that with the ipup option.
>
> Is there a way to correct that.
Maybe I'm wrong... but I believe that pppd, on RedHat, calls always
ip-up and ip-down, so it doesn't matter if it is called directly or by
diald, /etc/ppp/ip-up and /etc/ppp/ip-down always run. Just try it and
find out, if so don't need to set them on diald.conf, just set
ip-goingdown.
If I'm wrong I appologize.
> My second question is more related to diald itself. diald will work
> fine for hours but then it will start going nuts, like it would try
to
> start a connection and hangs there not doing anything! I don't know
> why yet, but did anyone experience such a thing?
No, not a clue without the syslog relevant parts. If it goes on just
add a cron job, say once in a while, to restart diald (better check if
the link is up and sleep for a while if so, if you don't want to break
a eventual connection when restarting).
---
Lazarus Long
<[EMAIL PROTECTED]>
PGP:
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x5C1DC205>
ICQ#: 30062012
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
