With all the wondeful help I've received on this list, I am now almost
there. Unfortunately, almost is not quite!
I have a mixed network environment containing a linux client, a linux server
(running Samba, ip_masq, ipchains) and two win98 machines. I am running
named on my server and my win98 machines and my linux client using that
machines nameserver. Using the various suggestions, I have cut down on almost
all unnecessary dialings from diald.
Two problems:
1) When my win98 systems boot, or when I play with network neighborhood,
diald gets a packet like this:
Nov 22 17:33:52 firewall diald[1180]: Trigger: udp 192.168.0.100/1027
207.198.253.36/53
The 192.168.0.100 address is the "dummy" address I use for diald. The
207.198.253.36 is my ISP nameserver address. Since the linux server is
the only box that knows that address, I cannot blame this on win98
stupidities. Why is the linux server (which happens to also host diald)
trying to talk to my ISP's nameserver? Yes, my named.conf has the
'forward only' option.
2) When diald is triggered, I see the following:
Nov 22 17:33:52 firewall diald[1180]: Calling site 192.168.0.101
Nov 22 17:33:53 firewall chat[1699]: Can't get terminal parameters: Invalid argument
Nov 22 17:33:53 firewall diald[1180]: Connect script failed.
N
This all used to work. When setting things up on this new server, I
switched to tap0 instead of slip. Could this be the cause? Even while I
have this problem, I can 'ifup ppp0' and it all works fine.
TIA!
--
Jake Colman
Principia Partners LLC Phone: (201) 946-0300
Harborside Financial Center Fax: (201) 946-0320
902 Plaza II Beeper: (800) 505-2795
Jersey City, NJ 07311 E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
web: http://www.ppllc.com
"Every time I think I've idiot-proofed something someone comes up with a
better idiot"
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
