I want to thank all those who took time to post replies to my request for help with a PPPD problem! Many, many thanks! I have PPPD 2.3.7 working with a 2.0.30 kernel. This was the first time EVER I have had to post a request for assistance, and I have to say I am impressed with the quality and the gentle tone of writing that I found in correspondence with everyone in 'linux-ppp'. I hope that in the future, as I become more proficient and familiar with Linux and its components, I can return the enthusastic help that I have experienced back to members of the Linux community. regards, Allan.
On Thu, 3 Jun 1999, Allan Jones wrote: > here's what I've been trying, and I've examined the /usr/adm/messages > file for clues, to no avail: > > #/usr/sbin/pppd /dev/ttyS2 57600 debug kdebug 7 \ > connect '/usr/sbin/chat -v -f /etc/ppp/chatscript' \ > ipcp-accept-local ipcp-accept-remote 192.168.0.1:192.168:0.1 \ > demand > ^^^^^^ > | > +-----------When I add the "demand" flag, nothing happens. The debug > info looks like the dialing process stops at opening the > /etc/ppp/chatscript file. However, when I remove the "demand" option, I > connect with no problems to my ISP... > > > Ummm, to those who have demand-dialing working, what kernel version > and with what version of PPP are you using? > Allan, I have successfully used kernel v2.0.35 and 2.2.5 (with Alan Cox's patches) with various versions of pppd up to pppd 2.3.7. My only suggestion would be to change your invocation method to use the peers option that pppd supports. ie. if pppd is installed in /etc/ppp then you can setup a subdirectory called peers and create a file that contains the pppd setup options relevant for the particular connection. eg. create a file /etc/ppp/peers/ispname. In the ispname file enter the options such as demand, nopersist, ipcp ... Then when you start pppd you type pppd call peer_file_name_of_choice. eg pppd call ispname. an example from my setup (where I have a dedicated local IP address) follows. ttyS1 # modem is connected to /dev/ttyS1 115200 # run the serial port at 115200 modem # device is a modem crtscts # use hardware flow control noauth # don't require the host to authenticate itself defaultroute # set defaultroute to ISP A.B.C.D:E.F.G.H # local IP:remote IP #noipdefault # no default IP address demand # use demand mode persist # don't keep line up all the time idle 90 # disconnect line after 90 seconds lock # create lock file #maxconnect 3000 # 50 min maximum connect time #debug name isp_username # set name of user for the ISP remotename ispname # set name of ISP (I use this to allow the # connection to occur and use the pap-secrets file) connect '/usr/sbin/chat -f /etc/ppp/ispname_chat_script' pppd will then start up and establish an pppX interface (where X is the next available ppp interface number) BUT it will not actually dial-up and establish the connection till it receives a packet which is not destined for the local network. pppd then dials the number and actually establishes the ppp connection. You can also specifiy an idle time so that pppd will kill the connection (although still leaving the pppX interface so that it can dial again in the future - the persist option). Unfortunately my other config file, where I am allocated a dynamic ip address each time the pppd connection occurs, is at home and I can't exactly remember the details. It is very similar but you would use the ipcp-accept... options mentioned in earlier posts. If I can be of any further assistance, please contact me. Regards Paul +++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++ EML (CHEM) Pty Ltd Telephone: +61 3 9836 1999 425-427 Canterbury Road Facsimile: +61 3 9836 0517 SURREY HILLS, VICTORIA 3127 Email: [EMAIL PROTECTED] +++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++---+++
