chima

[Log in to get rid of this advertisement]

Works like discribed above, but using WEP YaST seems to ignore the settings for wlan0. So you have to set it up manually. Take the following steps in order:

- /usr/sbin/iwconfig wlan0 key restricted <key>
if you want to give the ASCII-key the prefix s: is necessary

- /usr/sbin/iwconfig wlan0 essid "<ESSID>"

- /sbin/ifconfig wlan0 up <IP-Addr.>

Didn't try without encryption.
Have fun...

cck23

I finally got my wireless D-Link650+ card to work after many hours of heartache and debugging. I thought I would share experiences with you all so hopefully you wont have to go through the same thing

first, following the instructions on:

http://www.linuxquestions.org/hcl/showproduct.php?product=1125

this page is specifically for dlink650+ but the principles should be the same for any wireless card you intend to use via ndiswrapper

The other thing you may need to install is "wireless tools". This is included with the CDs of my dist Mandrake 10 though I had to manually intall it. This gives you access to commands like iwconfig, iwlist, iwactivity...

Follow the steps in above link to configure ndiswrapper and your card.

Assuming you have ndiswrapper installed and configured for you card, you should get a device like wlan0 when you run "ifconfig -a"

There are two cases and I realised that not both worked, ie. no matter what you do, if you get case 1 when you plug your card in it's not going to work (well, it's fairer to say I could not get it to work):

FIRST (CASE 1)
==============
wlan0 Link encap:Ethernet HWaddr 00:80:C8:2C:7F:08
inet6 addr: fe80::280:c8ff:fe2c:7f08/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:308 (308.0 b)
Interrupt:11 Memory:20820000-20821ff

SECOND (CASE 2)
===============
wlan0 Link encap:Ethernet HWaddr 00:80:C8:2C:7F:08
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Memory:20820000-20821fff

The main difference between case 1 and case 2 is that case 1 picks the device as inet6 and link is up.

In case 1, I found any iwconfig commands were being accpeted but then deleted straight away (realised this using a while loop to run iwlist wlan0 key every one second)

In Case 2 though, the iwconfig commands were being accepted, hence enabling me to set the ESSID and keys so that I could connect successfully

However, this is all very well and it helps me connect successfully but could anyone explain why Case 1 and Case 2 are different?

Thanks

I have given this a compatibility rating of 5/10 which is still good but not perfect due to the way my card is detected when i push it in, though this might be down to user knowledge which i am willing to accept if anyone wants to point out the root cause

CK

iceman47

Forget about ndiswrapper, there _are_ drivers for this card:
http://acx100.sourceforge.net/
Encryption doesn't work yet, use stunnel ;)

kersten78

Follow the directions above. Ndiswrapper is simple if you follow the INSTALL file. For me, ndiswrapper .10 and .09 worked perfectly. One thing to take note of:
If you write a script to activate the card on boot, make sure to add a pause after modprobe. I added a "sleep 6" command after the modprobe and then continued with my iwconfig settings, and it works every time. Without the sleep command, my iwconfig settings would not take. For some reason, the ndiswrapper module is slow to load. Good luck, and PM me if you have any questions.
-Kris

toxiq

even in case 2, that member cck23 describes above, I still can't make it work. I set up the key, and as soon as I set up the correct ESSID the linux hangs/crashes. When I check the access point (DWL-2000AP+) log I can see that the card connected to the AP. I've tried god knows how many combinations but nothing changes. If ESSID is any/off, it shows the "missing link, check cable?" error. If I have the correct settings on the bootup I can actually see an "kernel panic" error (and alot of debug info) when its bringing up interface wlan0. If anyone has heard of a problem like this please help me, any ideas are welcome.

b.t.w. the card works perfect under windowsxp.

-toxiq

aaron.browne

In the end it seemed so easy. I required WPA for work purposes.

* Download and install ndiswrapper-1.1rc1
* Download Windows XP drivers for DWL-G650+ from dlink.com.au
(DWL-G650+Driver2.02.zip)

* Setup ndiswrapper and load module
- ndiswrapper -i WinXP/GPLUS.inf
- modprobe ndiswrapper

* Configure wireless device and scan for access point.
- iwconfig wlan0 essid <SSID>
- iwlist wlan0 scan

* Download, configure and install wpa_supplicant
* Activate wlan0 and start wpa_supplicant
- ifconfig wlan0 up
- wpa_supplicant -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf -B

These are a compressed form of the instructions available on the
ndiswrapper and wpa_supplicant web sites.

Overall I found the 2.6 kernel to be far more reliable when loading
this particular device. Sometimes when loading the ndiswrapper
module under 2.4 the device would not be initialised correctly.

exit3219

Works without ndiswrapper, with the acx module (in the kernel by default). Many have said that this driver doesn't support WEP. It *does*, maybe it was introduced in a recent version. Tried only in Ad-Hoc mode, with WEP encryption ON. Not quite satisfied by the range, but this is my first wireless product so maybe I just expected too much. Another drawback is that it gets uncomfortably hot in my notebook.

/etc/network/interfaces entry:
auto wlan0
iface wlan0 inet static
address 192.168.xxx.xxx
netmask 255.255.255.0
gateway 192.168.xxx.xxx
dns-nameservers 192.168.xxx.xxx
wireless-essid xxxxxxxxx
wireless-key s:xxxxx
wireless-mode Ad-Hoc

Don't forget to specify the "s:" flag for wireless-key, if you want to provide the key in ASCII!

ChickenFeed

I got the PCMCIA version (REV B) of this card to work in my old Packardbell laptop using the Linuxant "driverloader" module.

http://www.linuxant.com/driverloader/wlan/full/

All the driver files (.inf .sys and .bin's) I took from the origional CD but you can also download them from D-Link.

bolt_thrower

This card worked for me after some problems.

I managed to get WPA-PSK working under Slackware 12.1. Here are steps:

1. Install ndiswrapper with Windows driver (I use 2004 version). Installation is very simple.
2. Set broadcast SSID option on your router
3. Install wpa_supplicant and configure /etc/wpa_supplicant.conf (some options may not be necessary, but this file works for me):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network{
ssid="mysessid"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk=<hexadecimal output from wpa_passphrase>
}

4. Configure /etc/rc.d/rc.inet1.conf
IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
WLAN_WPA[4]="wpa_supplicant"
#WLAN_WPADRIVER="ndiswrapper" - did not worked for me;(
WLAN_WPADRIVER="wext"

5. Configure /etc/rc.d/rc.wireless.conf
# comment out section below
#*)
# INFO="Any ESSID"
# ESSID="any"
# ;;
# beginning of MAC address of DLINK card
00:11:95:*)
INFO="D-Link DWL-G650+"
ESSID="mysessid"
NWID=""
MODE="Managed"
FREQ=""
CHANNEL="6"
SENS=""
RATE="auto"

The biggest problem for me was using ndiswrapper as driver form wpa_supplicant. It worked perfectly after setting it to "wext"