Brian wrote:
>
> 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
I had a problem as you similarly describe it when I was using diald 0.14.
It looked like messing up the routing table, the same as annihilation?
After an upgrade to V. 0.16 this has gone by.
> set up during the ethernet configuration, and then wants to go dial up a
> nameserver when you try to execute a 'route' command.
That's normal. Try 'route -n' to prevent route from asking a nameserver but
shows the table with IP numbers only.
>
> 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
Be sure not to use an address that's already used in your LAN.
And I'm not quite sure whether it's a good idea to use a "mask address" like
192.255.255.255 for the remote address of the slip device where outgoing
requests are directed to until a dialup connection is established.
I for example set up
local 192.168.1.1
remote 192.168.1.2
I made the experience that it would be better here to use addresses from another
network (192.168.1.x) for diald since my Ethernet addresses are all in the
(192.168.0.x)-room
> dynamic
> defaultroute
> include /usr/lib/diald/pyrite.filter
>
> # Debugging info
> accounting-log /var/log/diald.log
>
[...]
> Any suggestions on the routing table problem?
I could only tell you these few things as I don't know anymore about this stuff,
but I hope this helps.
BTW: I have question too, please read below.
Regards
Thomas
>
> --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.
Is this the case when Netscape starts? In /var/log/messages I can always see the
accept rule for nameserver requests whenever I start Netscape, and, of course,
it's my ISP's nameserver as I don't use a local nameserver. How can I prevent
Netscape from sending an outgoing request at startup?
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
