Network library lcrzo

              -------------------------------------------
              |              KNOWN PROBLEMS             |
              -------------------------------------------

This file describes known problems (incompatibilities, unsupported
functionalities, errors, etc.).
If you seek help (usage help, examples, etc.), it's better to read 
lcrzo-4.xx-doc_html.tgz.

Problems described in this file are (if you encounter an unknown problem,
thanks for contacting me, as explained in ./doc/problemreport_en.txt) :

PROBLEMS CAUSED BY THE SYSTEM
 1: [Windows] Display is slow.
 2: [Windows] The system crashes when lcrzoex is run.
 3: [Windows 95] At lcrzo end, the modem link stops.
 4: [Windows XP] Converting an IP address to a hostname returns a bad value.
 5: [Windows XP] Functions lcrzo_hs_init_xxx returns bad value.

PROBLEMS CAUSED BY LIBPCAP OR WINPCAP
 6: [Windows] Several tools of lcrzoex doesn't seem to work.
 7: [Windows] Sniff does not work with a modem
 8: [Windows] Popup : The dynamic library wpcap.dll was not found. 
    [Note : I'am not sure about the exact error message because I do not 
    have access to an English computer]

PROBLEMS CAUSED BY LCRZO'S DESIGN
 9: Network configuration is incorrect.
10: Lcrzo's functions behave strangely
11: Lcrzo's functions interfere with other functions
12: Lcrzo is slow.
13: Some functionalities does not fully work.
14: Some functionalities are not provided.



-------------------------------------------------------------------------------
Problem 1 :
  Problem synthesis :
    Display is slow.
  Environment affected by the problem :
    Windows
  What's causing the problem :
    In a msdos console, we cannot print more than 100 lines per seconds.
  Solution 1 :
    Redirect output in a file :
      commandname > fichier
    However in this case, we do not see when data has to be entered.
  Solution 2 :
    Use tools, or printprofiles, less verbose.

-------------------------------------------------------------------------------
Problem 2 :
  Problem synthesis :
    The system crashes when lcrzoex is run.
  Environment affected by the problem :
    Windows
  What's causing the problem :
    Under Windows 95/98, when a network board is not correctly configured,
    the driver cannot be opened by WinPCAP (PacketOpenAdapter). The driver
    crashes, and also the system.
  Solution :
    We have to ensure the network card is correctly configured :
    [menu names might be incorrect, because I do not have access to
    an English localized computer]
     - Open menu Start, Parameters, Configuration, Icon System,
       Periphericals, Network Cards. You should see one line per card.
       Moreover, the icon should not have "(!)" on top of it.
     - Open menu Start, Parameters, Configuration, Icon Network.
       The network card should be here, and linked to TCP/IP. Moreover
       TCP/IP configuration should be correct.

-------------------------------------------------------------------------------
Problem 3 :
  Problem synthesis :
    At lcrzo end, the modem link stops.
  Environment affected by the problem :
    Windows 95 with a modem
  What's causing the problem :
    At the end of a program, references to unused object are freed.
    It's the case for the low level driver of WinPcap (packet.sys).
    Unfortunately, as explained in WinPcap FAQ, Windows also
    stops the modem connection. So, at the end of lcrzoex, the phone
    line stops.
  Solution 1 :
    Installation of :
     - Windows Sockets 2 Update, and
     - Dialup Networking 1.3 Update
    might resolv this problem. 
    Those updates are available here :
     - http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/default.asp
     - http://www.microsoft.com/Windows95/downloads/contents/WURecommended/S_WUNetworking/dun13win95/Default.asp
  Solution 2 :
    You can contact WinPcap developers to help them to write a 
    driver/dll not having this problem.

-------------------------------------------------------------------------------
Problem 4 :
  Problem synthesis :
    Converting an IP address to a hostname returns a bad value.
  Environment affected by the problem :
    Windows XP
  What's causing the problem :
    Functions lcrzo_hs_init_xxx use gethostbyaddr().
    However, there is a bug in WindowsXP's implementation of gethostbyaddr,
    as described in Knowledge Base Q317936 of Microsoft.
    This bug appears when DNSorWINS and NetBIOSoverTCPIP are activated.
  Solution :
    Patch Q317936 corrects this problem.

-------------------------------------------------------------------------------
Problem 5 :
  Problem synthesis :
    Functions lcrzo_hs_init_xxx returns bad value.
  Environment affected by the problem :
    Windows XP
  What's causing the problem :
    Functions lcrzo_hs_init_xxx use gethostbyaddr().
    However, there is a bug in WindowsXP's implementation of gethostbyaddr,
    as described in Knowledge Base Q317936 of Microsoft.
    This bug appears when DNSorWINS and NetBIOSoverTCPIP are activated.
  Solution :
    Patch Q317936 corrects this problem.

-------------------------------------------------------------------------------
Problem 6 :
  Problem synthesis :
    Several tools of lcrzoex doesn't seem to work.
  Environment affected by the problem :
    Windows
  What's causing the problem :
    Lcrzo depends on WinPcap. If WinPcap does not work, several
    functionalities of lcrzo/lcrzoex will not work.
    So, we have to ensure WinPcap works correctly.
  Solution :
    Install and test windump as described in INSTALL_FR.TXT.

-------------------------------------------------------------------------------
Problem 7 :
  Problem synthesis :
    Sniff does not work with a modem
  Environment affected by the problem :
    Windows
  What's causing the problem :
    WinPCAP is not conceived to work with a modem.
    File lcrzoex-4.xx-doc-html.tgz/en/examples.html lists systems where
    modems are supported.
  Solution :
    If your system does not support modems, try to apply WinPCAP solution :
      http://winpcap.polito.it/misc/dialup.htm

-------------------------------------------------------------------------------
Problem 8 :
  Problem synthesis :
    Popup : The dynamic library wpcap.dll was not found. 
    [Note : I'am not sure about the exact error message because I do not 
    have access to an English computer]
  Environment affected by the problem :
    Windows
  What's causing the problem :
    WinPCAP is not installed.
  Solution :
    Download and install WinPCAP as described in INSTALL_EN.TXT
    or INSTALLWINDOWS_EN.TXT.

-------------------------------------------------------------------------------
Problem 9 :
  Problem synthesis :
    Network configuration is incorrect.
  Environment affected by the problem :
    All
  What's causing the problem :
    Obtaining the configuration (device, arp cache, routes) of the 
    local computer is an important step of lcrzo. Several tools need
    this configuration to be accurate.
    Different kinds of network cards, modems, operating systems, etc.
    exist. So, it's possible that your computer contains unrecognized
    hardware. In this case, several lcrzoex tools would be 
    unusables.
    For these reasons, the first tool to use is 'lcrzoex 157' to
    ensure correct configuration setting.
    Here is a correct example (taken on Linux) :
     Devices
      device  ethernet          ip          /netmask        mtu
      lo      00:00:00:00:00:00 127.0.0.1   /255.0.0.0      3924 up
      eth0    00:00:33:AC:C2:24 192.168.1.1 /255.255.255.0  1500 up
      eth0:1  00:00:33:AC:C2:24 192.168.2.1 /255.255.255.0  1500 up,alias
      eth1    00:00:43:BC:D2:34 192.168.3.1 /255.255.255.0  1500 up
     Arp
      lo      00:00:00:00:00:00 127.0.0.1     (permanent)
      eth0    00:00:33:AC:C2:24 192.168.1.1   (permanent)
      eth0:1  00:00:33:AC:C2:24 192.168.2.1   (permanent)
      eth1    00:00:43:BC:D2:34 192.168.3.1   (permanent)
      eth0    12:34:56:78:90:ab 192.168.1.254 (-1s)
     Routes
      device  destination  /netmask         ip_source     gateway
      lo      127.0.0.1    /255.255.255.255 local_device                 0,up
      eth0    192.168.1.1  /255.255.255.255 local_device                 0,up
      eth0:1  192.168.2.1  /255.255.255.255 local_device                 0,up
      eth1    192.168.3.1  /255.255.255.255 local_device                 0,up
      eth0    192.168.1.0  /255.255.255.0   192.168.1.1                  0,up
      eth0:1  192.168.2.0  /255.255.255.0   192.168.2.1                  0,up
      eth1    192.168.3.0  /255.255.255.0   192.168.3.1                  0,up
      lo      127.0.0.0    /255.0.0.0       127.0.0.1                    0,up
      eth0    0.0.0.0      /0.0.0.0         192.168.1.1   192.168.1.254  0,up
    In this example, we see the loopback device (lo), and two network cards
    (eth0 and eth1). Card eth0 has an alias.
    The arp table contains permanent entries, and the dynamic entry for
    the router 192.168.1.254.
    The routing table first contains entries to access local devices, then
    network connected to the local devices, and finally the default router
    192.168.1.254.
  Solution :
    As I cannot have access to your hardware, you have to send me information
    about your configuration in order to help lcrzo's improvements.
    Run :
      lcrzoex 278 > resultfile
    Then, send me the file 'resultfile', along with configuration information
    (ifconfig, ipconfig /all, arp -a, route print, netstat -rn, 
    winipcfg /all /batch file.out, winipcfg, network card type, modem type,
    etc.). Thanks.

-------------------------------------------------------------------------------
Problem 10 :
  Problem synthesis :
    Lcrzo's functions behave strangely
  Environment affected by the problem :
    All
  What's causing the problem :
    There might exist conflicts between lcrzo and your program.
  Solution :
    Read integration_en.txt.

-------------------------------------------------------------------------------
Problem 11 :
  Problem synthesis :
    Lcrzo's functions interfere with other functions
  Environment affected by the problem :
    All
  What's causing the problem :
    There might exist conflicts between lcrzo and your program.
  Solution :
    Read integration_en.txt.

-------------------------------------------------------------------------------
Problem 12 :
  Problem synthesis :
    Lcrzo is slow.
  Environment affected by the problem :
    All
  What's causing the problem :
    I choose to create a modular library, easy to use.
    One of the consequence is the high level structuration of lcrzo.
    So, it is slower than a low level programming interface.
  Solution 1 :
    Using records (lcrzo_record.h), you can construct your packets,
    save them, and then send them.
  Solution 2 :
    You can also use only low level fonctions of lcrzo, and create
    your specific code around.
    If its still too slow, you should not use lczro and use directly
    system's functions, or buy a new computer ;)

-------------------------------------------------------------------------------
Problem 13 :
  Problem synthesis :
    Some functionalities does not fully work.
  Environment affected by the problem :
    All
  What's causing the problem :
    Lcrzo's development contains several branches, each one having its 
    own priority. I cannot develop everything in one day :). So, my 
    priorities might not be the same as yours.
  Solution 1 :
    Read todo.txt to obtain list of action to be done.
  Solution 2 :
    Contact-me to explain your needs.

-------------------------------------------------------------------------------
Problem 14 :
  Problem synthesis :
    Some functionalities are not provided.
  Environment affected by the problem :
    All
  What's causing the problem :
    Lcrzo's development contains several branches, each one having its 
    own priority. I cannot develop everything in one day :). So, my 
    priorities might not be the same as yours.
  Solution 1 :
    Read todo.txt to obtain list of action to be done.
  Solution 2 :
    Contact-me to explain your needs.