| View previous topic :: View next topic |
| Author |
Message |
eniac
Apprentice
Joined: 11 Aug 2003
Posts: 233
Location: Belgium, Brussels
|
 Posted: Sun May 23, 2010 2:02 pm Post subject: |
 |
|
I'm also using the broadcom-sta driver.
And having some trouble setting up a connection.
I always get the CTRL-EVENT-DISCONNECTEd - Disconnect event - remove keys message in wpa_cli.
If I understood the latest post in this thread I should stop using TKIP and switch to something else ?
_________________
Turns out the pony only had one trick. |
|
| Back to top |
|
 |
pappy_mcfae
Watchman
Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.
|
| Posted: Sun May 23, 2010 8:00 pm Post subject: |
|
|
You need not do such things. The broadcom-sta driver is not where TKIP comes into play. That is taken care of via wpa_supplicant. If you have the kernel set to where broadcom-sta will finish compilation, that is all you need.
As to the question of dropping connections, that can happen with any driver. It is less likely to happen using ndiswrapper and tweaking the .conf file that sets the driver's default operating characteristics. But it still happens.
Just for grins, post your /etc/conf.d/net file.
Cheers,
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols. |
|
| Back to top |
|
|
wormite
n00b
Joined: 05 Apr 2010
Posts: 19
|
| Posted: Mon May 24, 2010 5:53 pm Post subject: |
|
|
| pappy_mcfae wrote: | You need not do such things. The broadcom-sta driver is not where TKIP comes into play. That is taken care of via wpa_supplicant. If you have the kernel set to where broadcom-sta will finish compilation, that is all you need.
As to the question of dropping connections, that can happen with any driver. It is less likely to happen using ndiswrapper and tweaking the .conf file that sets the driver's default operating characteristics. But it still happens.
Just for grins, post your /etc/conf.d/net file.
Cheers,
Pappy |
I do not know exactly how the TKIP functionality is divided between wpa_supplicant and the broadcom-sta driver, but to me it is obvious that broadcom-sta driver has a part that is dealing with tkip:
| Code: | wl/sys/wl_linux.c: if (wl->tkip_bcast_data[key->id]) {
wl/sys/wl_linux.c: wl->tkipmodops->deinit(wl->tkip_bcast_data[key->id]);
wl/sys/wl_linux.c: wl->tkip_bcast_data[key->id] = NULL;
wl/sys/wl_linux.c: // if (!wl->tkip_bcast_data) {
wl/sys/wl_linux.c: // //wl->tkip_bcast_data = wl->tkipmodops->init(key->id);
wl/sys/wl_linux.c: // wl->tkip_bcast_data[key->id] =
wl/sys/wl_linux.c: // wl->tkipmodops->init(key->id);
wl/sys/wl_linux.c: // if (wl->tkip_bcast_data) {
wl/sys/wl_linux.c: // wl->tkipmodops->set_key(&key->data, key->len,
wl/sys/wl_linux.c: // (uint8 *)&key->rxiv, wl->tkip_bcast_data);
wl/sys/wl_linux.c: // if (wl->tkip_bcast_data) {
wl/sys/wl_linux.c: // wl->tkipmodops->deinit(wl->tkip_bcast_data);
wl/sys/wl_linux.c: // wl->tkip_bcast_data = NULL;
wl/sys/wl_linux.c: if (!wl->tkip_ucast_data) {
wl/sys/wl_linux.c: wl->tkip_ucast_data = wl->tkipmodops->init(key->id);
wl/sys/wl_linux.c: if (wl->tkip_ucast_data) {
wl/sys/wl_linux.c: wl->tkipmodops->set_key(&key->data, key->len,
wl/sys/wl_linux.c: (uint8 *)&key->rxiv, wl->tkip_ucast_data);
wl/sys/wl_linux.c: if (wl->tkip_ucast_data) {
wl/sys/wl_linux.c: wl->tkipmodops->deinit(wl->tkip_ucast_data);
wl/sys/wl_linux.c: wl->tkip_ucast_data = NULL;
|
This part has undergone huge changes between 5.10.91 and 5.60.48.36. The last reported working version of driver for BCM4322 is 5.10.91.
http://en.gentoo-wiki.com/wiki/Dell_Latitude_E6x00#Broadcom
I tried to merge the two versions to find out what the problem is. I am just guessing that the tkip part can be an important factor since when I downgraded to 5.10.91 and switched to
CCMP everything worked. |
|
| Back to top |
|
|
pappy_mcfae
Watchman
Joined: 27 Dec 2007
Posts: 5999
Location: Pomona, California.
|
| Posted: Mon May 24, 2010 7:41 pm Post subject: |
|
|
Having worked with the broadcom-sta for some time, I've never seen this issue. Since I recently found out that ndiswrapper has been placed back among the functional, I stopped using braodcom-sta. I didn't do it because the broadcom-sta was problematic. I did it because ndiswrapper works so much better.
The kernel settings required to make ndiswrapper finish compilation are also the same as broadcom-sta, and kernel-based TKIP, etc. are not among those settings. Those things are best left to wpa_supplicant.
Cheers,
Pappy
_________________
This space left intentionally blank, except for these ASCII symbols. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
