ethload user's guide.txt

黑客培训教程

       29        PHONE
       42        CTERM
 
 NETWORKS.XNS
       
       This  file  contains the mapping between the  XNS  (or  IPX)
       network numbers and their names.
       
       This  file  is  used  when  you  are  displaying  XNS/Novell
       screens else it can be safely deleted.
       
       The  key token is the network number in the format XX-XX-XX-
       XX where each X is an hexadecimal digit.
       
       The shipped NETWORK.XNS file contains:
       
       00-00-00-00     Local
       FF-FF-FF-FF     Broadcast
       ;
       ;   The rest has to be customized
       ;
       00-00-00-03     Net3
       
       Of  course this file will have to be heavily customized  for
       each site.
       
 
 TYPES.XNS
       
       This  file  contains the mapping between the  XNS  (or  IPX)
       protocol types and their names.
       
       This  file  is  used  when  you  are  displaying  XNS/Novell
       screens else it can be safely deleted.
       
       The  key  token  is the type number in the format  XX  where
       each X is an hexadecimal digit.
       
       The file TYPES.XNS contains:
       
       00        Unknown
       01        RIP (Routing Information Protocol)
       02        Echo
       03        Error
       04        PEP (Packet Exchange, datagram)
       05        SPP/SPX (Sequence Packet Protocol)
       11        Netware Core Protocol
       
       This file should be correct for most networks.
       
 
 WKS.XNS
       
       This  file  contains the mapping between the  XNS  (or  IPX)
       socket numbers and their names.
       
       This  file  is  used  when  you  are  displaying  XNS/Novell
       screens else it can be safely deleted.
       
       The  key  token is the socket number in the format XX-XX-XX-
       XX where each X is an hexadecimal digit.
       
       The file WKS.XNS contains:
       
       0001    RIP (Routing Information)
       0002    Echo
       0003    Error Handler
       0451    Novell File Service
       0452    Novell Service Advertising
       0453    Novell Routing Information
       0455    Novell NetBIOS
       0456    Novell diagnostic
       0457    Novell Copy Protection
       
       This file should be correct for most sites.
       
 
 NLIDS.OSI
       
       This  file  contains the mapping between the first  byte  of
       the network PDU for the OSI stack.
       
       Currently, the file contains only:
       
       00      ISO 8473: inactive network layer
       81      ISO 8473: ES-ES
       
       This should be correct for most sites.
       
 
 SELECTOR.OSI
       
       This  file  contains the mapping between the  NSAP  selector
       (last byte of a NSAP) and its name.
       
       The key token format is two hexadecimal digits.
       
       Here follow a few lines from the file:
       
       00        Network Layer Identifier
       06        TCP & UDP with Bigger Addresses (TUBA): TCP
       11        TCP & UDP with Bigger Addresses (TUBA): UDP
       1E        CLNP short term ping request
       1F        CLNP short term ping reply
       20        DECnet/OSI: NSP transport
       21        DECnet/OSI: OSI transport
       
       This  file may be customized for your network but should  be
       correct.
 
 NSAPS.OSI
       
       This file contains the mapping between a NSAP and its name.
       
       The  format of the key token is HH-HH....-HH where HH  is  a
       hexadecimal digit. There can be up to 20 bytes in the  NSAP.
       The file may contain NSAP of different length.
       
       Here follow a possible line for the NSAPS.OSI file:
       
       39-52-8F-11-00-00-09-10-00-00-00-00-40-BB-BB-AA-AA-00-10-00
       tuba10
       
       This  file  should be customized for your site, the  shipped
       file is just an example.
 
 AFI.OSI
       
       This  file  contains the mapping between the  Authority  and
       Format Identifier (first byte of a NSAP) and its name.
       
       The key token format is HH where h is an hexadecimal digit.
       
       Here follows some lines from the shipped AFI.OSI:
       
       36        X.121: decimal coded: non-zero first IDI digit
       37        X.121: binary coded: non-zero first IDI digit
       38        DCC (Data Country Code): decimal coded
       39        DCC (Data Country Code): binary coded
       
       The file should be correct as shipped.
       
 
 ICD.OSI
       
       This  file contains the mapping between an ISO IDI with  the
       format  Internal  Code  Designator  and  the  name  of   the
       organization.
       
       The key token format is HH-HH.
       
       Here follow a few line from the shipped ICD.OSI:
       
       0057    Saint Gobian
       0058    Siemens Corporate Network
       0059    DANZNET
       0060    Data Universal Numbering System
       
       The file should be correct as shipped.
       
 
 DCC.OSI
       
       This  file contains the mapping between an ISO IDI with  the
       format Data Country Code and the name of the country.
       
       The key token format is HH-HH.
       
       Here follow a few lines from the shipped file:
       
       052     BARBADOS
       112     BELARUS
       056     BELGIUM
       084     BELIZE
       
       The file should be correct4 as shipped.
       
                               * * *
                                * *
                                 *

4. Set-up of datalink drivers.
       
       ETHLOAD  as already said is currently running as  it  is  on
       the   top  of  four   different  datalink  drivers.  ETHLOAD
       automatically  configures itself to  use  the  first  driver
       found. It tries in the following order:
         - Novell ODI;
         - Microsoft 3Com NDIS version 2.0.1 or higher5;
         - Digital Equipment DLL;
         - PC/TCP packet driver;
         - ASCII file driver.
       
       If  you  use another driver and you have a specification  of
       its  API  (or  even some C routines in the  public  domain),
       please  email me because I would like that ETHLOAD  runs  on
       nearly all datalink drivers... ;-)
       
       Sun  PC-NFS  drivers  are NOT supported by  ETHLOAD,  mainly
       because  the specification is not freely available and  also
       because Sun seems to prefer to use NDIS now.
       
       If  this order does not work for you, you will have  to  use
       the  -d option in the command line for starting ETHLOAD (see
       section 5).
       
       Some  of  these  datalink  drivers  allow  for  simultaneous
       execution  of ETHLOAD and of you usual protocol stack:  NDIS
       and  ODI.  All other drivers prevent the execution  of  your
       usual  protocol  stack, it means that  you  will  abort  all
       current connections to any servers.
       
       Some  of  these datalink drivers do not require a PC  reboot
       after  running them: DLL, NDIS version 2.0 or higher, packet
       driver and ODI.
       
       Finally, only one kind of drivers namely ODI allows for  the
       identification   of  faulty  frame  by   their   source   or
       destination addresses.
       
       In  conclusion, if your Ethernet hardware has a  ODI  driver
       with promiscuous mode support, it is better to use ODI.
       
       ETHLOAD  despite its name can probably work on all IEEE  LAN
       (with  48  bits  addresses and IEEE  802.2  LLC  sub-layer).
       Starlan has been analyzed through ETHLOAD. The single  point
       to  keep  in  mind is that the MAC screen (see  further)  is
       computed  for  a bandwidth of 10 Mbps (or you may  elect  to
       use the -b option to specify the LAN bandwidth).
       
       Another important point is that most Token Ring adapters  do
       not  support  promiscuous mode (notably IBM  adapters).  So,
       when  starting ETHLOAD a warning message will  be  displayed
       and   only  broadcast/multicast  packets  will  be  analyzed
       showing  a very lightly loaded token ring! The only  way  to
       escape  this  problem is to get a promiscuous  mode  adapter
       and  driver  (IBM  has  a  trace  adapter,  Olicom  supports
       promiscuous  mode).  The ODI driver for  Madge  adapters  is
       supported by ETHLOAD.
       
       A   final  remark,  packet  driver  does  not  differentiate
       between  the  various kind of errors in its statistics.  So,
       you should use any other driver if possible.
 
 4.1. Novell ODI.
       
       The  first  thing to note is that only very few ODI  drivers
       supports  the promiscuous mode which is needed for  ETHLOAD.
       Novell  has  a  list of those drivers since the  promiscuous
       mode is also needed by Novell LANanalyzer product.
       
       You  should also check that your NET.CFG has enough  buffers
       and  mempool  allocation (see also the  annex  about  common
       pitfalls).
       
       To  use  ETHLOAD,  you  just have to  load  the  ODI  driver
       (preceded as usual by loading LSL.COM) and having a  correct
       NET.CFG.  If  you can run any other ODI application  (Novell
       LAN  Workplace  for DOS, Siemens Nixdorf LAN  1,  ...),  you
       should  be  able  to run ETHLOAD as it is. Nevertheless,  it
       seems that IPXODI and NETX cannot be loaded before ETHLOAD.
       
       The  use  of ETHLOAD is not disruptive to your other network
       application  which  will  continue  to  run  at   very   bad
       efficiency...
       
       ETHLOAD  does  not support IEEE 802.2 type 2 frames,  so  if
       your  NET.CFG contains several frame types, you may have  to
       use  the -do2 option to select the second frame type, or the
       -do3, ...
       
       To  start ETHLOAD, just issue the ETHLOAD command to the MS-
       DOS prompt.
       
 
 4.2. Microsoft 3Com NDIS v 1.0.1.
       
       Before  running ETHLOAD for the first time, you must  modify
       your       PROTOCOL.INI      (usually       located       as
       C:\LANMAN\PROTOCOL.INI see your C:\CONFIG.SYS file  and  the
       DEVICE=..PROTMAN... /I:<path>).
       
       You  must  add  the  following lines  in  your  PROTOCOL.INI
       (anywhere in the file but after a section):
       
       [ETHLOAD]
            drivername = ETHLOAD$
            bindings = MYMAC
       
       where MYMAC is the name of the MAC module you want  to use.
       
       These  modifications do not modify the  usual  behaviour  of
       your  PC,  so you may leave these lines in your PROTOCOL.INI
       file even if you don't use ETHLOAD.
       
       After you have made these changes, you must reboot your PC.
       
       After  this  reboot, when you want to use ETHLOAD  you  must
       issue the ETHLOAD command to the MS-DOS prompt.
       
       By  the  way,  the  Protocol Manager  directory  (containing
       NETBIND.EXE, ...) should be in the PATH of MS-DOS.
       
       Remark  1: in PROTOCOL.INI the case of the left part of  '='
       does  not matter, but uppercase characters must be  used  on
       the right part as indicated in the examples above.
       
       Remark  2:  as  you are using a version of Protocol  Manager
       older  than  version  2.0.1  6, ETHLOAD  will  display  some
       warnings  and  you  have  to pay special  attention  to  the
       following points:
             don't  run NETBIND.EXE before ETHLOAD (so look out  in
           your AUTOEXEC.BAT for an automatic run of NETBIND.EXE)7
             reboot  your  PC after running ETHLOAD since  Protocol
           Manager cannot be reset in a correct state
            some statistics are missing.
 
 4.3. Microsoft 3Com NDIS v2.0.1 or higher.
       
       Before  running ETHLOAD for the first time, you must  modify
       your       PROTOCOL.INI      (usually       located       as
       C:\LANMAN\PROTOCOL.INI see your C:\CONFIG.SYS file  and  the
       DEVICE=..PROTMAN... /I:<path>).
       
       You  must  add  the  following lines  in  your  PROTOCOL.INI
       (anywhere, after a section):