Forgive me if this seems like a silly question, I'm new here.
From reading this thread, I get the impression that this Kamikaze you've all been talking about is an embedded linux for a wireless router. Is that correct?
I was directed here by Pat Erley (http://wireless.erley.org/stable.html) in the hope that your patches might work for me.
In my desktop, I have a broadcom bcm4306(rev 3) PCI card that I salvaged from a dead Netcomm NB9W router. The card works fine in ad-hoc, managed and even monitor mode. I don't know what kind of radio is on the card.
My problem is that I cannot seem to get the card to work in master mode. I followed the instructions that Pat posted on his web site (above) I downloaded and installed all the software which seemed to go OK but it still doesn't work. I don't need to tell you that I need master mode to setup an AP.
When I do:
~ # hostapd -dd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
ctrl_interface_group=1
Opening raw packet socket for ifindex 0
BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits)
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
Allowed channel: mode=1 chan=1 freq=2412 MHz
Allowed channel: mode=1 chan=2 freq=2417 MHz
Allowed channel: mode=1 chan=3 freq=2422 MHz
Allowed channel: mode=1 chan=4 freq=2427 MHz
Allowed channel: mode=1 chan=5 freq=2432 MHz
Allowed channel: mode=1 chan=6 freq=2437 MHz
Allowed channel: mode=1 chan=7 freq=2442 MHz
Allowed channel: mode=1 chan=8 freq=2447 MHz
Allowed channel: mode=1 chan=9 freq=2452 MHz
Allowed channel: mode=1 chan=10 freq=2457 MHz
Allowed channel: mode=1 chan=11 freq=2462 MHz
Hardware does not support configured mode
wlan0: IEEE 802.11 Hardware does not support configured mode (0)
Could not select hw_mode and channel. (-1)
wlan0: Unable to setup interface.
rmdir[ctrl_interface]: No such file or directory
Which is really strange bcause:
~ # iwconfig wlan0
wlan0 IEEE 802.11bg Mode:Master Frequency:2.412 GHz Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
And:
~ # dmesg
input: b43-phy0 as /class/input/input5
b43 ssb0:0: firmware: requesting b43/ucode5.fw
b43 ssb0:0: firmware: requesting b43/pcm5.fw
b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 30-bit DMA initialized
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
b43-phy0 debug: Wireless interface started
b43-phy0: Radio turned on by software
b43-phy0 debug: Adding Interface type 3
b43-phy0 debug: Removing Interface type 3
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-30 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_AC_VO: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-30 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
Even stranger is if I then do:
~ # /etc/init.d/net.wlan0 start
* Starting wlan0
* Configuring wireless network for wlan0
* wlan0 connected to ESSID "Odysseus" at 00:00:00:00:00:00
* in ad-hoc mode on channel 1 (WEP disabled)
* Bringing up wlan0
* 12.0.1.1 [ ok ]
* Running postup function
Which puts the card back into ad-hoc mode, and then:
~ # ifconfig
wlan0 Link encap:Ethernet HWaddr 00:16:38:c6:b7:a8
inet addr:12.0.1.1 Bcast:12.0.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1900 (1.8 KiB)
wmaster0 Link encap:UNSPEC HWaddr 00-16-38-C6-B7-A8-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The interface wmaster0 doesn't appear until AFTER I have tried to start wlan0 manually. Hostapd doesn't create this interface when I start it, nor does it start wlan0. I noticed also that wmaster0 also has a very long hardware address. Much longer than I have ever seen for any virtual device. Could this be related to the problem?
I have tried patches from several sources but none seem to do the trick. The above was generated with the unpatched kernel drivers supplied in 2.6.28. The results from patching these drivers don't differ all that much.
Any clues? Is it possible that your patches will work for me? If so, how do I go about patching the kernel drivers? Would the easiest way would be to compile Kamikaze for x86 and then copy the compiled drivers to my /lib/kernels directories? I saw that suggested two pages back.
Regards,
Ben.
PS. sorry for such a long post ;-)
System:
3.0GHz P4
1GB RAM
Broadcom BCM4306 (rev 3) PCI
Kernel-2.6.28
Kernel-headers-2.6.28-r1
libnl-1.1-r1
hostapd-0.6.6
crda-0.9.5
iw-0.9.7
compat-wireless-2009-01-11
wireless-regdb-20081117
References:
http://hostap.epitest.fi/gitweb/gitweb. … stapd.conf
http://linuxwireless.org/en/users/Drivers/b43
http://en.gentoo-wiki.com/wiki/Wireless … ur_drivers
http://www.gentoo.org/doc/en/handbook/h … amp;chap=4
http://hostap.epitest.fi/gitweb/gitweb. … icant.conf
http://wireless.erley.org/stable.html
http://wireless.erley.org/git.html
http://wireless.kernel.org/download/
http://www.gentoo-wiki.info/Broadcom_43xx
http://aircrack-ng.org/doku.php?id=mac8 … eec7a5f6da
http://johannes.sipsolutions.net/patche … ll/LATEST/
http://linuxwireless.org/en/users/Drivers/b43/faq
http://www.myscienceisbetter.info/2008/ … eless.html
http://forum.openwrt.org/viewtopic.php?id=15443&p=3