Steven T. Hatton wrote:
Kenneth,
I have something working now. I have learned that diald and chat are both four letter words. I have diald activating when I attempt to hit an outside site with something like a traceroute by name (I think that worked). I couldn't for the life of me figure out how to get the chat working on Earthlink/Sprint. I finally did this. BTW, I called sprint tech support and they did have minimal Linux support. They get a big ataboy from me for that. The guy didn't have all the answers I was looking for, but he did have a little script that helped.
Any how, I now have diald activating a ppp.chat script. Unfortunately it doesn't connect every time. It can take as many as five trys. The errors are different ever time it fails. I will look at this when I have had some sleep. What I did was to copy over the /usr/doc/packages/diald/config/diald.config and diald.defs to /etc I then added
-m ppp local 10.10.10.1 remote 10.10.10.10 dynamic connect /etc/ppp/ppp-up
to diald.conf.
I started the daemon like this: diald /dev/modem defaultroute
Thanks for your help,
Steve
I took the supplied sample diald.conf file from /usr/doc/packages/diald/config and added the following lines to the end of it. I works pretty reliably. Because all of the necessary arguments are in my systems's "/etc/diald.conf" file, I run diald with no runtime arguments at all. This stuff should be fairly boilerplate expect for the "ip-up" and "ip-down" stuff. I use diald on my gateway/firewall system for my home network and have some basic firewall and IP Masquerading stuff setup. fifo /var/run/diald.ctl mode ppp connect "/bin/sh /etc/ppp/connect" device /dev/ttyS1 speed 115200 modem lock crtscts local 127.0.0.2 remote 127.0.0.3 dynamic defaultroute retry-count 10 redial-timeout 15 first-packet-timeout 300 connect-timeout 120 two-way ip-up /etc/ppp/firewall.rules ip-down /etc/ppp/firewall.reset If you're having problems generally with the login stuff and you're using "chat" in your connect script, try running "chat" with the "-v" argument which causes verbose output to be sent to the "syslogd" process. You can look at the output in the /var/log/messages file. Tony -- Anthony.Schlemmer@gte.net - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e