The firmware supports WEP, but it is configured differently than
version 0.8 and later, and I've never managed to work out how to
properly activate it.
> If I change the line to enable the WEP for fw 7, I get mixed
> results in 2.4.19-pre6:
>
> - I can ping, but I cannot telnet.
> - My dmesg is full of
> eth1: Null event in orinoco_interrupt!
That's unrelated, due to a shared interrupt.
> and ocassionally I get
> eth1: Undecryptable frame on Rx. Frame dropped.
> - when I ping I seem to get double replies sometimes (depending
> on who I ping - never for the access point, always for another
> client) - either I am somehow seeing both the packet from
> the client to the AP and from AP to me, or there is some
> problem in the receiving routines
>
> Does the driver support interrupt sharing? I have quite a lot
> devices on the PCI bus, the plx board is not able to get
> a dedicated interrupt and shares it with the USB controller.
> I have a SMP board, which can be a factor too.
Yes it does, except for that "Null event" message which is gone in
more recent versions (not yet pushed to Linus and Marcelo).
> Anyway, if I can ping and see the traffic of another clients
> using tcpdump, the has_wep check is obviously too strict.
> I would suggest to either lower the requirement to firmware 7,
> or (if this is an exception and another cards are different)
> to add a module parameter to override it.
Yes, but the interface doesn't actually work properly.
-- David Gibson | For every complex problem there is a david@gibson.dropbear.id.au | solution which is simple, neat and | wrong. -- H.L. Mencken http://www.ozlabs.org/people/dgibson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/