Orinoco/Realtek 8180 interoperability problem
grungie
grungie at chez.com
Tue Jan 27 00:45:12 GMT 2004
eth1: Looks like a Lucent/Agere firmware version 6.16
I remember flashing both cards a while ago under Windows (AFAIK, there
is no way of doing it under Linux) because they only supported the
Lucent proprietary Ad-Hoc mode.
Is this firmware known to have compatibility problems with other Wi-Fi
products?
Thanks for your reply!
> On Mon, Jan 26, 2004 at 04:37:19PM +0000, grungie wrote:
>> Hello,
>>
>> I've been using two ELSA Airlancer cards under Linux for a few years
>> and recently tried to add a node to my small Wi-Fi LAN. Both ELSA
>> cards
>> are running the orinoco driver, one under 2.4.x and the other under
>> 2.6.x. Everything is fine until I try adding the Realtek 8180 Windows
>> XP machine to my Ad-Hoc network.
>>
>> Just to make sure this is not a WEP problem, I have temporarily
>> disabled encryption.
>> The funny thing is that Windows sees my WLAN, tells me it has
>> excellent
>> link quality but fails to talk to my Linux boxen (and vice versa). On
>> the Windows side, I get loads of "TX Beacon Errors" and also quite a
>> few "RX CRC Errors".
>>
>> This is the output of iwconfig on the 2.4.x box:
>>
>> eth1 IEEE 802.11-DS ESSID:"ducon" Nickname:"armada"
>> Mode:Ad-Hoc Frequency:2.457GHz Cell: 02:02:2D:0F:87:A3
>> Bit Rate:2Mb/s Tx-Power=15 dBm Sensitivity:1/3
>> Retry limit:4 RTS thr:off Fragment thr:off
>> Encryption key:off
>> Power Management:off
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:1
>> Tx excessive retries:11 Invalid misc:0 Missed beacon:0
>>
>> Any idea what's going wrong?
>
> What's the firmware version on the Linux nodes? It should show up if
> you run "dmesg" immediately after loading the driver.
>
> --
> David Gibson | For every complex problem there is a
> david AT gibson.dropbear.id.au | solution which is simple, neat and
> | wrong.
> http://www.ozlabs.org/people/dgibson
>
More information about the wireless
mailing list