kelsey hudson wrote:
rbw wrote:
$ rpm -qa|grep madwifi
madwifi-0.9.2.1-1.lvn6
kmod-madwifi-0.9.2.1-1.2.6.18_1.2868.fc6
madwifi-devel-0.9.2.1-1.lvn6

This is FC6 so it has:
$ rpm -qa|grep wireless
wireless-tools-devel-28-1.fc6
wireless-tools-28-1.fc6

My advice is to grab the latest svn of madwifi-ng (or at least the latest 'reported-somewhat-stable-reccommended' version from the madwifi website [madwifi.org], and compile it from source and use it. Livna is usually *way* out of date with madwifi.

I fought this battle a lot. I finally was able to get it working with Cisco LEAP a while back, but I've since changed jobs and haven't messed with it in a long time. Let me know if you need some help and I'll see if I can dig up my hacks and tricks.

talk to you later.
-kelsey


Thanks...
the two biggest things I am curious about how and why this is all working (and therefore how not to "optimize into brokenness" ;^) are:

1.) My ath0 card responds to commands directed at "ath0", so what is FC6 trying to do with "wifi0". I can actually assign a different fixed IP to each of them. I use a CLI script kludge to do that and I don't mess with the ifcfg-ath or ifcfg-wifi files system files and other such files... Well don't let me lie here, I did do this:
-rw-r--r-- 1 root root   165 Dec 23 14:25 original-ifcfg-wifi0

so now all I see now is this with no "wifi0" entry, and everything is working:
$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.31.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0 0.0.0.0 192.168.31.1 0.0.0.0 UG 0 0 0 ath0

That's as brave as I want to get right now...

2.) What the "boot" sequence is from start to finish is for a wifi card just like you pretty much need to know the boot sequence for Linux itself before you can delve into it any deeper...

But DJA had the right suggestion, to go there I need to go to the other specific forums, but KPLUG does give very good tips on what to consider...

Thanks!

rbw


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to