Hi,
It sounds to me like you have some service attempting to link to an outside
host by (most probably) first doing a DNS query, do you have diald-top???
you could use this (or dialmon) to see what packets are being routed.
When you work out what host is trying to be contacted then you can either
add it to your hosts file or disable it altogether.
At 05:15 2/02/99 +0000, you wrote:
>Still can't diald to behave the way I think it should.
>
>I'm running RH5.2. IP masquerading and diald 0.16 rev something
>installed.
>
>In /etc/rc.d/init.d the files diald and diald.init exist
>I added a line in /etc/rc.d/rc.local
> /usr/sbin/diald
>
>but when I rebooted diald started dialing the modem immediately. This
>is not the behavior that I think I should have - namely, that diald will
>fire up the modem when I try to ping outside my own 192.168.14.xxx home
>network and not at boot.
>
>The only thing that I can fingure out is that I should make a link to
>diald.init in the /etc/rc.d/init.d directory but I'm just not good
>enough at scripting to figure each line of diald.init out.
>
>Any ideas??
>
>Thanks for the time,
>
>
>Bob
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-diald" in
>the body of a message to [EMAIL PROTECTED]
>
>
Sid Young
=======================================================
Linux!, because reboots are only for *kernel* upgrades!
=======================================================
http://www.synaptic.com.au
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
