June 7, 1991





                           - 25 -


3.42.3.2.6.  ppp <iface> lcp local mru [ <size>  |  allow  [on  |
off] ]

Display or set the Maximum Receive Unit.  The default is 1500.

3.42.3.2.7.  ppp <iface> lcp local default

Reset the options to their default values.

3.42.3.3.  ppp <iface> lcp listen

Wait for the physical layer to come up, then wait for  configura-
tion negotiation from the remote.  The open command is preferred.

3.42.3.4.  ppp <iface> lcp open

Wait for the physical layer to come up, then initiate  configura-
tion negotiation.

3.42.3.5.  ppp <iface> lcp remote ...

These commands control the configuration of the  remote  side  of
the  link.  The options are identical to those of the local side.
If an option  is  specified,  the  parameters  will  be  used  in
responses  to the remote's configuration requests.  If not speci-
fied, that option will be accepted if it is allowed.

For each of these options, the allow parameter  will  permit  the
remote  to  specify  that option in its request.  By default, all
options are allowed.

3.42.3.6.  ppp <iface> lcp timeout [<seconds>]

Display or set the interval to wait between configuration or ter-
mination attempts.  The default is 3 seconds.

3.42.3.7.  ppp <iface> lcp try ...

These commands are used for the various counters.

3.42.3.7.1.  ppp <iface> lcp try configure [<count>]

Display or set the number of configuration  requests  sent.   The
default is 20.

3.42.3.7.2.  ppp <iface> lcp try failure [<count>]

Display or set the number of bad configuration  requests  allowed
from the remote.  The default is 10.

3.42.3.7.3.  ppp <iface> lcp try terminate [<count>]

Display or set the number of  termination  requests  sent  before
shutdown.  The default is 2.



                        June 7, 1991





                           - 26 -


3.42.4.  ppp <iface> ipcp ...

These commands are used for the IPCP [Internet  Protocol  Control
Protocol] configuration.

The close, listen, open, timeout and try sub-commands are identi-
cal to the LCP (described above).

3.42.4.1.  ppp <iface> ipcp local ...

These commands control the configuration of the local side of the
link.   If an option is specified, the parameters will be used as
the initial values in configuration requests.  If not  specified,
that option will not be requested.

For each of these options, the allow parameter  will  permit  the
remote  to  include  that  option  in its response, even when the
option is not included in the request.  By default,  all  options
are allowed.

3.42.4.1.1.  ppp <iface> ipcp local address [  <hostid>  |  allow
[on | off] ]

Display or set the local address for negotiation purposes.  If an
address of 0 is specified, the other side of the link will supply
the address.  By default, no addresses are negotiated.

3.42.4.1.2.  ppp  <iface>  ipcp  local  compress  [  tcp  <slots>
[<flag>] | none | allow [on | off] ]

Display or set the compression protocol.  The default is none.

The tcp <slots> specifies the  number  of  "conversation"  slots,
which must be 1 to 255.  (This may be limited at compilation time
to a smaller number.) A good choice is in the range 4 to 16.

The tcp <flag> is 0 (don't compress the slot number) or 1 (OK  to
compress  the  slot  number).   KA9Q  can  handle compressed slot
numbers, so the default is 1.

3.42.4.2.  ppp <iface> ipcp remote ...

These commands control the configuration of the  remote  side  of
the  link.  The options are identical to those of the local side.
If an option  is  specified,  the  parameters  will  be  used  in
responses  to the remote's configuration requests.  If not speci-
fied, that option will be accepted if it is allowed.

For each of these options, the allow parameter  will  permit  the
remote  to  specify  that option in its request.  By default, all
options are allowed.






                        June 7, 1991





                           - 27 -


3.42.4.3.  ppp <iface> ipcp pool [<ip-address> [<count>]]

Specify a pool of addresses to be assigned to the  <iface>.   The
<count> is the number of addresses in the pool; the default is 1.

The addresses will be used in rotation.   Overlapping  series  of
addresses may be assigned to more than one <iface>, and conflicts
will be resolved.

3.42.5.  ppp <iface> pap ...

These commands are used for the PAP [Password Authentication Pro-
tocol] configuration.

The timeout  and  try  sub-commands  are  identical  to  the  LCP
(described above).  However, the terminate counter is unused.

3.42.5.1.  ppp <iface> pap user [ <username> [<password>] ]

Display or set the username (the password may  be  set,  but  not
displayed).   When  the username is specified, but no password is
supplied, the ftpusers file is searched for the password.  When a
username/password  is  unknown or rejected, a session will appear
at the console to prompt for a new username/password.

3.42.6.  ppp <iface> trace [<flags>]

Display or set the flags that control the logging of  information
during PPP link configuration.

The flag value is 0 for none, 1 for basic,  and  2  for  general.
Values greater than 2 are usually not compiled, and are described
in the appropriate source files where they are defined.

3.43.  ps

Display all current processes in the system. The  fields  are  as
follows:

PID - Process ID (the address of the process descriptor).

SP - The current value of the process stack pointer.

stksize - The size of the stack allocated to the process.

maxstk - The apparent peak stack  utilization  of  this  process.
This  is  done  in  a  somewhat heuristic fashion, so the numbers
should be treated as  approximate.  If  this  number  reaches  or
exceeds  the  stksize  figure,  the  system  is almost certain to
crash; the net.exe program should be recompiled to give the  pro-
cess a larger allocation when it is started.

event - The event this task is waiting for, if it  is  not  runn-
able.



                        June 7, 1991





                           - 28 -


fl -  Process  status  flags.  There  are  three:  I  (Interrupts
enabled),  W (Waiting for event) and S (Suspended). The I flag is
set whenever a task has executed a pwait() call (wait for  event)
without first disabling hardware interrupts. Only tasks that wait
for hardware interrupt events will turn off this  flag;  this  is
done to avoid critical sections and missed interrupts. The W flag
indicates that the process is waiting for  an  event;  the  event
column will be non-blank. Note that although there may be several
runnable processes at any time (shown in the ps listing as  those
without  the W flag and with blank event fields) only one process
is actually running at any one instant  (The  Refrigerator  Light
Effect  says  that  the ps command is always the one running when
this display is generated.)

3.44.  pwd [<dirname>]

An alias for the cd command.

3.45.  record [off | <filename>]

Append to filename all data  received  on  the  current  session.
Data  sent  on  the current session is also written into the file
except for Telnet sessions in  remote  echo  mode.   The  command
record off stops recording and closes the file.

3.46.  remote [-p <port>] [-k  <key>]  [-a  <kickaddr>]  <hostid>
exit | reset | kick

Send a UDP packet to the specified host commanding it to exit the
net.exe  program,  reset the processor, or force a retransmission
on TCP connections.  For this command to be accepted, the  remote
system  must  be  running  the  remote server and the port number
specified in the remote command must match the port number  given
when  the  server  was started on the remote system.  If the port
numbers do not match, or if the remote server is not  running  on
the  target  system,  the command packet is ignored.  Even if the
command is accepted there is no acknowledgement.

The kick command forces a retransmission timeout on all TCP  con-
nections that the remote node may have with the local node.  If a
connection is idle, a current ACK packet (without data) is  sent.
If  the  -a option is used, connections to the specified host are
kicked instead. No key is required for the kick subcommand.

The exit and reset subcommands are mainly useful  for  restarting
the  net.exe program on a remote unattended system after the con-
figuration file has  been  updated.   The  remote  system  should
invoke the net.exe program automatically upon booting, preferably
in an infinite loop.  For example, under  MS-DOS  the  boot  disk
should contain the following in autoexec.net:

        :loop
        net
        goto :loop



                        June 7, 1991





                           - 29 -


3.47.  remote -s <key>

The exit and reset subcommands of remote require a password.  The
password  is  set on a given system with the -s option, and it is
specified in a command to a remote system with the -k option.  If
no  password  is  set with the -s option, then the exit and reset
subcommands are disabled.

Note that remote is an experimental feature in NOS; it is not yet
supported by any other TCP/IP implementation.

3.48.  rename <oldfilename> <newfilename>

Rename oldfilename to newfilename.

3.49.  reset [<session>]

Reset the specified session; if no argument is given,  reset  the
current  session.  This command should be used with caution since
it does not reliably inform the remote end that the connection no
longer  exists.   (In TCP a reset (RST) message will be automati-
cally generated should the remote TCP send anything after a local
reset  has been done.  In AX.25 the DM message performs a similar
role.  Both are used to get rid of a lingering half-open  connec-
tion after a remote system has crashed.)

3.50.  rip ...

These commands are used for the RIP service.

3.50.1.  rip accept <gateway>

Remove the specified gateway from the RIP filter table,  allowing
future broadcasts from that gateway to be accepted.

3.50.2.  rip add <hostid> <seconds> [<flags>]

Add an entry to the RIP broadcast table.  The  IP  routing  table
will be sent to hostid every interval seconds. If flags is speci-
fied as 1, then "split horizon" processing will be performed  for
this  destination. That is, any IP routing table entries pointing
to the interface that will be used to send this  update  will  be
removed  from  the  update.   If  split horizon processing is not
specified, then all routing table  entries  except  those  marked
"private"  will  be  sent  in  each update.  (Private entries are
never sent in RIP packets).

Triggered updates are always done. That is,  any  change  in  the
routing  table  that causes a previously reachable destination to
become unreachable will trigger an  update  that  advertises  the
destination with metric 15, defined to mean "infinity".

Note that for RIP packets to be  sent  properly  to  a  broadcast
address,  there  must  exist  correct  IP  routing  and ARP table



                        June 7, 1991





                           - 30 -


entries that will first steer the broadcast to the correct inter-
face  and  then place the correct link-level broadcast address in
the link-level destination field.  If  a  standard  IP  broadcast
address  convention  is  used  (eg. 128.96.0.0 or 128.96.255.255)
then chances are you already have the necessary IP routing  table
entry,  but  unusual  subnet  or  cluster-addressed  networks may
require special attention.  However, an arp add command  will  be
required  to translate this address to the appropriate link level
broadcast address.  For example,


arp add 128.96.0.0 ethernet ff:ff:ff:ff:ff:ff


for an Ethernet network, and


arp add 44.255.255.255 ax25 qst-0


for an AX25 packet radio channel.

3.50.3.  rip drop <dest>

Remove an entry from the RIP broadcast table.

3.50.4.  rip merge [on | off]

This flag controls  an  experimental  feature  for  consolidating
redundant  entries  in  the IP routing table. When rip merging is
enabled, the table is scanned after processing each  RIP  update.
An entry is considered redundant if the target(s) it covers would
be routed identically by a less "specific" entry already  in  the
table.  That is, the target address(es) specified by the entry in
question must  also  match  the  target  addresses  of  the  less
specific  entry  and the two entries must have the same interface
and gateway fields. For example, if the routing table contains


Dest            Len Interface    Gateway          Metric  P Timer  Use
1.2.3.4         32  ethernet0    128.96.1.2       1       0 0      0
1.2.3           24  ethernet0    128.96.1.2       1       0 0      0


then the first entry would be deleted as redundant since  packets
sent  to  1.2.3.4  will  still  be routed correctly by the second
entry. Note that the relative metrics of the entries are ignored.

3.50.5.  rip refuse <gateway>

Refuse to accept RIP updates fr