On Mon, 27 Sep 1999, Rajiv Ghai wrote: |To connect to my ISP I use the command ./ifup-ppp ifcfg-ppp0 & |The Linux box dials out, chat script executes and I get connected with |remote and local IP address allocated dynamically. I then deliberately do I don't know what all this command entails but it's not necessary to start a connection to install pppd for demand dialing. |nothing until the connection times out and disconnects after a few minutes. |At the prompt I then telnet any site on the internet and the dialer fires |up again, makes the connection again to my ISP. So demand dialing works fine. |My question is: Is this the normal way that demand dialing is supposed to |work ? It is not. You can install pppd for demand dialing without connecting. Again, something in the command above causes the connection to be made immediately. |Why cant I just telnet at the prompt to fire up the connection the first |time ? That's how it should work, after properly installing pppd for demand dialing. |The second option I mentioned is that I activate the PPP interface at boot |time (from selecting the relevant ppp settings in linuxconf). As the linux |box boots up the machine dials out and connects to the internet. I wait a |few minutes until the connection times out and try a telnet. It fires up |again. |It seems to me that for ppp demand dialing to work an initial connection |must be made to the ISP (or other ppp link) manually after booting the |system or automatically at bootup. Is this correct ? No, it's not correct. Something must request network access to a host that is not available locally before pppd will make a demand dial connection. |There is no LAN involved here. Just a standalone linux box at this time. |What I did notice in both cases is that after doing a dialout and timeout |the pppd daemon is still running when I check the process list using ps ax. |Is there a way to get the pppd daemon running in demand dialing mode at |boot up without actually dialing out ? I've attached a script that can do it when manually executed by root. All you need do is to change ttySx, xxx-xxxx, and abcdefgh appropriately and it should work. That is provided that you authenticate with CHAP, otherwise you'll have to adjust it for the authentication that you do use. The script should install pppd for demand dialing without causing an immediate connection. The same command can probably be inserted in a boot-up script and made to work there without much difficulty but I haven't done so. If you have a problem with attachments then let me know and I'll resend the script as a plain text email. |Has anyone else run into the same problem ?. I saw on the diald mailing If they use the same command you used above then they undoubtedly do have the same problem. |list that several people had this problem using diald but no one posted a |solution. Perhaps they just leave the machine on 24hrs a day so it doesnt |really matter wasting a few minutes of access time during bootup. I'm not qualified to address diald problems, but I doubt that diald has the problem when properly installed. --- Clifford Kite Not a guru. (tm)
#!/bin/sh exec /usr/sbin/pppd connect '/usr/sbin/chat -v ABORT "NO DIALTONE" \ ABORT BUSY ABORT "NO CARRIER" ABORT "PROTOCOL: NONE" \ "" ATZ OK\\r ATDT*70,xxx-xxxx CONNECT\\s \\c' \ /dev/ttySx 115200 lock debug kdebug 0 crtscts modem asyncmap 0 \ defaultroute mtu 552 noipdefault demand idle 60 ipcp-accept-local \ ipcp-accept-remote 192.168.0.1:192.168.0.2 name abcdefgh
