From: nazareth@malibu.janet.ucla.edu (Sean F. Nazareth)
Newsgroups: rec.radio.amateur.packet
Subject: PA0GRI NOS QUESTION
Date: 8 Jan 93 23:48:33 GMT
Organization: University of California at Los Angeles, EE Dept.

Hi,

I recently downloaded a copy of PA0GRI NOS version 2.0l which the info command
dates as 920725.  I am trying to set it up such that I can have one computer 
physically connected to an ethernet network and also connected to a separate
computer using a serial SLIP line.

The idea is to be able to get the second computer, the one not connected to the
ethernet, to be able to send/receive mail, and have ftp/telnet services.  The
ethernet network is part of the larger Internet.

I have tried to set up the computers properly and have read the NOS operating
manual, the Getting Started with TCP/IP by Ackermann, and the Beginners Guide... by Gary Ford.  I have been able to connect the 2 pc's using the serial SLIP
connection, but I have failed trying to communicate with the internet.

I am including my AUTOEXEC.NOS file.  Please examine it and let me know anything that I may do to accomplish this goal.

Thanks in advance,

Sean 
nazareth@janet.ucla.edu


# AUTOEXEC.NET
# This is a sample autoexec file for GRINOS version N1BEE 0.72.
# It doesn't have all the fancy features one might hope for, but
# the basics are there, with some hopefully useful comments.
# Any line beginning with a "#" character is treated as a comment.  
# To uncomment a line, delete the # character

# NOS needs to know three things about you:  your hostname, 
# your  ham callsign, and your IP address.  By convention, the
# hostname # is your callsign in lower case, followed by ".ampr.org".
# The  callsign is generally used in upper case to distinguish it.
# The IP address comes from a local area coordinator.  Note that 
# there are a minimum of three places in this file where you need to
# insert your IP address -- here, in the ifconfig command, and at the
# end of each attach command.
hostname test8.icsl.ucla.edu.
ip address [128.97.90.158]

# This should match your IP address
ifconfig loopback ipaddress [128.97.90.158]

# PC setup
isat on
multitask on

# This makes short forms of the hostname work.
domain suffix icsl.ucla.edu.

# NOS needs to know how to convert hostnames to IP addresses.
# You can do this manually via the "DOMAIN.TXT" file, or you can 
# use a nameserver if one is available.  To enable the
# nameserver, uncomment this line and plug in its correct 
# address.
domain addserver [128.97.92.2]

# Some additional commands for the domain service.  Don't turn 
# translate on unless you have a small domain file and/or a fast machine.
domain verbose off
domain cache size 40
domain translate off

# To use POP, uncomment these lines.  Fill in "pop mailhost" with 
# the IP address of the station serving as your POP server.  Fill in the 
# "pop# mailbox" name with your hostname, i.e., your call.  The "pop 
# userdata" line needs to have your hostname, followed by a password
# (as negotiated with your mail server).  "pop timer" sets
# how often, in seconds, to query for mail.
#pop mailhost [44.xx.xx.xx]
#pop mailbox hostname
#pop userdata hostname password
#pop timer 1800


# Attach commands are complex; these are samples for COM 1
# and 2.  See Appendix C for details.  Uncomment the
# appropriate line(s) for your hardware.
# COM1 -- 256 byte MTU, 4800 baud serial link as ax0
attach asy 0x3f8 4 slip sl0 4096 1500 9600
attach packet 0x60 ec0 5 1500
#attach asy 0x3f8 4 slip sl0 2048 256 4800
# COM2 -- 256 byte MTU, 4800 baud serial link as ax1
#attach asy 0x2f8 3 ax25 ax1 2048 256 4800

# This is the basic route, sending everything out ax0 
route add default ec0 
route add 128.87.90.159 sl0

# These are tcp parameters you shouldn't need to mess with.
ip ttl 16
ip rtimer 240
tcp irtt 3000

# On a shared channel, you may want to change timertype to
# exponential; that's more courteous, but will slow your 
# retries down significantly.  mss and window should ordinarily be 
# the same value, equal to the largest mtu set in the attach
# command(s) above minus 40.  With the common mtu for 1200 baud
# channels of 256, that means both mss and window should be 216.
tcp timertype linear
# tcp bblimit 16
tcp mss 1460 
tcp window 2920

# These set up AX.25 parameters
ax25 digipeat off
ax25 maxframe 1
ax25 paclen 256
ax25 retry 20
ax25 window 4096
ax25 blimit 15
ax25 version 2

# as with tcp timertype, you may want to set this to 
# exponential on a shared channel.
ax25 timertype linear

# These are netrom setup commands.  Don't turn them on 
# unless you need them, and you know what you're doing.  You
# can really screw up the network by putting out netrom 
# broadcasts that don't fit with the configuration of the 
# "real" netrom nodes that can hear you.
#attach netrom
#netrom interface ax0 MYALIAS 192
#netrom obsotimer 1800
#netrom nodetimer 10800
#netrom verbose yes
#netrom bcnodes ax0
#netrom ttl 8


# These start the servers.
start smtp
start ftp
start echo
start discard
start telnet
start finger
start ax25

# Uncomment this line to enable logging.
#log \spool\net.log

# Default file type for ftp transfers.  Type image is for binary files; 
# type
# ascii is for text; it's safest to set the default to image.
# ftype image

# This makes telnet sessions to Unix systems work
# line-by-line, rather than character-by-character.
echo refuse

# Tell smtp how often to scan for outgoing mail
#smtp timer 600
#smtp batch on 

# GRINOS can send a string of commands to the TNC on startup.
# You could use this to force the TNC into KISS mode.  Note that
# you need to specify which interface to use.  This must be done
# <after>defining the interface, and <before>any data is sent to
# the TNC (for example, by the smtp and pop kick commands below).
# These commands will do that for a TNC2:
# comm ax0 "kiss on"
# comm ax0 "reset"

# kick the smtp and POP servers at startup.  Only uncomment the 
# "pop kick" line if you've defined a POP server above.
#smtp kick
#pop kick

# GRINOS (but not other versions) can define the function 
# keys with macros to make things a bit easier.  Here are a 
# couple of examples.  Note that each command must end with 
# a "\n" to signify a carriage return.  The numbers 
# represent the keys; 59 - 68 for F1- F10 (though F10 can't
# be redefined; it's always the escape key), 84 - 93 for 
# shiftF1 - shift F10, 94 - 103 for ctrlF1 - ctrlF10, 104 -
# 113 for altF1 - altF10.
# fkey 59 "tcp status\n"
# fkey 60 "mem status\n"
# fkey 61 "status\n"

# THE END