nexmon – Blame information for rev 1

Subversion Repositories:
Rev:
Rev Author Line No. Line
1 office 1 Pcmcia Wireless configuration
2 -----------------------------
3  
4 One of the most exciting things having happen after release 20
5 is the addition of Wireless Tools support in the Pcmcia init
6 scripts. Here is a quick intro on the subject...
7  
8 Pre-requisite :
9 -------------
10 o Pcmcia package with Wireless Extension support : 3.1.15 onward
11 o A driver with Wireless Extension support
12 o The tools (iwconfig and co.) installed in the /usr/local/sbin
13 or /usr/sbin
14  
15 Raylink driver :
16 --------------
17 The Raylink driver as of 1.70 doesn't support writable
18 Wireless Extensions, so enabling wireless.opts on this driver will
19 make things worse.
20 On the other hand, the latest version of the Raylink driver
21 accepts Wireless Extensions at boot time, so the procedure described
22 below will work.
23  
24 Distribution specific notes :
25 ---------------------------
26 Most modern distributions don't use wireless.opts and have
27 their own procedure for wireless configuration, which is usually
28 compatible with their configuration tools and work for non-Pcmcia
29 devices. This is documented in DISTRIBUTIONS.txt.
30 The procedure described here will work only with the original
31 Pcmcia configuration scripts. If you use a precompiled package part of
32 a distributions, this is usually not the case (see above).
33 On the other hand, if you install the Pcmcia package in source
34 form from the official Linux-Pcmcia web site, it will install the
35 proper init scripts and those instructions will apply.
36  
37 Basic support :
38 -------------
39 The file /etc/pcmcia/wireless.opts contains some templates for
40 the most common drivers. Just fill in your card configuration in the
41 template corresponding to your driver configuration.
42 Then, to activate it, you just need to remove or comment the 4
43 lines at the top of wireless.opts and restart the Pcmcia package.
44  
45 Things to take care of :
46 The options of wireless.opts will be used directly as
47 arguments of iwconfig. So, you need iwconfig, and you need to check
48 the man page of iwconfig to know how to format them.
49 A quick way to determine the correct options without
50 restarting Pcmcia is to play a bit with iwconfig directly to see what
51 is possible and what is the proper setup of the card and to copy that
52 in wireless.opts.
53 At the end of wireless.opts, there is also a generic template
54 containing all the possible options and explaining their meaning. Not
55 all of them are supported by all cards (actually, most cards support a
56 limited subset of it).
57 The current card templates are designed to match the MAC
58 address of the card. Please check that this matches with your card.
59 Also, sample describe the most common/useful options available
60 with the card, for more advance option, borrow options from the
61 template. You can also remove some options, the card will usually
62 initialise with a sane value.
63  
64 Alternatively, you can also discard the current wireless.opts
65 and replace it with a file looking like this :
66 ----------- wireless.opts ---------------------
67 case "$ADDRESS" in
68 *,*,*,*)
69 ESSID="MY_ESSID"
70 MODE="Managed"
71 ;;
72 esac
73 -----------------------------------------------
74  
75  
76 Scheme support :
77 --------------
78 The file wireless.opts fully supports schemes. This allow you
79 to define different configurations (home, work...) and to switch on
80 the fly between them.
81 The best way to explain it is to show an example.
82 Let's say you have an infrastructured setup at work (MY_WORK)
83 and an Ad-Hoc network at home (MY_HOME). Moreover, when a specific card
84 is inserted, you want it to be in Ad-Hoc mode (TEST). The work setup
85 will be the default...
86  
87 Each Wireless LAN will have the following configuration :
88 --------- wireless.opts --------------------
89 # Lucent Wavelan IEEE - Ad-Hoc mode for test card
90 *,*,*,00:60:1D:03:9F:2D)
91 ESSID="TEST"
92 MODE="Ad-Hoc"
93 FREQ="10"
94 RATE="1M"
95 ;;
96  
97 # Lucent Wavelan IEEE - Ad-Hoc mode at home
98 home,*,*,00:60:1D:*|home,*,*,00:02:2D:*)
99 ESSID="MY_HOME"
100 MODE="Ad-Hoc"
101 FREQ="5"
102 ;;
103  
104 # Lucent Wavelan IEEE - infrastructured mode at work
105 *,*,*,00:60:1D:*|*,*,*,00:02:2D:*)
106 ESSID="MY_WORK"
107 MODE="Managed"
108 KEY="s:verysecurekey"
109 ;;
110 --------------------------------------------
111  
112 Don't forget the IP configuration :
113 --------- network.opts ---------------------
114 # Wavelan IEEE : ad-hoc mode for test card
115 *,*,*,00:60:1D:03:9F:2D)
116 DHCP="n"
117 IPADDR="10.0.0.1"
118 NETMASK="255.255.255.0"
119 NETWORK="10.0.0.0"
120 BROADCAST="10.0.0.255"
121 ;;
122  
123 # Wavelan IEEE : ad-hoc mode at home
124 home,*,*,00:60:1D:*|home,*,*,00:02:2D:*)
125 DHCP="n"
126 IPADDR="10.0.1.19"
127 NETMASK="255.255.255.0"
128 NETWORK="10.0.1.0"
129 BROADCAST="10.0.1.255"
130 GATEWAY="15.0.1.1"
131 ;;
132  
133 # Wavelan IEEE : infrastructured mode at work
134 *,*,*,00:60:1D:*|*,*,*,00:02:2D:*)
135 DHCP="y"
136 ;;
137 --------------------------------------------
138  
139 Now, when you are at work you do :
140 > cardctl scheme default
141 And at home, you do :
142 > cardctl scheme home
143  
144 I guess you get the idea ;-)
145  
146 More elaborated configurations :
147 ------------------------------
148 Some people may need some more complex configurations. For
149 example, you might want to do one of the following thing :
150 o cycle through a set of schemes
151 o autodetect the proper scheme
152 There is currently no support to do that. However, the
153 Wireless Tools package contains a tool called "iwgetid" that can help
154 in this job. The source code contains some hints on how to achieve the
155 above thing.
156 If you ever write such a package, please send me the URL.
157 Good luck !
158  
159  
160 Jean <jt@hpl.hp.com>