2
0
Fork 0
A manager for on-demand network links
Go to file
2003-05-10 22:28:41 +00:00
bin Wrong type for variable used for return value of time() 2001-09-10 09:30:07 +00:00
config Put the modem dialler under the devices directory where 2002-04-30 17:47:19 +00:00
contrib Reduce the sensitivity to whitespace in time stamps. 2000-01-18 09:45:35 +00:00
doc Removed references to default fifo - there is no default now. 2001-08-20 13:32:29 +00:00
lib Merge of local changes branched off DIALD0_16_5 before I 1998-11-28 21:26:36 +00:00
patches Initial revision 1998-07-15 19:02:01 +00:00
setup Reorganised example setup and install it. 2001-07-10 14:33:29 +00:00
access.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
access.h Added comments :-). 1999-01-20 20:31:05 +00:00
buffer.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
bufio.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
bufio.h Updated copyright headers. 1999-03-21 15:07:26 +00:00
BUGS Changed references to mailing list archives. 1999-07-08 21:48:38 +00:00
CHANGES Compile TUN support if configure can find linux/if_tun.h 2002-05-29 09:49:40 +00:00
config.h.in Add missing entry for tun header. 2003-05-10 22:28:41 +00:00
configure Compile TUN support if configure can find linux/if_tun.h 2002-05-29 09:49:40 +00:00
configure.in Compile TUN support if configure can find linux/if_tun.h 2002-05-29 09:49:40 +00:00
dev.c Moved the check for a local address to just after the check to 2001-06-27 13:35:16 +00:00
diald.c Dammit! Newer glibc defines CLK_TCK to be a sysconf call 2002-05-09 20:57:15 +00:00
diald.h Refix the time.h includes :-(. 2002-02-17 23:08:10 +00:00
diald.spec Use rpm macros for pathnames where suitable ones exist 2002-05-09 21:37:22 +00:00
filter.c Major rewrite of packet handling code and related config options 2001-06-19 12:08:35 +00:00
firewall.c The latest ANSI C, and thus gcc3, require that labels always 2002-04-24 11:08:25 +00:00
firewall.h Timeouts now take an optional colon followed by a second 2001-06-25 15:09:22 +00:00
fixwrappers Check exit status of fixwrappers. 1999-09-20 19:12:22 +00:00
fsm.c Use ip to set and remove addresses if we have it and specify the 2001-06-19 17:39:18 +00:00
fsm.h Updated copyright headers. 1999-03-21 15:07:26 +00:00
install-sh Changed to use GNU autoconf. 2001-06-16 11:16:04 +00:00
LICENSE Documentation and version updates ready for 1.0 release. 2001-06-15 15:38:20 +00:00
lock.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
log.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
Makefile.in Use $(sysconfdir) rather than hardcoding /etc 2002-05-09 21:12:15 +00:00
modem.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
netlink.h Use a local netlink.h so we can, hopefully, compile with any 1999-08-31 20:52:12 +00:00
NOTES Merge of local changes branched off DIALD0_16_5 before I 1998-11-28 21:26:36 +00:00
NOTES.budget Major rewrite of packet handling code and related config options 2001-06-19 12:08:35 +00:00
options.c Use ip to set and remove addresses if we have it and specify the 2001-06-19 17:39:18 +00:00
parse.c Timeouts now take an optional colon followed by a second 2001-06-25 15:09:22 +00:00
ppp.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
proxy.c Compile TUN support if configure can find linux/if_tun.h 2002-05-29 09:49:40 +00:00
proxy.h send_packet returns an error status. 1999-10-06 22:04:55 +00:00
proxy_dev.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
proxy_slip.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
proxy_tap.c More include changes. Definitely the last. Honest! 2001-06-16 20:12:45 +00:00
proxy_tun.c Compile TUN support if configure can find linux/if_tun.h 2002-05-29 09:49:40 +00:00
proxyarp.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
README Major rewrite of packet handling code and related config options 2001-06-19 12:08:35 +00:00
README.ethertap Basic explanation of how to set up ethertap interfaces. 1999-03-17 21:21:08 +00:00
README.masq Hints on using masquerading and dynamic addrs. 1999-02-21 12:39:48 +00:00
README.pam Added PAM authentication method on TCP monitor connections. 1999-10-11 21:29:41 +00:00
README.tun Documentation for TUN/TAP 2003-05-10 22:21:45 +00:00
route.c Use ip to set and remove addresses if we have it and specify the 2001-06-19 17:39:18 +00:00
shell.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
slip.c Always include config.h explicitly before anything else. 2001-06-16 19:51:39 +00:00
THANKS Merge of local changes branched off DIALD0_16_5 before I 1998-11-28 21:26:36 +00:00
timer.c Get the correct clocks per second value for the return from 2001-08-20 13:47:18 +00:00
timer.h Merge of local changes branched off DIALD0_16_5 before I 1998-11-28 21:26:36 +00:00
TODO Added note about flush_timeout_queue. 2002-02-17 22:37:46 +00:00
TODO.budget More TODO 1999-02-14 22:47:58 +00:00
utils.c Use getprotoent() and getservent() to read protocol and 2002-02-17 23:01:23 +00:00

The Diald README File

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

This is release 2.0 of diald.

Diald is a daemon that provides on demand IP links via SLIP or PPP. 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.

Getting Diald

The file is called diald-2.0.tar.gz. It can be obtained from the diald
project on "http://sourceforge.net/". Note that the diald home page has
moved from its old locations of "http://diald.unix.ch" and
"http://www.loonie.net/~erics/diald.html". It can now be found at
"http://diald.sourceforge.net".

Mailing List

There is a mailing for the discussion of diald at vger.kernel.org. Send
mail containing the line "subscribe linux-diald" in the BODY of the message
to Majordomo@vger.kernel.org to join the list. Send mail with the word "help"
in the body to get help on the correct use of the Majordomo list server.
Announcements of new releases are made on the mailing list, and
its a good place to ask questions of users who already have diald up and
running. I would prefer the mailing list to be my primary channel of
communication with users. This gives you the added benefit of asking your
questions of everyone on the list, many of whom may have the same question,
or some of who may have already solved your problem. This minimizes the time
I have to spend answering questions about diald, and gives me more time to
spend improving the program. Let me repeat that. Please, if at all possible,
use the mailing list to ask questions! I read the list every day, sometimes
more than once, and your question will not be answered any more quickly if
it is sent directly to me, in fact, if I don't see the answer to your
question right away, then it may just get filed until I have time to deal
with it. Someone on the mailing list will probably be able to suggest a
solution to your problem well before that.

The mailing list is, or was, being archived by the Mailing List
Archives at "http://www.geocrawler.com" (along with a whole load of others).

FAQ

There is a copy of the FAQ distributed with the diald release in the
subdirectory "doc". This is the version that was current when the diald
release was packaged.

Before Installation

You must have ethertap or SLIP devices in your kernel in order to use diald,
EVEN IF YOU PLAN TO USE ONLY PPP CONNECTIONS! Let me repeat that, diald
needs ethertap or SLIP to work under all circumstances. It creates a proxy
interface that stands in for the real connection. Naturally, if you plan on
using diald to establish PPP connections, you must also have PPP devices in
your kernel. You must also have a program like "chat" to do dialing.

Configuring Diald

Run the ./configure script. By default configure will set diald up
to live under /usr/local. For a live installation you probably
want to use:

	./configure --prefix=/usr --sysconfdir=/etc \
		--localstatedir=/var --mandir=%{_mandir}

Basic Installation (First Time Users)

First run "make" then "make install" as root. This makes the diald daemon
and installs it. After installation you need to write an /etc/diald.conf
file to be able to use diald. Read the manual page to find out what this
file can contain. The diald-examples manual page gives several
example diald.conf files.

Installation If You Are Already Using an Earlier Version

Unlike previous releases of diald, the basic installation procedure no
longer installs an /etc/diald.conf file. Therefore, you can follow the same
installation procedure as for first time users (above). The set of standard
filters rules is now located in "/usr/lib/diald/standard.filter". This used
to be installed as /etc/diald.conf. If you want, you can now include this
file into your /etc/diald.conf file with the new "include" directive. If you
wish to change the rules in this file you should just copy them into another
file and edit them as desired. You can either place rules directly in
/etc/diald.conf, or put then in another file that is included by
/etc/diald.conf. In any case, the syntax of the filter rules has not changed
between diald 0.14 and diald 0.15, so you should be able to continue using
your old /etc/diald.conf file. If you want to use a particuarly old
/etc/diald.conf file you may need to update some of the contents as the
names and meanings of various commands have evolved a little over time. In
particular a major change in syntax took place between version 0.3 and 0.4
and a change in semantics took place between version 0.7 and 0.8 and again
between 0.10 and 0.11. See the CHANGES file for more information. If you are
planning to use diald with a kernel numbered 1.3.75 or greater, then you
MUST compile diald using the include files for that kernel.

Using Diald

There are several manual pages that cover the use of diald. The "diald"
manual page is the basic reference manual for diald. It will point you at
other relevant manual pages. Of particular interest will be the
"diald-examples" manual page, which will help you get diald configured. You
might also want to look at the contents of the "contrib" directory in this
distribution.

Bugs, Limitations and Warnings

There are some known problems and limitations.

Lines in options files can contain at most 1024 characters. Longer lines are
silently truncated.

If there are no filter rules specified then no packets will be matched and
the daemon won't do anything. It should probably match all packets by
default in this case.

Diald attempts to automatically adjust the MTU of the proxy to match the MTU
of the actual connection negotiated by ppp, but this is not guaranteed to
work, since changing the MTU on an active interface is not supported by the
kernel. It is possible that an auto adjusted MTU will cause some long
packets to get dropped on the floor. If you are having problems you should
match these values manually. Diald will report the negotiated MTU in the
system logs and warn you that you should adjust the settings.

The monitor command represents a security risk as anyone who has access to a
diald control fifo can ask diald to write to any named pipe in the system.
Be careful with the permissions on your fifo's.

Please send bug reports, patches or suggestions for improvements to me,
preferably via the mailing list.

Mike Jagdis
jaggy@purplet.demon.co.uk

and previously,

Eric Schenk
Eric.Schenk@dna.lth.se

Lund, Sweden, January 28th, 1997.