diald 0.6 vs 0.7

diald 0.6 vs 0.7

Post by Dean Carpent » Fri, 16 Jun 1995 04:00:00



I can't seem to get diald 0.6 to use the local address I give it on
the command line ...  That is :

        diald .... local xx.xx.xx.xx remote yy.yy.yy.yy ....

It ignores the local IP I give it and insists on using the machines
actual IP address.  A workaround for this is to pass the IP address
pair to pppd with the -- parm at the end, as in :

        diald ..... -- xx.xx.xx.xx:yy.yy.yy.yy

I tried diald 0.7, but for some reason that just hangs up the modem
right after sending the login password.  I just grabbed pppd-2.1.2d
but haven't installed it yet - still at 2.1.2b.  Could either of these
problems be related to that ?

Dean

 
 
 

1. Release 0.7 of diald (a demand dialing daemon)

I am happy to to announce the release of version 0.7 of diald.
This is the seventh ALPHA release of this code. This release
introduces time restrictions on connections, several new
filtering rules for controlling connection uptime, as well
as a few bug fixes and other minor feature upgrades.

For those who do not already know, diald is a daemon that
does demand dialing for PPP and SLIP. The purpose of diald
is to make it transparently appear that you have a permanent connection
to a remote site. Diald sets up a "proxy" device which stands in for
the physical connection to a remote site. It then monitors the proxy,
waiting for packets to arrive. When interesting packets arrive
it will attempt to establish the physical link to the remote site
using either SLIP or PPP, and if it succeeds it will forward traffic
from the proxy to the physical link. As well, diald will monitor
traffic once the physical link is up, and when it has determined
that the link is idle, the remote connection is terminated. The
criteria for bringing the link up and taking it down are configurable
at run time, and are based upon the type of traffic passing over the link.

As I said before, this is still ALPHA code, your mileage may vary!
I'm using diald daily, and it works for me, but I can't anticipate
every software/hardware configuration out there. For reference,
I wrote and tested diald on a system running bleeding edge
Linux 1.1.*. Currently I'm up to Linux 1.2.0. I've tested diald
using both pppd-2.1.2b and pppd-940914 and it should work with either.
I've had reports that people cannot get it to work with 1.0.x series
kernels. If anyone does get it working with 1.0.x series kernels
I'd be interested to hear about it.

The file is diald-0.7.tar.gz. As usual I've uploaded it to
sunsite.unc.edu:/pub/Linux/Incoming. It should move to
sunsite.unc.edu:/pub/Linux/system/Network/serial after a suitable interval.

-- eric

---------------------------------------------------------------------------

Department of Computer Science, University of Toronto

--

PLEASE remember Keywords: and a short description of the software.

2. JOBS

3. diald (0.7) does not lock the modem

4. strange behaviour of dip-3.3.7-uri

5. Diald 0.6 troubleshooting (long)

6. Newbie interested in Linux

7. Release 0.6 of diald

8. Big (for me =) ) problem with PPP

9. RPM v3.0.6 vs. SuSE 7.3 Pro

10. Linux vs OS2 vs NT vs Win95 vs Multics vs PDP11 vs BSD geeks

11. wmf 0.7 - converting mails to html

12. linux kernel conf 0.7

13. PCSND 0.7 driver and Doom