On Tue, 26 May 1998, Howard Arons wrote:
When I was using older versions of chat and pppd, I used the pppd option "nodetach" to keep pppd from becoming a background process, and the chat option "-vs" to direct all the output of chat to stderr. Then I could follow the progress of the dialup, and see when my dynamic IP address was assigned, confirming my connection.
With pppd and chat in SuSE 5.2 I can't get this scheme to work.
With '&' at the end of your 'pppd' call, it is detaching anyway. I have put at the end of my scripts: sleep 40 echo route -n 1>&2 A successful dial-up connection will then show up in your routing. You could also use 'ifconfig' instead of 'route' with the added bonus that it would tell you your dynamic IP assignment. I do that with other scripting, so for me that is unneccesary. I say I 'have' done this. But this is what I actually do: I have changed ISPs using different authentication protocols so often I have found it advisable to use the 'debug' option in 'pppd' and turn on debug logging in /etc/syslog.conf with: daemon.debug /etc/ppp/ppp_log Then I open the ppp_log with 'tail -f /etc/ppp/ppp_log in an xterm su'd to root. This way I see all the details of the login negotiation. As I have replaced SuSE-5.2 pppd with ppp-2.3.3 and use dial-on-demand to connect to the Internet, I find this a very reliable way of verifying that an Internet connection is actually established. 'ping' is also very useful for this. Note that when you change /etc/syslog.conf you have to restart 'syslogd' with: kill -HUP `cat /var/run/syslogd.pid` to get the changes to work. Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e