no connection with DWL-520 using linux-wlan-nx driver

das111 · 10-16-2004, 04:53 PM

I just installed the Linux-wlan-ng driver for my DWL-520(b2) PCI card on Fedora Core 2. I can't seem to get a connection established to my network. When I ping it says there is no connection.

Where I have looked for help:
I ran through the instructions for configuring in the README (found ftp.linux-wlan.org/pub/linux-wlan-ng/ ) and looked through the FAQ and I can't quite figure it out. I have also been involved in the Fedoraforum.com and linuforums.org sites trying to figure it out. Those forums appear to be less active than this one and so I hope we can get a solution here. FYI - I have been using Linux for a week, so am not familiar with too much, but I do know how to change directories, edit files, login as root and a few basics like that.

Since the Read me says Linux-wlan-ng does not fully implement the wireless extensions interface we can't use iwconfig and its kin to set things up. It does give some instructions, but I had 2 problems in following them.

Possible suspects:
1. The read me says to make sure that the drivers get loaded at boot time and that the necessary initialization takes place by adding the following commands to the rc.local file:

Code:

modprobe prism2_pci
     wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
     wlanctl-ng wlan0 lnxreq_autojoin ssid=<your APs SSID> authtype=opensystem
     ifconfig wlan0 <yourIP> netmask <yourNetmask> broadcast <yourBroadcast>
     route add default gw <yourGateway>

since I have WEP enabled and my IP is dynamic I changed it and left out a bit like this:

Code:

modprobe prism2_pci
     wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
     wlanctl-ng wlan0 lnxreq_autojoin ssid=hazar (this is my network ssid)
     authtype=sharedkey

Should I have done something different for the ifcong part - as opposed to leaving it off? My router's IP address (default gateway?) is 192.168.0.1 and the subnet mask is 255.255.255.0, but I would not know what to put for my broadcast and my IP.

2. Read me says to add an alias for wlan0 in /etc/modules.conf.

Code:

   alias wlan0 prism2_pci

When I tried to do this I had to create the file /etc/modules.conf - so it is completely empty other than the alias I put there.

I actually had someone else tell me this alias had to be in the modprobe.conf file too - is that right?

3. When I boot in Fedora I get Kudzo asking me about setting up new hardware - this happened since I had tried to use the Network Devices tool to set up the card and then I deleted that configuration. Now the device eth1 (prism2.5 chipset - this wireless card) is listed under network hardware, but wlan0 does not show up. Should I set up the device using kudzo - or tell it to ignore it?

4. My network is filtered by MAC address. Is the MAC address for this card gonna be the same in XP and Linux?

I am trying to give what might be useful, but please ask if there is anything else I could tell you to help get this thing rolling. I will be checking this several times a day. Thanks in advance for volunteering your time and knowledge.

darkleaf · 10-18-2004, 06:46 AM

4. MAC addresses are hardware addresses and are the same in windows and linux.

Also this might not be what you want but since the dirver you're using says it doesn't fully implement wireless interfaces and your card is on the ndiswrapper supported list at http://ndiswrapper.sourceforge.net/wiki/index.php/List that you try it with ndiswrapper. It's not hard and if it can get your card to work properly and you can just use the wireless commands of iwconfig.

And if you're having trouble with it it's easier to sort out because a lot of people just use ndiswrapper instead of the program you're trying to get to work.

das111 · 10-18-2004, 09:18 AM

Quote:

Originally posted by darkleaf
Your card is on the ndiswrapper supported list at http://ndiswrapper.sourceforge.net/wiki/index.php/List that you try it with ndiswrapper.

And if you're having trouble with it it's easier to sort out because a lot of people just use ndiswrapper instead of the program you're trying to get to work. [/B]

Thanks for the info. This will be my last resort - rather than ditching linux or buying a new wireless card. The reason I don't go do it right now is that I would really like to learn how to get it done since I know that it is possible.

darkleaf · 10-18-2004, 10:20 AM

Quote:

Originally posted by das111
The reason I don't go do it right now is that I would really like to learn how to get it done since I know that it is possible.

With that other driver program you're trying now? Have fun! BTW you can get your internet running in like 3 minutes with ndiswrapper. Give or take some when editing stuff to do it on boot as well, or a bit longer if you're new but soon nonetheless.

das111 · 10-18-2004, 01:21 PM

I know at least 2 people that got it to work with the linux-wlan-ng prism2_pci driver, so it can be done, but I guess if no one is able to help me then I will have to resort to using ndiswrapper. I just thought it would be cool to keep it all open source and linux native.

das111 · 10-18-2004, 01:35 PM

I was looking at that list and do not see my card on there anyway.
I find the D-Link DWL-G520, DWL-G520+, and D-Link DWL-520+. This card uses the Prism 2.5 chipset.

das111 · 10-20-2004, 11:43 PM

I guess I was wrong about this forum being more active. Maybe I used a bad subject line?

The ndiswrapper does not work with my card, a DWL-520 (b2), so no one has offered any useful advice so far.

darkleaf · 10-21-2004, 04:14 AM

Have you tried using ndiswrapper with your card. It just might be that your card hasdn't been recognised as supported yet.

And like I said not many people use the driver you say around here and it isn't very busy.

das111 · 10-21-2004, 07:52 AM

I'll give it a shot, probably tomorrow. I'll let you know if it works.