Hi Guys,
I'm not so pretty sure if I'm right here but at least it's related to
networking.
Here comes the story. Recently I have bought a WLAN setup consisting of a
PCI card SMC 2802W V2 (V2, I assume) and a PCMCIA D-Link DWL-G650+. I
don't have a
access point and I'm actually not willing for buing one.
The SMC 2802W is plugged into my Linux router (Debian Sarge, Kernel
2.6.11.8).
Unfortunately this SMC card is not supported by the Prism54 driver,
although
I checked the supported cards for this driver, I didn't knew at this time
that
there are quite a bunch of different subversions of this card on the
market.
Anyhow, I would barly be able to check the subversion of any hardware
before
I have bought it.
So currently I'm using Ndiswrapper, a pretty new version, a few days old.
I configured my wlan0 in Ad-hoc mode, since I want to connect my notebook
to my
Linux router via my WLAN setup. Right after the start of ndiswrapper
everything
works fine, I get a connection, I get access to the Internet, and so on.
But, and finally I come to the point, when I shut down my notebook and by
this
of course disconnect from my Linux machine I won't be able to reconnect
later on.
For some reason the SMC card shuts down it's transmitter (I assume), since
I do see packages
arrive on the Linux router, wlan0 rx counter increases, but there is not a
single
package going out, at the notebook nothing arrives.
To reenable my WLAN I have to unload the ndiswrapper and reload it again,
with exact
the same configuration as before, then everything works fine again until I
disconnect
my notebook.
Do you guys have any idea on how I can overcome this anoying behaviour?
Any suggestions are highly appreciated.
Servus Daniel
--
Using Opera's revolutionary e-mail client:
http://www.opera.com/mail/