Search Linux Wireless

Re: iwl3945 associated and _worked_ with a *wrong* essid!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I recently wrote about my iwl3945 problems - I usually
>  have to try 20-50 times before I can use a wep-encrypted access point.
>  Once the link goes up - no more problems. But getting the first
>  connection takes time.

I can testify that I have the same issue with w2k. I'm not sure how intel 
wired up their drivers package, but I usually have to wait about 1-2 minutes 
to get _any_ package back from the AP (judging from the network icon). Once I 
get the first package back (I'd guess it's a dhcp resp), i can start using the 
network.

I once picked up somehwere that this wa an issue with wither this intel chip 
of the broadcom chip I have in the Linksys AP. Either one of them was picky 
on the nitial handshake and the speed/rate used for that handshake. Waiting a 
while both ends agree to do it at 1Mbps or something and it all works from 
there.

hth,
/Anders

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux