DLink DWL-520 v.E1 - ANYONE?

gpeacock · #1 22nd December 2005, 05:21 PM

I can't see that anyone has gotten one of these DLink DWL-520 v.E1 to work with Fedora. I have it running fine with Kanotix, but no joy with any other distribution, including FC4. (Kanotix comes with HostAP and a DWL520e script for setting up this PCI card.) Has anyone gotten this thing working?

funchords · #2 23rd December 2005, 05:39 AM

Quote:

Originally Posted by gpeacock

I can't see that anyone has gotten one of these DLink DWL-520 v.E1 to work with Fedora. I have it running fine with Kanotix, but no joy with any other distribution, including FC4. (Kanotix comes with HostAP and a DWL520e script for setting up this PCI card.) Has anyone gotten this thing working?

Is this a DWL-G520, or a 520+, or really just a 520?

gpeacock · #3 23rd December 2005, 02:13 PM

This is the older 'B' version. I think they went through several chipsets before ending up wtih the ver. E with the SFF design. Firmware must be installed each boot, which is maybe the complication. Reading around, seems like upgrading to a DWL-G520 might save some headaches.

funchords · #4 24th December 2005, 07:27 AM

Definitely. I'm using a DWL-G520 right now with the madwifi drivers.

I don't have 108 mbps, but I'm not sure if that's a madwifi limitation, something I've done, or something I've yet to do. But it works at 54 mbps and is very stable!

heffo_j · #5 24th December 2005, 07:53 AM

I have a D-Link G650 with Antros chipset working. I am not sure what speed it is running: my boot details reports and error setting the bit rate. I am not sure how to change this. I guess I am happy that I have the thing working with MADWIFI. Any advice on how to set the bit rate to work more quiockly would be appreciated.

Regards
John

funchords · #6 24th December 2005, 08:03 AM

When I run system-config-network, I find that the app that comes up nukes the rate line.

Here's a file you can use to compare to yours and experiment with...

[root@topol003 ssh]# cat /etc/sysconfig/network-scripts/ifcfg-ath0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
IPV6INIT=no
ONBOOT=yes
USERCTL=yes
PEERDNS=no
GATEWAY=192.168.177.251*
TYPE=Wireless
DEVICE=ath0
HWADDR=00:11:22:33:44:55*
BOOTPROTO=dhcp
NETMASK=255.255.255.0
DHCP_HOSTNAME=
IPADDR=192.168.177.103*
DOMAIN=
ESSID=YourSSIDhere*
CHANNEL=1*
MODE=Managed
RATE=Auto

Definitely change the lines with an asterisk (*) to fit your network

heffo_j · #7 25th December 2005, 06:50 AM

Thanks Robb, I'll have play and see what happens.

Regards
John

othas3 · #8 12th January 2006, 02:02 AM

I got it to work on non-Fedora kernels (FC2 class) because I had to compile the hostap driver and could never find the kernel sources on Fedora kernels. I've just upgraded to FC4, and while the 2.6.11-whatever kernel couldn't load the driver, the 2.6.14-1.656 kernel did....but then blocked all traffic in and out of the box...including wired connections. I called myself downloading and installing the 'correct' rpms, and now there is no network jam, but no wireless either. The drivers don't load.

othas3 · #9 12th January 2006, 08:14 PM

I got it working using 2.6.14-1.1656_FC4, although I think it was working with 2.6.11-1.1369_FC4. I finally figured out how to compile the drivers (hostap-driver-0.3.7), too. One issue here is that make install will put the drivers somewhere that isn't where modprobe is going to load them from. Some t/e found the right dir...I think.

I ran into the traffic jam problem again, and said "hmmph, it's like someone through a shield up or something". I ping'd and browsed and found that I was only getting traffic through 2 ip's, and 127.0.0.1 (calling it localhost by name was jammed). I thought back to the shield thing and one of the synonymous terms came to mind -- shield, blocking, barrier, selective barrier...FIREWALL.

With this kernel, firestarter loads after wlan0, which now comes up without the annoying "device not ready....aborting"-but seemed to load anyway, and does load. On FC2, firestarter failed after wlan0 appeared to fail, but I guess it loaded when I initiated wlan0 through rc.d/local

While firestarter didn't behave this way on FC2, but now it was going 0.0001% tolerance, and blocking everything. Editting the policies didn't seem to make a difference so I had to shut it down....and now it works!