Linux wireless networking development ()

Pavel Roskin | 30 Jan 23:54

Getting dscape running

On Tue, 2007-01-30 at 17:36 -0500, Jon Smirl wrote:
> Here's the same rt2570 device using the ifconfig commands. I was
> trying to get NetworkManager running on it in case it was doing
> something that I wasn't doing manually. Some is not quite right with
> the WEP exchange.
> 
> jonsmirl at jonsmirl:/extra/wireless-dev/net/d80211$ iwconfig
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> wmaster0  IEEE 802.11g  Frequency:2.412 GHz
>           RTS thr:off   Fragment thr=2346 B
> 
> wlan0     IEEE 802.11g  ESSID:""
>           Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
>           RTS thr:off   Fragment thr=2346 B
>           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
> 
> jonsmirl at jonsmirl:/extra/wireless-dev/net/d80211$ sudo iwconfig wlan0 channel 1
> jonsmirl at jonsmirl:/extra/wireless-dev/net/d80211$ sudo iwconfig wlan0
> key F491B8B905
> jonsmirl at jonsmirl:/extra/wireless-dev/net/d80211$ sudo iwconfig wlan0
> essid Smirl
> jonsmirl at jonsmirl:/extra/wireless-dev/net/d80211$ sudo iwconfig wlan0
> ap 00:11:95:18:15:31

It would be interesting to look at the iwconfig output at this point.

(Continue reading)

headers

Jon Smirl | 31 Jan 01:19

Getting dscape running

On 1/30/07, Pavel Roskin <proski at gnu.org> wrote:
> > I'm unable to connect to it using WEP. The same device works on the Intel stack.
>
> And how about connections without WEP?
>
> > wmaster0: TX to low-level driver (len=26) FC=0x00a0 DUR=0x013a
> > A1=00:11:95:18:15:31 A2=00:15:e9:2d:76:57 A3=00:11:95:18:15:31
> > wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
>
> My understanding of the code that prints the above is that either the AP
> doesn't support WEP or the client doesn't have WEP enabled.  That can
> include the case when some other encryption algorithm is active.

I think I've located what the problem is. NetworkManager was hanging
around as a deamon and changing my encryption settings improperly
probably because of the NULL gobject problem. I fixed my system to not
run NM, rebooted and now I can connect.

> Just in case, please make sure your .config enables CONFIG_CRYPTO_ECB
> and CONFIG_CRYPTO_ARC4.
>
> --
> Regards,
> Pavel Roskin
>
>
>

--

-- 
Jon Smirl

(Continue reading)

headers

Michael Wu | 31 Jan 01:16

Getting dscape running

On Tuesday 30 January 2007 17:54, Pavel Roskin wrote:
> Just in case, please make sure your .config enables CONFIG_CRYPTO_ECB
> and CONFIG_CRYPTO_ARC4.
d80211 selects ARC4. ECB is selected too if you have Linville's last update.

-Michael Wu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.tuxdriver.org/pipermail/wireless/attachments/20070130/6406fefd/attachment.pgp

headers

Jon Smirl | 31 Jan 01:09

Getting dscape running

On 1/30/07, Pavel Roskin <proski at gnu.org> wrote:
> > I'm unable to connect to it using WEP. The same device works on the Intel stack.
>
> And how about connections without WEP?
>
> > wmaster0: TX to low-level driver (len=26) FC=0x00a0 DUR=0x013a
> > A1=00:11:95:18:15:31 A2=00:15:e9:2d:76:57 A3=00:11:95:18:15:31
> > wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
>
> My understanding of the code that prints the above is that either the AP
> doesn't support WEP or the client doesn't have WEP enabled.  That can
> include the case when some other encryption algorithm is active.

I think I've located what the problem is. NetworkManager was hanging
around as a deamon and changing my encryption settings improperly
(turning off WEP) probably because of the NULL gobject problem. I
fixed my system to not run NM, rebooted and now I can connect. I'll
just get rid of NM since it is not needed for my application. Turning
off encryption gave me enough clues to blame NM.

>
> Just in case, please make sure your .config enables CONFIG_CRYPTO_ECB
> and CONFIG_CRYPTO_ARC4.
>
> --
> Regards,
> Pavel Roskin
>
>
>

(Continue reading)