I'm slowly working my way towards a functional diald setup, and am
almost there. Right now, I am starting diald from my rc.local script
(i.e., I'm not using any of the rc.x startup scripts). This is done
after my LAN setup is accomplished in rc.sysinit.
Problem is, starting up diald appears to annihilate the routing table
set up during the ethernet configuration, and then wants to go dial up a
nameserver when you try to execute a 'route' command.
Here is my /etc/diald.conf file:
---------------------------
lock
mode ppp
connect /etc/diald/hex.chat.script
device /dev/cua1
speed 57600
modem
crtscts
local 192.168.0.1
remote 192.255.255.255
dynamic
defaultroute
include /usr/lib/diald/pyrite.filter
# Debugging info
accounting-log /var/log/diald.log
-----------------------------
The filter I'm using is a copy of standard.filter, with a probably lame
attempt to keep diald from trying to connect to 192.255.255.255 whenever
Netscape thinks localhost doesn't exist (such as when the httpd daemon
isn't up), or when one of the LAN hosts are down:
ignore tcp tcp.dest&255.0.0.0=192.0.0.0
ignore tcp tcp.dest&255.0.0.0=127.0.0.0
Any suggestions on the routing table problem?
--Brian
P.S. I just now see why diald tries to connect to 192.255.255.255,
that's my "dummy" remote IP address. I probably have to filter out the
"keyword.netscape.com" IP address Netscape tries to connect to when it
doesn' t know what else to do.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
