
attach


Attaching the ports on a PC

    attach <hw_type> <io_addr> <vector> <mode> <label> <bufsize> <mtu>
    [<speed>]

     Configure and attach a hardware interface to the system. Detailed
instructions for each driver are in the Attach Commands chapter.  An
easy way to obtain a summary of the parameters required for a given
device is to issue a partial attach command (e.g., attach asy). This
produces a message giving the complete command format.

        <hw_type> is the kind of I/O device being attached to the
        system.
        <io_addr> is the base address of the control registers for the
        device.
        <vector>  is the interrupt vector number.  Both the address
        and the vector must be in hexadecimal.  You may put "0x" in
        front of the numbers, but they will be interpreted in
        hexadecimal even without the prefix.
        <mode>    controls how IP datagrams are to be encapsulated in
        the device's link level protocol.
        Choices are ax25 or slip.

     slip      Encapsulates IP datagrams directly in SLIP frames
     without a link header.  This is for operating point-to-point
     lines and is compatible with 4.28BSD UNIX SLIP.

     ax25      Similar to slip, except that an AX.25 header and a KISS
     TNC control header are added to the front of the datagram before
     SLIP encoding.  Either UI (connectionless) or I (connection-
     oriented) AX.25 frames can be used.
        
        <label>   defines the name by which the interface will be
        known to various commands, such as "connect", "route",
        "trace", etc.
        
        <bufsize> For ASYNCHRONOUS PORTS, specifies the size of the
        ring buffer in bytes to be statically allocated to the
        receiver; incoming bursts larger than <bufsize> may cause data
        to be lost.
        For ETHERNET, specifies how many PACKETS may be queued in the
        receive queue at one time.  Excess packets will be discarded
        as they are received.  This is useful to prevent the system
        from running out of memory should another node suddently
        develop a case of diarrhea.
        
        <mtu>     is the Maximum Transmission Unit size in bytes.  See
        the System Configuration Manual for a discussion of the effect
        of MTU on system performance.

    attach asy <io_addr> <vector> <mode> <label> <bufsize> <mtu>
    [<speed>]

     Configure and attach a standard PC asynchronous I/O port using
the National 8250, 16450, or 16550 chip or equivalent to the system,
where:

        <io_addr> is the comm port address; e.g., com1 = 0x3f8
        <vector>  is the comm port IRQ value.
        
    attach axip <iface> <mtu> <ipaddress> [<callsign>]

     Create a RFC1226 compatible AX.25 frame encapsulator for
transmission of AX.25 frames over the IP.  This command is used to
establish a point-to-point AX.25 'tunnel' between two systems.


        <iface>   will be the name of the new interface,
        <mtu>     is the maximum transmission unit for the interface,
        <ipaddress> is the address of the system on the other side of
        the 'tunnel,
        <callsign> is the optional AX.25 callsign this station is
        listening on for frames to digipeat. Note that if you want
        cross-tunnel digipeating to work, each attached axip interface
        should listen to a different callsign.  These should also be
        different from other callsigns used on this station.
          
          attach axip axip1 256 44.26.1.19 WG7J-15
          
          
    attach pkiss <iface> <mtu> <ipaddress> [<callsign>]
     Attach a serial port in G8BPQ polled kiss mode.
     
     To attach other TNCs to be polled on the same port, attach them
     as additional kiss devices (see below).  They will automatically
     be polled.
     
    attach kiss <asy_iface_label> <port> <label> [mtu]

     Attach a second kiss interface on the serial port. This command
     allows the use of multiport TNCs.
     
        <asy_iface_label>   is the name of the serial port interface.
        <port>    is the port number (1-15) to use, and probably
        should be 1. (the original asy port is automatically port 0 !)
        <label>   is the name for this second kiss port.
        <mtu>     is an optional mtu, if different from the mtu on the
        first kiss port.

          # Attach a dualport tnc in kiss mode.
          # Ports are labelled 'port1' and 'port2'
          
          # Attach a PC asynch port (com1 in this example)
          
          attach asy 03f8 4 ax25 port1 512 256 9600
          
          # Attach the second port on the multiport tnc
          
          attach kiss port1 1 port2
          
    

    

    attach netrom

     This makes available a pseudo interface to enable NET/ROM
operations.  This command is automatically executed when the netrom
server is started with the 'start netrom' command.

     [ipaddress] is an optional ip address for the netrom interface.
If not set, the system 'ip address' will be used.


    attach packet <softintr#> <iface_label> <maxqueue> <mtu>

     Driver for use with separate software "packet drivers" which
     conform to the FTP Software, Inc., Software Packet Driver
     specification.  See the Crynwr (TM) packet driver collection
     if your hardware driver came without a packet driver.
     
    attach scc

     PE1CHL driver for generic 8530 cards
     

