ka9qnos.txt

uCLinux下的一个TCP/IP协议栈源码

                           - 13 -


Up to 7 optional digipeaters may be given; note that the word via
is  NOT  needed. If digipeaters are specified, they are automati-
cally added to the AX25 routing table as though  the  ax25  route
add command had been given before issuing the connect command.

3.13.  delete <filename>

Delete a filename in the current working directory.

3.14.  detach <iface>

Detach a previously attached interface from the  system.  All  IP
routing  table  entries  referring to this interface are deleted,
and forwarding references by any other interface to  this  inter-
face are removed.

3.15.  dialer <iface> [<dialer-file> [<seconds>  [<tests>  [<hos-
tid>]]]]

Setup an autodialer session  for  the  interface.   Whenever  the
interface  is  idle for the interval in <seconds>, the autodialer
will ping the <hostid>.  If there  is  no  answer  after  <tests>
attempts,  or  the  interface  is otherwise known to be down, the
autodialer will execute the special  commands  contained  in  the
<dialer-file>.

The <dialer-file> may have any valid name, and must be located in
the  configuration  directory  (see the Installion section).  The
commands in the file are  described  in  the  Dialer  Subcommands
chapter.

If the <dialer-file> is missing, any previous dialer command pro-
cess will be removed.  If <seconds> is missing, the <dialer-file>
will be executed  immediately  without  any  further  tests.   If
<tests> is missing, the default is 2.  If <hostid> is missing and
the interface uses the PPP encapsulation, the PPP LCP  echo  will
be used instead.

3.16.  dir [<dirname>]

List the contents of the specified directory on the  console.  If
no  argument is given, the current directory is listed. Note that
this command works by first listing the  directory  into  a  tem-
porary  file,  and  then  creating  a more session to display it.
After this completes, the temporary file is deleted.

3.17.  disconnect [<session #>]

An alias for the close command (for the benefit of AX.25 users).

3.18.  domain ...

These commands control the operation of the Internet Domain  Name
Service (DNS).



                        June 7, 1991





                           - 14 -


3.18.1.  domain addserver <hostid>

Add one or more  domain  name  server(s)  to  the  list  of  name
servers.

3.18.2.  domain dropserver <hostid>

Remove one or more domain name server(s) from the  list  of  name
servers.

3.18.3.  domain listservers

List the currently configured domain  name  servers,  along  with
statistics  on  how  many queries and replies have been exchanged
with each one, response times, etc.

3.18.4.  domain query <hostid>

Send a query to a domain server asking for all  resource  records
associated with this <hostid>, and list the records.

3.18.5.  domain retry [<count>]

Display or set the number of attempts to reach each server on the
list during one call to the resolver.  If this count is exceeded,
a failure indication is returned.  If set to  0,  the  list  will
cycle  forever; this may be useful for unattended operation.  The
default is 3.

3.18.6.  domain suffix [<domain suffix>]

Display or specify the default domain name suffix to be  appended
to  a  host name when it contains no periods. For example, if the
suffix is set to ampr.org and the user enters  telnet  ka9q,  the
domain  resolver  will attempt to find ka9q.ampr.org. If the host
name being sought contains one  or  more  periods,  however,  the
default  suffix  is  NOT applied (eg. telnet foo.bar would NOT be
turned into foo.bar.ampr.org).

3.18.7.  domain trace [on | off]

Display or set the flag controlling the tracing of domain  server
requests  and  responses.  Trace  messages will be seen only if a
domain name being sought is not found in the  local  cache  file,
domain.txt.

3.18.8.  domain cache ...

These commands are used for the use of the resource  record  file
domain.txt, and the local memory cache.

3.18.8.1.  domain cache clean [on | off]

Display or set the  flag  controlling  the  removal  of  resource



                        June 7, 1991





                           - 15 -


records  from  the domain.txt file whose time-to-live has reached
zero.

When  clean  is  off  (the  default),  expired  records  will  be
retained;  if  no replacement can be obtained from another domain
name server, these records will continue to be used.

When clean is on, expired records will be removed from  the  file
whenever any new record is added to the file.

3.18.8.2.  domain cache list

List the current contents of the local memory cache.

3.18.8.3.  domain cache size [<count>]

Display or set the nominal  maximum  size  of  the  local  memory
cache.  The default is 20.

(Note: The cache may be temporarily larger when waiting  for  new
records to be written to the domain.txt file.)

3.18.8.4.  domain cache wait [<seconds>]

Display or set the interval in seconds  to  wait  for  additional
activity before updating the domain.txt file.  The default is 300
seconds (5 minutes).

3.19.  echo [accept | refuse]

Display or set the flag controlling client Telnet's response to a
remote WILL ECHO offer.

The Telnet presentation protocol specifies that in the absence of
a  negotiated  agreement to the contrary, neither end echoes data
received from the other.  In this mode, a Telnet  client  session
echoes  keyboard input locally and nothing is actually sent until
a carriage return is typed. Local line editing is also performed:
backspace  deletes  the  last  character  typed,  while control-U
deletes the entire line.

When communicating from keyboard to keyboard the  standard  local
echo  mode  is  used,  so  the  setting  of this parameter has no
effect. However, many timesharing systems (eg. UNIX) prefer to do
their  own  echoing  of  typed input.  (This makes screen editors
work right, among other things). Such systems send a Telnet  WILL
ECHO  offer immediately upon receiving an incoming Telnet connec-
tion request. If echo accept is in effect, a client  Telnet  ses-
sion  will automatically return a DO ECHO response. In this mode,
local echoing and editing is turned off and each  key  stroke  is
sent immediately (subject to the congestion control algorithms in
TCP).  While this mode is just fine across  an  Ethernet,  it  is
clearly  inefficient  and  painful  across slow paths like packet
radio channels. Specifying echo refuse causes  an  incoming  WILL



                        June 7, 1991





                           - 16 -


ECHO  offer  to  be  answered with a DONT ECHO; the client Telnet
session remains in the local echo mode.  Sessions already in  the
remote  echo  mode are unaffected. (Note: Berkeley Unix has a bug
in that it will still  echo  input  even  after  the  client  has
refused  the  WILL  ECHO offer. To get around this problem, enter
the stty -echo command to the shell once you have logged in.)

3.20.  eol [unix | standard]

Display or set Telnet's end-of-line behavior when in remote  echo
mode.   In  standard  mode, each key is sent as-is. In unix mode,
carriage returns are translated to line feeds.  This  command  is
not  necessary  with  all UNIX systems; use it only when you find
that a particular system responds to line feeds but not  carriage
returns.   Only SunOS release 3.2 seems to exhibit this behavior;
later releases are fixed.

3.21.  escape [<char>]

Display or set the current command-mode escape character in  hex.
(This  command  is  not  provided  on  the IBM-PC; on the PC, the
escape char is always F10.)

3.22.  etherstat

Display 3-Com Ethernet controller statistics (if configured).

3.23.  exit

Exit the net.exe program and return to MS-DOS.

3.24.  finger <user@hostid> [<user@hostid> ...]

Issue a network finger request for user user at host hostid. This
creates  a  client  session  which  may  be interrupted, resumed,
reset, etc, just like a Telnet client session.

3.25.  ftp <hostid>

Open an FTP control channel to  the  specified  remote  host  and
enter  converse  mode  on  the  new  session.  Responses from the
remote server are displayed directly on the screen. See  the  FTP
Subcommands chapter for descriptions of the commands available in
a FTP session.

3.26.  help

Display a brief summary of top-level commands.

3.27.  hop ...

These commands are used to test the connectivity of the network.





                        June 7, 1991





                           - 17 -


3.27.1.  hop check <hostid>

Initiate a hopcheck session to the specified host.  This  uses  a
series  of  UDP  "probe" packets with increasing IP TTL fields to
determine the sequence of gateways in the path to  the  specified
destination. This function is patterned after the UNIX traceroute
facility.

ICMP message tracing should be turned off before this command  is
executed (see the icmp trace command).

3.27.2.  hop maxttl [<hops>]

Display or set the maximum TTL value to be used in hop check ses-
sions.  This effectively bounds the radius of the search.

3.27.3.  hop maxwait [<seconds>]

Display or set the maximum interval that a hopcheck session  will
wait  for  responses at each stage of the trace. The default is 5
seconds.

3.27.4.  hop queries [<count>]

Display or set the number of UDP probes that will be sent at each
stage of the trace. The default is 3.

3.27.5.  hop trace [on | off]

Display or set the flag that controls the display  of  additional
information during a hop check session.

3.28.  hostname [<name>]

Display or set the local host's name. By convention  this  should
be  the  same  as  the host's primary domain name. This string is
used only  in  the  greeting  messages  of  the  various  network
servers; note that it does NOT set the system's IP address.

If <name> is the same as an  <iface>  (see  the  Attach  commands
chapter),  this  command  will search for a CNAME domain resource
record which corresponds to the IP address of the <iface>.

3.29.  hs

Display statistics about the HS high speed HDLC driver  (if  con-
figured and active).

3.30.  icmp ...

These commands are used for the Internet Control Message Protocol
service.





                        June 7, 1991





                           - 18 -


3.30.1.  icmp echo [on | off]

Display or set the flag controlling the asynchronous  display  of
ICMP Echo Reply packets.  This flag must be on for one-shot pings
to work (see the ping command.)

3.30.2.  icmp status

Display statistics about the Internet  Control  Message  Protocol
(ICMP),  including  the number of ICMP messages of each type sent
or received.

3.30.3.  icmp trace [on | off]

Display or set the flag controlling the  display  of  ICMP  error
messages.  These informational messages are generated by Internet
routers in response to routing, protocol or congestion  problems.
This  option  should  be  turned  off  before using the hop check
facility because it relies on ICMP Time  Exceeded  messages,  and
the  asynchronous  display of these messages will be mingled with
hop check command output.

3.31.  ifconfig

Display a list of interfaces, with a short status for each.

3.31.1.  ifconfig <iface>

Display an extended status of the interface.

3.31.2.  ifconfig <iface> broadcast <address>

Set the broadcast address for the interface.  The <address> takes
the  form  of  an  IP  address  with  1's in the host part of the
address.  This is related to the netmask sub-command.   See  also
the arp command.

3.31.3.  ifconfig <iface> encapsulation <name>

Not fully implemented.

3.31.4.  ifconfig <iface> forward <forward-iface>

Set a forwarding interface for multiple channel  interfaces.   To
remove the forward, set <forward-iface> to <iface>.

3.31.5.  ifconfig <iface> ipaddress <hostid>

Set the IP address for this interface.  It is  standard  Internet
practice that each interface has its own address.  For hosts with
only one interface, the interface address is usually the same  as
the host address.  See also the hostname and ip address commands.