Odyssey Client Enterprise Edition, version 4.30 for Linux 

***********************************************************************
README.TXT                                                 July 7, 2006

    This file contains important information about system requirements,
    compatibility with other products, known problems, late-breaking
    items that are not covered in the manual, etc.

***********************************************************************
Contact information:

    Juniper Networks, Inc.
    1194 North Mathilda Avenue
    Sunnyvale, CA 94089

    (408) 745-2000             (Main number)
    (408) 936-1576             (Technical support number)
    http://www.juniper.net     (web home page)

***********************************************************************
Operating System Requirements:

    Odyssey Client for Linux runs on any of the following:

        Red Hat Enterprise Linux 3
        Red Hat Enterprise Linux 4

***********************************************************************
Hardware Compatibility:

    The Odyssey Client is capable of authenticating with any Wireless
    Access point or Ethernet switch that supports the 802.1x protocol.

    The Odyssey Client is capable of performing 802.1x authentication
    using a wireless adapter card driver that supports the
    Atheros AR5002, AR5004, AR5005 or AR5006 chipsets.

    The wireless adapter card must be based on an Atheros AR5002, AR5004, 
    AR5005, or AR5006 chipset. You can verify if a specific NIC uses
    one of these chipsets by consulting the Customer Product Database
    on Atheros web site.
    http://customerproducts.atheros.com/customerproducts/ResultsPageBasic.asp.  


***********************************************************************
Installing Odyssey Client:

    * Odyssey Client will run on RHEL3 U5 (kernel 2.4.21-32.0.1.EL)
      or RHEL4 U2 (kernel 2.6.9-22.0.1.EL). The kernel version can be
      determined by running the "uname -a" from a terminal window.

    * You must have super user privileges to install Odyssey Client and
      the NIC driver. 

    * To install the latest NIC driver on RHEL3,
      copy the package locally and uncompress it using the command:
          "tar xvfz igx-atheros-rhel3.tar.gz"
      then install it using the command:
          "rpm -vih ixath-Linux-i686-1.0.18-FUNK.i686.rpm"

    * To install the latest NIC driver on RHEL4,
      copy the package locally and uncompress it using the command:
          "tar xvfz igx-atheros-rhel4.tar.gz"
      then install it using the command:
          "rpm -vih ixath-Linux-i686-1.0.18-FUNK.i686.rpm"

    * To install Odyssey Client, invoke the executable:
      For RHEL3:
          "./OdysseyClientLinuxRH3.rpm.bin"
      For RHEL4:
          "./OdysseyClientLinuxRH4.rpm.bin"
      Press Y and Enter to accept the End User License Agreement.


***********************************************************************
New Features in Odyssey Client 4.30:

    * Initial support of Red Hat Enterprise Linux 3 and 
      Initial support of Red Hat Enterprise 4


***********************************************************************
Known Issues:
  

1) Odyssey Client for Linux can operate with a dynamically 
   assigned IP address, but it requires special configuration to 
   enable a custom DHCP client instead of the DHCP client that 
   is built into Linux.

   To enable an adapter to use a dynamically assigned IP 
   address, you configure the adapter's settings to "static" 
   with an EMPTY IP address, netmask and gateway.

   To enable an adapter to use a static assigned IP address, 
   configure the target adapter to "static" and supply the 
   desired IP address, netmask and gateway.

   Enabling DHCP on an adapter configured in Odyssey Client
   will cause multiple DHCP clients to be run.  This may
   result in unpredictable behavior.

2) Changes to an adapter's IP configuration may not be noticed by the
   client.  If changes are made while the client is running, the user
   must click Settings/Close and then reopen the client.

3) This release does not support certificates containing a private key
   longer than 2048 bits.  An 'Unexpected Error' dialog will be displayed
   if a certificate with a private key length greater than 2048 is used.
   If you install such a certificate, you will have to remove it to
   restore normal operation.

4) An issue with the Atheros driver on RedHat Enterprise 3 may 
   infrequently cause Odyssey Client to display 'adapter not available'
   in the Connection panel.  This must be resolved by rebooting the
   operating system.