
Internal CSNET (and MMDF) notes.

  Copyright (c) 1991 Bolt Beranek and Newman, Inc.
  All rights reserved.

  Redistribution and use in source and binary forms are permitted
  provided that: (1) source distributions retain this entire copyright
  notice and comment, and (2) distributions including binaries display
  the following acknowledgement:  ``This product includes software
  developed by Bolt Beranek and Newman, Inc. and CREN/CSNET'' in the
  documentation or other materials provided with the distribution and in
  all advertising materials mentioning features or use of this software.
  Neither the name of Bolt Beranek and Newman nor CREN/CSNET may be used
  to endorse or promote products derived from this software without
  specific prior written permission.

  THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
  WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

AT SYSTEM BOOT TIME
-------------------
	duattach /dev/dialup0
	ifconfig dua0 192.31.242.100  192.31.242.99
Possible errors:
	+ Are you root? Does the device /dev/dialup0 exist (built into the
	  kernel)?

DIALING OUT
-----------
	diald
Should be run from /etc/rc.local.  Possible errors:
	+ Modem is stuck, can't get it to dial.  Use tip(1) and try
	  to get the modem in command mode (e.g., AT commands).
	+ Baud rate problems; check the speed on the modem and in
	  the config file.
	+ Does /etc/diald.conf exist, readable by diald, and have
	  the right information?
	+ Are the referenced script files in /usr/dialupip/config?
	+ Is there a login and password on the remote machien?
	+ Is diald running under root?
	+ Does /usr/dialupip/log exist, and are the call.log and dial.log
	  writable by diald?

DIALING IN
----------
	dudisc_duXX
Most errors are written to stderr (which will go out to the remote site)
and dial.log.  In case of problems, try using tip to connect to the remote
site and log in as the script file dictates, noticing the output from
dudisc.  If everything works fine you should be disconnected shortly after
the login sequence and "connected" message.  Is the program setuid root?

	dulogin
Make sure the user is a member of the group "dialupip".  All errors
are written to stdout or stderr, so to debug it you will have to call
in and invoke the program via tip.

	dialmonitor
Make sure the host is using the nameserver and that there are PTR entries
for each IP address associated with a dialup interface.


ADDING A NEW DIALUP IP SITE
---------------------------
	1.  Decide which du interface to use for the site
	2.  Decide which IP address to use for the site, and give relay2
	    the odd address within the 192.31.242 network.
	3.  Add a PTR record for the site and its relay2 counterpart to
	    the named.dialup-rev.db database.
	4.  Create an account in /etc/passwd.  Choose any username and
	    password, put them in the "dialupip" group and make their
	    home directory be /usr/dialupip.  The shell should be
	    /usr/dialupip/bin/dudisc_duXX where XX is the interface assigned
	    in step 1.


ADDING A NEW SMTP/DIALUP IP SITE
--------------------------------

The following procedure allows a remote site to start up an SMTP deliver
on relay2 to themselves.  There are two methods for doing this.  One will
be to just rlogin or rsh in from the remote host.  The other will be to
deliver mail to a dummy user which will kick off the maildelivery.
	1.  Make sure the site has a Dialup IP account and is able to
	    connect and do a "ping"
	2.  Add a channel table for the site in
	    /mmdf/table/sitename_you_choose.  Map the host to the IP
	    address to be used to receive mail.  If this is not a
	    192.31.242. address, then you must verify routing.
	3.  Add a new channel to mmdftailor.ACTUAL on relay2:
	    a.  No "user" or "trn"
	    b.  "pgm=smtp"
	    c.  Choose, and remember, an appropriate name
	    d.  Host should have a dot style name
	    e.  "tbl=sitename_you_choose"
	    f.  Queue is the same as the phonenet queue
	4.  Add a new user for this site:
	    a.  Choose a name such as delisr, deltek, or delunlv and
		put them in group "dialupip"
	    b.  Create a home directory in /usr/dialme/deliver, use a name
		like tekdeliver or unlvdeliver.
	    c.  The login shell will be /usr/dialme/deliver/XXX/rundeliver,
		where XXX is the directory chosen in step 4b.
	    d.  Copy the files from /usr/dialme/deliver/generic into the home
		directory of the new user.
	    e.  Edit the .rhosts, .maildelivery, and rundeliver files:
		+   .rhosts should contain the name of their host,
		    such as tektronix.tek.com.
		+   .maildelivery  should kick off a deliver when mail is
		    received for the new user.
		+   .rundeliver will fire up deliver on the new channel,
		    and mail the results to the appropriate person.
