Gentoo Archives: gentoo-user

From: Drew Tomlinson <drew@××××××××××××××.net>
To: Gentoo User <gentoo-user@l.g.o>
Subject: [gentoo-user] Trouble Getting Wireless Networking Configured
Date: Wed, 27 Jun 2007 01:44:47
Message-Id: 4681BFB0.7080607@mykitchentable.net
1 I have a Gateway 6454 laptop with 2.6.21-gentoo-r3 amd64 kernel running.
2 I am trying to set up the wireless network. I have never done this
3 before so I started with the Handbook's Wireless Networking section. I
4 begin by attempting to figure out what network card I have. lspci
5 reports the wireless network chip as:
6
7 05:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan
8 mini-PCI (rev 01)
9
10 Thus it seems the bcm43xx driver is what I need. I selected it to
11 compile as a module with DMA+PIO transfer mode selected. Along with it,
12 I compiled:
13
14 <M> Generic IEEE 802.11 Networking Stack
15 --- IEEE 802.11 WEP encryption (802.1x)
16 <M> IEEE 802.11i CCMP support
17 <M> IEEE 802.11i TKIP encryption
18 <M> Software MAC add-on to the IEEE 802.11 networking stack
19
20 I wasn't sure exactly what I needed so I compiled all as modules and
21 loaded all. My though was that once I had it working, I would remove
22 modules to see what I really needed.
23
24 Googling revealed something about cutting firmware. Thus I emerged
25 bcm43xx-fwcutter and followed some tidbits I found on the web about how
26 that worked. First I grabbed the latest Windows driver and copied
27 bcmwl564.sys (since I am using an amd64 kernel). When running
28 bcm43xx-fwcutter -i bcmwl564.sys, I got the following error/output:
29
30 *** WARNING ***
31 This file contains new version4
32 firmware. v4 firmware is _not_ supported by
33 the driver in mainline kernels. For v4 firmware
34 you need latest bcm43xx development version
35 (wireless-dev kernel tree). If you don't know what
36 this warning is about, use a 3.xx.xx.xx driver version
37 instead to extract the firmware.
38
39 Well I couldn't find a version 3 driver and I have no idea how to use
40 the "wireless-dev kernel tree" even after Googling for another hour.
41 However I did find a Linux driver for the BCM43xx named "wl_apsta.o" but
42 I really don't know much about it. Thus I extracted firmware from that
43 and copied it to /libs/firmware. An 'ifconfig eth1 up' and now I was
44 able to get the wireless card recognized:
45
46 eth1 Link encap:Ethernet HWaddr 00:14:A5:FC:3B:B2
47 UP BROADCAST MULTICAST MTU:1500 Metric:1
48 RX packets:2 errors:0 dropped:29319 overruns:0 frame:0
49 TX packets:91345 errors:0 dropped:0 overruns:0 carrier:0
50 collisions:0 txqueuelen:1000
51 RX bytes:184 (184.0 b) TX bytes:4141799 (3.9 Mb)
52 Interrupt:17
53
54 Anyway, next I continued following the Gentoo Handbook on Wireless
55 Networking
56 (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4),
57 specifically the WPA Supplicant section. Here's the contents of the
58 files I created pursuant to that page:
59
60 tagalong ~ # cat /etc/conf.d/net
61 # From http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=4&chap=4
62 # Prefer wpa_supplicant over wireless-tools
63 modules=( "wpa_supplicant" )
64
65 # It's important that we tell wpa_supplicant which driver we should
66 # be using as it's not very good at guessing yet
67 wpa_supplicant_eth1="-Dwext"
68
69 tagalong ~ # cat /etc/wpa_supplicant/wpa_supplicant.conf
70 # The below line not be changed otherwise we refuse to work
71 ctrl_interface=/var/run/wpa_supplicant
72
73 # Ensure that only root can read the WPA configuration
74 ctrl_interface_group=0
75
76 # Let wpa_supplicant take care of scanning and AP selection
77 ap_scan=1
78
79 # This is a network block that connects to any unsecured access point.
80 # We give it a low priority so any defined blocks are preferred.
81 network={
82 key_mgmt=NONE
83 priority=-9999999
84 }
85
86 network={
87 ssid="DrewNet"
88 key_mgmt=NONE
89 key_mgmt=NONE
90 wep_key0="ffffffffff" # not the real keys - but then it's WEP so
91 wep_key1="ffffffffff" # am I hiding them? :)
92 wep_key2="ffffffffff"
93 wep_key3="ffffffffff"
94 wep_tx_keyidx=0
95 priority=5
96 }
97
98 Now when I fire up wpa_supplicant, it seems to associate:
99
100 wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -ieth1 -d
101 Initializing interface 'eth1' conf
102 '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'default'
103 ctrl_interface 'N/A' bridge 'N/A'
104 Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' ->
105 '/etc/wpa_supplicant/wpa_supplicant.conf'
106 Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
107 ctrl_interface='/var/run/wpa_supplicant'
108 ctrl_interface_group='0' (DEPRECATED)
109 ap_scan=1
110 Priority group 5
111 id=0 ssid='DrewNet'
112 Initializing interface (2) 'eth1'
113 EAPOL: SUPP_PAE entering state DISCONNECTED
114 EAPOL: KEY_RX entering state NO_KEY_RECEIVE
115 EAPOL: SUPP_BE entering state INITIALIZE
116 EAP: EAP entering state DISABLED
117 EAPOL: External notification - portEnabled=0
118 EAPOL: External notification - portValid=0
119 SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
120 capabilities: key_mgmt 0xf enc 0xf
121 WEXT: Operstate: linkmode=1, operstate=5
122 Own MAC address: 00:14:a5:fc:3b:b2
123 wpa_driver_wext_set_wpa
124 wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
125 wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
126 wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
127 wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
128 wpa_driver_wext_set_countermeasures
129 wpa_driver_wext_set_drop_unencrypted
130 RSN: flushing PMKID list in the driver
131 Setting scan request: 0 sec 100000 usec
132 ctrl_interface_group=0
133 Added interface eth1
134 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
135 Wireless event: cmd=0x8b06 len=12
136 State: DISCONNECTED -> SCANNING
137 Starting AP scan (broadcast SSID)
138 Trying to get current scan results first without requesting a new scan
139 to speed up initial association
140 Received 268 bytes of scan results (1 BSSes)
141 Scan results: 1
142 Selecting BSS from priority group 5
143 Try to find WPA-enabled AP
144 0: 00:0f:b5:17:d7:fc ssid='DrewNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
145 skip - no WPA/RSN IE
146 Try to find non-WPA AP
147 0: 00:0f:b5:17:d7:fc ssid='DrewNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
148 selected non-WPA AP 00:0f:b5:17:d7:fc ssid='DrewNet'
149 Trying to associate with 00:0f:b5:17:d7:fc (SSID='DrewNet' freq=2412 MHz)
150 Cancelling scan request
151 WPA: clearing own WPA/RSN IE
152 Automatic auth_alg selection: 0x1
153 WPA: clearing AP WPA IE
154 WPA: clearing AP RSN IE
155 WPA: clearing own WPA/RSN IE
156 No keys have been configured - skip key clearing
157 wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=10
158 wpa_driver_wext_set_key: alg=1 key_idx=1 set_tx=0 seq_len=0 key_len=10
159 wpa_driver_wext_set_key: alg=1 key_idx=2 set_tx=0 seq_len=0 key_len=10
160 wpa_driver_wext_set_key: alg=1 key_idx=3 set_tx=0 seq_len=0 key_len=10
161 wpa_driver_wext_set_drop_unencrypted
162 State: SCANNING -> ASSOCIATING
163 wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
164 WEXT: Operstate: linkmode=-1, operstate=5
165 wpa_driver_wext_associate
166 Setting authentication timeout: 10 sec 0 usec
167 EAPOL: External notification - portControl=ForceAuthorized
168 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
169 Wireless event: cmd=0x8b06 len=12
170 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
171 Wireless event: cmd=0x8b04 len=16
172 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
173 Wireless event: cmd=0x8b1a len=23
174 RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
175 Wireless event: cmd=0x8b19 len=16
176
177 OK, so good. Now I issue a DHCP request as so:
178
179 tagalong ~ # dhcpcd -dd eth1
180 Info, eth1: dhcpcd 3.0.17 starting
181 Info, eth1: hardware address = 00:14:a5:fc:3b:b2
182 Info, eth1: broadcasting for a lease
183 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
184 Debug, eth1: waiting on select for 20 seconds
185 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
186 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
187 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
188 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
189 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
190 Debug, eth1: sending DHCP_DISCOVER with xid 0x500d3c30
191 Error, eth1: timed out
192 Info, eth1: exiting
193
194 I ran tcpdump on eth1 and no packets are leaving the interface. Thus I
195 assume that's why I'm not getting an address. The DHCP server has no
196 problems with other machines on my network. The Wireless access point
197 works with other devices too. So I'm stumped. Is this related to
198 firmware? Other ideas?
199
200 I appreciate you reading this far and will gladly accept any suggestions.
201
202 Thanks,
203
204 Drew
205
206 --
207 Be a Great Magician!
208 Visit The Alchemist's Warehouse
209
210 http://www.alchemistswarehouse.com
211
212
213 --
214 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] Trouble Getting Wireless Networking Configured Randy Barlow <randy@×××××××××××××××××.com>