I am newbie in OpenSuse…I am using OpenSuse 11.4…
so here is the problem
I tried to connect to an AP which unprotected - success
I tried to connect to an AP which protected (WEP-OPEN) - Could not receive any packets
I tried to connect to an AP which protected (WPA-PSK) - success
On 05/19/2011 09:36 PM, VanDerSexx wrote:
>
> Hi…
>
> I am newbie in OpenSuse…I am using OpenSuse 11.4…
> so here is the problem
> I tried to connect to an AP which unprotected - success
> I tried to connect to an AP which protected (WEP-OPEN) - Could not
> receive any packets
> I tried to connect to an AP which protected (WPA-PSK) - success
We are not clairvoyant. Could you possible enlighten us as to what device you
have? If it is a PCI device, please post the output of ‘/sbin/lspci -nn’ or
‘lsusb’ if it is USB.
On 05/19/2011 11:06 PM, VanDerSexx wrote:
>
> lwfinger;2342078 Wrote:
>> On 05/19/2011 09:36 PM, VanDerSexx wrote:
>>>
>>> Hi…
>>>
>>> I am newbie in OpenSuse…I am using OpenSuse 11.4…
>>> so here is the problem
>>> I tried to connect to an AP which unprotected - success
>>> I tried to connect to an AP which protected (WEP-OPEN) - Could not
>>> receive any packets
>>> I tried to connect to an AP which protected (WPA-PSK) - success
>>
>> We are not clairvoyant. Could you possible enlighten us as to what
>> device you
>> have? If it is a PCI device, please post the output of ‘/sbin/lspci
>> -nn’ or
>> ‘lsusb’ if it is USB.
>
> I couldn’t post the thing because no Internet, so I think this is what
> you need to see
>
>>
>> lspci command:
>> 05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
>> [Golan] Network Connection (rev 02)
>>
>> lspci -n command:
>> 05:00.0 0280: 8086: 4222 (rev 02)
>>
>
> and the router is 2wire
Yes, that was what I needed. That device supports WEP with no difficulties, thus
you have a configuration problem.
Are you aware that using a passphrase with WEP is highly likely to fail? There
are something like 6 ways to convert a phrase to a WEP key and the probability
that your AP uses the same one as Linux is quite small, particularly since
Winblow$ and Linux do not use the same conversion. Enter your connection secret
as the hexadecimal key and it should work.