unixdev.net


Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (Debian-3.1)
Page:
Section:
Apropos / Subsearch:
optional field

ray_cs(January 20, 1999)                              ray_cs(January 20, 1999)



NAME
       ray_cs - Raylink wireless LAN - PCMCIA card device driver

SYNOPSIS
       insmod     ray_cs    [essid=string]    [irq_mask=n]    [net_type=[0-1]]
       [ray_debug=[0-5]]    [phy_addr=xNNNNNNNNNNNN]    [hop_dwell=n]    [bea-
       con_period=n]   [psm=[0-1]]  [translate=[0-1]]  [country=[1-8]]  [snif-
       fer=[0-1]] [bc=[0-1]]

DESCRIPTION
       ray_cs is the low level Card Services device  driver  for  the  Raylink
       wireless  LAN  PCMCIA  adapter.  It is normally loaded automatically by
       card services  according  to  the  parameters  specified  in  /etc/pcm-
       cia/ray_cs.opts.

PARAMETERS
       essid=string
              ESS  ID  - network name to join string with maximum length of 32
              chars default value = "LINUX"


       irq_mask=n
              linux standard 16 bit value 1bit/IRQ lsb is IRQ 0, bit 1 is  IRQ
              1 etc.  Used to restrict choice of IRQ's to use.


       net_type=n
              0 = adhoc network (default) 1 = infrastructure


       ray_debug=n
              (0-5) larger values for more verbose logging.

       phy_addr=string
              string  of  12  hex  digits containing new MAC address.  must be
              started with x e.g. x00008f123456


       hop_dwell=n
              hop   dwell   time   in   Kilo-microseconds   legal   values   =
              16,32,64,128(default),256


       beacon_period=n
              Beacon period in Kilo-microseconds.
              Legal  values = 16,32,64,128,256(default) must be integer multi-
              ple of hop dwell.


       psm=n  Power save mode
              0 = continuously active
              1 = power save mode (significantly slower)


       bc=n   Power save mode
              0 = 802.11 timing
              1 = 802.11 modified timing.  Interframe spacing is  slowed  down
              for compatibility with older Breezecom access points.


       translate
              0 = no translation (encapsulate frames)
              1 = translation (default)


       country=n
              Country code
              1 = USA (default)
              2 = Europe
              3 = Japan
              4 = Korea
              5 = Spain
              6 = France
              7 = Israel
              8 = Australia


       sniffer=n
              0 = normal network interface - not sniffer (default)
              1  =  sniffer  which  can  be used to record all network traffic
              using tcpdump or similar, but no normal network use is  allowed.
              This  is  because  linux  has no knowledge of 802.11 headers and
              cannot parse them correctly.  Note that tcpdump does not  under-
              stand 802.11 headers, either so it can't interpret the contents,
              but it can record to a file.



       BUGS   ray_cs can lock the machine if the  card  is  pulled  out  while
              active.  I have never observed a crash if card is deactivated as
              follows before removal:
              ifconfig eth0 down
              The above command assumes that the Raylink card is configured as
              eth0.

              This  driver  only  does encapsulation of ethernet frames within
              802.11 frames.  Most vendors, including Raytheon, are moving  to
              a  frame  translation  method.   Translation  support  has  been
              started, but is not yet functional.

              Support for defragmenting frames is not yet tested.

              The ioctl support is incomplete.  The hardware address cannot be
              set  using  ifconfig  yet.   If  a different hardware address is
              needed,  it  may  be  set  using  the  phy_addr   parameter   in
              ray_cs.opts.


WARNING
       This  man  page describes the standalone PCMCIA drivers provided by the
       pcmcia-cs source, not the PCMCIA kernel driver support that is included
       in  the 2.4 (and later) linux kernel.  While the kernel PCMCIA code has
       the same functionality as the driver  side  of  the  standalone  PCMCIA
       package,  there are some important differences.  Therefore, some or all
       of this documentation might not apply to the kernel drivers.


AUTHOR
       Corey Thomas - coreyATworld.com

SEE ALSO
       cardmgr(8), pcmcia(5), ifconfig(8).



                                                      ray_cs(January 20, 1999)