Thank You Dave for fast response. Looks like You have right. Unfortunately we can't upgrade from kernel 2.0.x to 2.2.x, because of shaper module. (It works not properly under 2.2.x with aliased interfaces). And I guess that to change nettools in different kernel versions is not very smart. There is some differences in 2.2.x ... Yes, wavelan2_cs is realy not old, it's old only from my viewpoint, we use it succesfully over 1 year :-). But now we need to settle two WaveLan cards in one linux box, one in ad-hoc and one in BSS mode. And this works with drivers from Andreas (according technician from Lucent Prague, CZ). On pages of Andreas stands, that his drivers should work with kernel 2.0.x ... I've tried, to use a eth=1 switch with wvlan_cs.o driver, which is designed to turn off the special naming from "wvlan0" into obvious "eth0". The result was that the driver registers no interface !!! The driver yells: wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4 wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de> wvlan_cs: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f wvlan_cs: Registered netdevice wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 wvlan_cs: MAC address on wvlan0 is 00 60 1d 04 05 93 cardmgr[47]: executing: './network start ' funny, isn't it? I need some suggestion, how to say to linux, that wvlan0 is a valid intarface. thanks again viktor@salamon.sk |
Messages