On Tuesday, June 15, 1999 8:46 AM, kidlinux [SMTP:[EMAIL PROTECTED]] wrote: > > Demand dialing (with pppd, I assume) would work. However, unless you've got a > static IP, it may not be any easier to set up than diald. The pppd man file > says > > "... the use of demand dialling with peers that do dynamic IP address > assignment is not recommended." > > I've spoken to someone who claims to have done it, and I tried it because diald > sounded difficult to setup with IP Masquerading. Once I read that line in the > pppd man file, I went back to diald and found it easy to setup with my masq'd > machines (all I had to do was add hostnames in /etc/hosts on each box and make > a small /etc/diald.conf file). > I'm using pppd demand mode at the moment without any problem (that I'm aware of). I was using diald 0.16.5 with a 2.0 kernel. I upgraded to a 2.2 kernel and wanted to go to diald 0.99, but found the lack of clear documentation, and the troubles people on this list have reported, too daunting. Diald 0.99 is a nice program, but will only become a nice product when there are clear instructions for setting it up, that can be followed by someone who is not already an expert. This is what I am doing. Comment/criticism is welcome. I start pppd at boot-time (in rc.local) using a script that just runs this command: /usr/sbin/pppd /dev/modem 115200 connect /usr/local/lib/connect crtscts defaultroute demand \ holdoff 30 idle 600 :203.110.25.2 ipcp-accept-local ipcp-accept-remote This disconnects after 600 seconds of inactivity, and waits 30 secs before redialing after a failure. An external ip address ( any valid address will do ) has to be given, but is automatically replaced when the real dynamically assigned address is known. I use pap, so the ppp-options file just contains: lock name bboutel and pap-secrets has the login name and password. The connect script is a simple initialise modem and dial affair, taken from an example in the diald package, and cut off after connecting because authentication is done with pap. Masquerading is unchanged from the earlier version, except that ipfwadm is replaced by ipchains. I haven't done the conversion properly yet, and am using ipfwadm-wrapper with the old ipfwadm command arguments. The main complication is that pppd is running all the time, so the existence of its pid can't be used to test if the link is up. (I have some cron programs, for example fetchmail, which I want to run frequently when the link is up, but less frequently if the link is down and would have to be brought up specially.) I solved this by getting ip-up to create a file in /var/run and ip-down to remove it, so any task that needs to test the link can check for that file. --brian Brian Boutel Phone +64 4 9386709 Fax +64 4 9386710 Mobile 021 410142 [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
