Next-in-Thread Next Message

Question Windows-2-Linux communication problems 

Forum: PCMCIA Wireless Network Adapter Issues
Date: 2000, Aug 06
From: Andrew Fernandes <>

I have three Lucent WaveLan/IEEE Gold cards, all with firmware-6.06. I use two of the cards in latops under win95 and win2k, and have no problems.

My linux box uses the VG469 ISA bridge, and the wvlan_cs driver *seems* to be working correctly. All the iwconfig commands work flawlessly, I can set/get all card parameters, and readling through the output of "pc_debug=65535" shows nothing out of the ordinary occurring.

I'm using Red Hat's 2.2.16 kernel, modified with pcmcia-cs-3.1.19.

Heck, if I tcpdump the wireless ethernet port, the transmition of the "arp-who-has" messages coincides precisely with the little flashing light on the pc-card. So, as far as I can tell, the card is working just fine.

The problem is that linux and the windoze boxen cannot communicate at all. They do not appear in the slightest on each other's radar. I have fiddled very carefully with every combination of ESSID (on or off), encryption, frequency, mode, bit rate, etc., etc., etc. that I can, on both the linux box and the windoze boxen, and the OSes completely ignore each other.

Communication is always swell between the windozen.

It doesn't matter if I rotate cards among machines.

A sample output of iwconfig is as follows. The essid, nickname, frequency, mode... etc. all can be changed quite flawlessly with iwconfig.

 eth2     IEEE 802.11-DS  ESSID:"Studio20"  Nickname:"Herbie"
          Frequency:2.457GHz  Sensitivity:1/3  Mode:Ad-Hoc  
          Access Point: 00:00:00:00:00:00
          Bit Rate:2Mb/s   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  invalid crypt:0  invalid misc:0

Notice that everything from "link quality" onwards is zero. Those numbers never change, no matter how many hundreds of packets that ifconfig reports have gone out over the interface. Ifconfig always reports zero Rx packets on the interface.

On the windows side, the "network spy" utilites refuse, no matter what settings I use, to see or recognize the linux box in any way.

I very, very rarely get (from the wvlan_cs driver)

 wvlan_cs: eth2 Tx timed out! Resetting card 

messages. These do not fill me with happiness. I don't seem to have interrupt conflicts, though... from the dmesg file:

 Linux PCMCIA Card Services 3.1.19
   kernel build: 2.2.16-4 #1 Thu Aug 3 11:12:13 EDT 2000
   options:  [pci] [cardbus] [apm] [pnp]
 PCI routing table version 1.0 at 0xf0d10
 PnP: PNP BIOS installation structure at 0xc00fd110
 PnP: PNP BIOS version 1.0, entry at f0000:d140, dseg at f0000
 Intel PCIC probe: 
   Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00
     host opts [0]: none
     host opts [1]: none
     ISA irqs (default) = 11 polling interval = 500 ms
 cs: IO port probe 0x0c00-0x0cff: clean.
 cs: IO port probe 0x0800-0x08ff: clean.
 cs: IO port probe 0x0100-0x04ff: clean.
 cs: memory probe 0x0d0000-0x0dffff: clean.
 wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.4
 wvlan_cs: (c) Andreas Neuhaus <>
 wvlan_cs: index 0x01: Vcc 5.0, irq 11, io 0x0100-0x013f
 wvlan_cs: Registered netdevice eth2
 wvlan_cs: Valid channels: 1 2 3 4 5 6 7 8 9 10 11 
 wvlan_cs: MAC address on eth2 is 00 60 1d f2 cb 55  

I have only two hints about what may be going on, but I don't know what they mean.

1) For the 21-July driver release from Lucent (NDIS 3 miniport driver 6.14, firmware 6.06), using a Point-to-Point network with a blank network-id causes the windoze drivers to lock up on both 95 and 2k. However, locking up the windows drivers sometimes makes the linux driver count a few "invalid misc" packets. This is the ONLY way I can get any received packets on the linux driver.

2) I tried using Lucent's wavelan2_cs driver (6.02)... it compiles and installs into the kernel just fine... but after the module initializes, the module hangs. Compling with debugging, and turning on full debugging gives me nothing more than an initialization string in "dmesg". The wvlan_cs driver has no problem getting the wireless ether device up and running... The inability to properly initialize may be a hint that Andy's wvlan_cs driver may only SEEM to be functioning properly... who knows?

I'd be happy to provide (a) pizza, or (b) beer, if someone can help me figure this one out.

Many thanks,


Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 3 All

1. Sad Ad-Hoc mode by Jean Tourrilhes, 2000, Aug 08
2. More Silly Lucent by Andrew Fernandes, 2000, Aug 09
3. News The problem is in Cardmgr! by Andrew Fernandes, 2000, Aug 28
1. More 'Twas a buffer overflow error... by Andrew Fernandes, 2000, Aug 31

Add Message to: "Windows-2-Linux communication problems"

Members Subscribe Admin Mode Show Frames Help for HyperNews at 1.10