As I explain in my howto, each Wavelan IEEE driver has
its strength and its weakness...
> One has to do with the wavelan2_cs driver from lucent. It
> misreports the link quality stats.
Wireless Extensions are far more advanced in wvlan_cs,
and I know that many neat WE features are not implemented in
wavelan2_cs. It's just the case of cut'n'paste my code from
one driver to another, but it seem that nobody at Lucent is
able to do this simple task...
> The second problem has to do with the wvlan_cs driver, I can
> install the module, but can't bring up any interface
> using ifconfig. Neither 'eth1' (or eth0) nor 'wvlan0' are
> recognized. I keep getting the following message (when I
> specify a IP address):
There are known issues with firmware 6.X, but it
should work with firmware 4.X. Please try to use wvlan0 as the
interface name, and give us a lot more info on what's
happening (like messages in the log).