Date: Thu, 19 Aug 93 04:30:06 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #213
To: tcp-group-digest
TCP-Group Digest Thu, 19 Aug 93 Volume 93 : Issue 213
Today's Topics:
56kb links - GRAPES mailing list
Interop
some WAMPES pointers
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Wed, 18 Aug 93 06:43 CDT
From: root@raider.raider.net (Mark J. Bailey [HOME])
Subject: 56kb links - GRAPES mailing list
To: tcp-group@ucsd.edu
Hello,
For more information on GRAPES, there is also an internet mailing list
run out on knuth.mtsu.edu. It is called GRAPES-L and many of the GRAPES
people attend. Send mail to 'listserv@knuth.mtsu.edu' with message bodies
of 'HELP' and 'INDEX' for listserv commands.
Mark
> Jack,
>
> You must have missed Huntsville... ;^) Lots of good information was
> presented there, the best source(s) for info would be the G.R.A.P.E.S.
> or ALANET groups, but I will try based on what I heard and as memory
> permits...
[stuff deleted]
> ******************************************************
> * 73 de Mike, N4CNW@W4DPH.#TPA.FL.USA.NA *
> * Amprnet: n4cnw@n4cnw.ampr.org [44.98.0.151] *
> * Internet: mike.murphree@stpete.honeywell.com *
> * -------------------------------------------------- *
> * "I'd rather have a bottle in front of me, *
> * than a frontal labotomy!" *
> ******************************************************
------------------------------
Date: Wed, 18 Aug 93 16:16:38 PDT
From: brian@nothing.ucsd.edu (Brian Kantor)
Subject: Interop
To: tcp-group@nothing.ucsd.edu
I'll be at INTEROP on Thurs 26th, and probably wandering aimlessly
around SF on the following Friday. Anyone care to do lunch?
- Brian
------------------------------
Date: Wed, 18 Aug 1993 11:30:37 -0700
From: Paul Traina <pst@cisco.com>
Subject: some WAMPES pointers
To: tcp-group@ucsd.edu
For those who have been worried about the security of WAMPES, or just
want a quick and easy guide to command differences, here's a start.
I've documented the command and system differences, but still TBD:
an english help file for the BBS (I'm about 2/3rds done)
real info on BBS forwarding
better documentation on SMTP client code for forwarding mail to AMPR TCP systems
a sane installation guide
What the hell, it's a start...
WAMPES command changes you should be aware of:
==============================================
attach:
ipip [<interface name> [{ip|udp} [protocol/port]]] (ipip ip 94)
Just like the 'encap' interface in NOS, but uses native UNIX
networking code to provide packet transport (this is how you
get your WAMPES system to act as a gateway betwen the Internet
and AMPRnet).
axip [<interface name> [{ip|udp} [protocol/port]]] (axip ip 93)
Attach an AX.25 over IP interface. This uses native
UNIX networking code instead of WAMPES.
axip
route {add|drop} <call> <host>
Set the AX.25 path to <call> to be via AXIP to <host>
bye
When controling net thorugh the 'cnet' program, causes
net to exit.
exit
Terminate the net program
domain
usegethostbyname (off)
Use the UNIX gethostbyname() call for all DNS translation
(let's you avoid dealing with the normal NOS based DNS)
escape (^C)
Set the escape character to switch back to command mode.
login
auto (on)
Attempt to auto-login without requesting username and
password. This is useful for simulating AX.25 BBS
connections.
create (on)
If a user does not have an /etc/passwd entry, create one
and allow them to log in. If disabled, users will not
get their own entry, but may login as 'defaultuser' if
defaultuser is set. Create will only create entries if
the callsign appears to be a valid ham callsign.
defaultuser (guest)
If a callsign is not available or not valid, the user may
be automaticly logged in under the default username. If
this parameter is unset, the user will be prompted for
a username and password.
logfiledir (disabled)
Log all information about a user to files in this directory
gid (400)
The UNIX group ID of newly created users
minuid (400)
The minimum UNIX user ID for newly created users
maxuid (32768)
The maximum UNIX user ID for newly created users
shell (/bin/sh)
The shell to be run for users who have been automaticly logged
in. For BBS operation, you may want to set this to /net/bbs.
homedir (/users/funk)
Automaticly created users have their home directory created in
a subdirectory of this prefix (e.g. /users/funk/kc6.../kc6tcn)
smtp
All of the 'server' stuff is gone since a WAMPES smtp
connection will go into sendmail, only SMTP client code
is present
Things to consider:
===================
Replace the pop2 daemon that comes with WAMPES with 'popper' available from
various sites around the internet, including:
Host ftp.uu.net
Location: /networking/mail/popper
FILE -rw-r--r-- 58961 Aug 31 1992 popper-1.831beta.tar.Z
BBS documentation (hah)
=======================
INFOFILE will be printed when the user types the 'info' command.
Infofile is (by default) /usr/local/lib/station.data (defined in bbs.h)
Command line options
--------------------
-d
debug (output goes to DEBUGDIR (defined in bbs.h)
-f <remote-bbs>
[must be root] forward all queued messages to remote BBS
-m
the BBS will accept a mail message or news article from
standard input and route it into the standard BBS mail or
bulletin system (this is so you can use the bbs as a
mail transport agent or a news batcher
-p
User is comming in from a DX packet cluster (?)
-w <time>
sleep <time> seconds... then proceed
BBS forwarding:
---------------
CONFIGFILE (/usr/local/bbs/config) contains information on remote BBS stations
to do bulletin/mail forwarding to.
Example:
w6yx w6yx-9
UNIX user id 'w6yx' is a BBS, when it logs in, flip into forwarding mode.
Connect to w6yx via AX.25 w6yx-9 for locally initiated forwarding.
Periodicly, the bbs program should be run as root to initiate BBS forwarding
to remote neighbors.
------------------------------
End of TCP-Group Digest V93 #213
******************************
******************************