Bugzilla – Bug 397
can't associate after changing mode
Last modified: 2005-10-03 15:35:04
You need to log in before you can comment on or make changes to this bug.
Can't associate if changing default mode(bg) to b or g. Steps: 1. Set AP to mixed mode (bg AP), without WEP 2. Associate ipw2200 v0.13 driver with AP (It is in bg mode, "iwpriv eth1 get_mode" returns 6) 3. set driver to b mode or g mode % iwpriv eth1 set_mode 2 (iwpriv eth1 set_mode 4) Verify the mode is set correctly using "iwpriv eth1 get_mode". 4. The driver is unassociated. 5. Try to associate to AP manually, still doesn't work % iwconfig eth1 essid <ESSID> key off still unassociated. 6. set driver to bg mode % iwpriv eth1 set_mode 6 The driver is associated with AP correclty.
Crystal, can you retest with 0.15, with debug=0x3fff. If it fails, please attach dmesg output.
Created an attachment (id=121) [details] dmesg output afer setting debug_level to 0x3fff Retested this on 0.15, following Crystal's steps, i found that using "iwpriv eth1 set_mode 2"will make the driver unassociated; but after "iwpriv eth1 set_mode 4",the driver is unassociated. our laptop is FC2,2.6.7 kernel,Dell D505. our AP is WRT54G. attached is the dmesg output when using "iwpriv eth1 set_mode 2" and the driver was unassociated.
sorry i made a typing mistake, my comments should be: Retested this on 0.15, following Crystal's steps, i found that using "iwpriv eth1 set_mode 2"will make the driver unassociated; but after "iwpriv eth1 set_mode 4",the driver is still associated.
fixed in version 0.16
verified in 0.16.