FC5 Wireless won't connect

[dcubed]

I have a D-Link DWL-G630 PCMCIA wireless card on my laptop (x86), and I use NetworkManager for network management. Under FC4 and Ubuntu, this card has worked fine. Under FC5, however, the card will see the available networks, try to connect (the connection animation will appear, but neither of the LEDs will light) and then return to the 'no connection' stage.

Is anybody else having this problem? Should I file a bug report, and with whom?

Thanks in anticipation of some great help.

edit: atheros/madwifi
edit: selinux and firewall are both disabled since install

[ihavenoname]

Is anybody else having this problem? Should I file a bug report, and with whom?

i am having the same problem and it seems many others are as well...i am not sure why thou i have a Linksys WUSB54gv4 card.

[dcubed]

I should also be more specific...it's an atheros chipset and I'm using madwifi. I imagine yours is, and you are, also.

It is heartening to hear that other people are having this problem too, so hopefully there will be a fix. Wireless connectivity is a make-or-break feature for me, so it would be nice to get it working.

[icantux]

You can add me to the list of non-working wireless... Mine just won't get an IP no matter what I do (using dhcp).

Running:
FC5 (installed today)
madwifi for my AR5212 (atheros) IBMa/b/g card (thinkpad)

I dunno what the problem is: networkmanager, madwifi or the dhcp client, but ...
I already un-yummed networkmanager (somehow that app doesn't seem robust enough), but regardless, it's an added useless layer in troubleshooting. I'd like to get my wireless working before having managers tagging along and perhaps messing things up more than anything.

[fog]

Same problem here with atheros :mad:

[icantux]

Well I just fixed my problem.

No matter what I did before I couldn't get an IP. Sooo.. back to basics. I turned off WEP encryption in my router and then did this:

# iwconfig ath0 essid yummybeer
# ifconfig ath0 up
# dhclient ath0
# ifup ath0

(yummybeer is my ssid as setup in the router) :D

... and BAM! it took about 20 seconds of "thinking" but finally I got an IP and I could use the wifi. This leads me to believe that the way the dhclient is currently setup it won't allow enough time for the wifi to get an IP while WEP encryption is set and therefore it times out .... I still need to test out this theory but if that's the case, then that's not very good IMO.

While running gentoo I get an IP within 3-5 seconds either on an encrypted connection or not.

Oh well, hope this helps you guys.

[fog]

Problem solved
Add in your /etc/sysconfig/network-scripts/ifcfg-ath0 this line:

IWPRIV="authmode 2"

:)

[janos]

I have a thinkpad with the A/b/g card, and it has this problem too but i cannot turn off my wep encryption due to my location...yes i know it's no real protection but atleast it's something... so i'm going to try another kernel

[dcubed]

Doesn't do anything for me. Here's the output of dmesg | grep ath1

ath1: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath1: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath1: H/W encryption support: WEP AES AES_CCM TKIP
ath1: mac 7.8 phy 4.5 radio 5.6
ath1: Use hw queue 1 for WME_AC_BE traffic
ath1: Use hw queue 0 for WME_AC_BK traffic
ath1: Use hw queue 2 for WME_AC_VI traffic
ath1: Use hw queue 3 for WME_AC_VO traffic
ath1: Use hw queue 8 for CAB traffic
ath1: Use hw queue 9 for beacons
ath1: Atheros 5212: mem=0x32000000, irq=4
ADDRCONF(NETDEV_CHANGE): ath1: link becomes ready
ath1: no IPv6 routers present
ADDRCONF(NETDEV_UP): ath1: link is not ready

[ihavenoname]

hmm i dont know what is stopping you from mainting a connection..my guess has something to do with selinux or the firewall....sometimes i question why i use fedora core....and it seems its mostly because of the larger number of packages available...i dont really have a problem dealing with security not even in windows...im an amazingly boring target for "hackers"(i say its cause i dont need a virus to break my comp. im good enough at doing that on my own :D ) in any case i think u should disable the firewall and selinux til u get everything working (if u already havent) and once everything is in order find out what it was exactly and get it fixed...and i wish u all the best of luck. OH and most importantly step back from the problem a little and take a few seconds b4 getting to it again..that usually helps me...sry if im not much help :(

[dcubed]

I have both firewall and selinux disabled since install. I'll add that to my first post so it helps other people out.

[Gallan]

what do you think about this:

[root@localhost vesa]# iwconfig ath0 essid default
[root@localhost vesa]# ifconfig ath0 up
[root@localhost vesa]# dhclient ath0
Internet Systems Consortium DHCP Client V3.0.3-RedHat
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ath0/00:02:e3:48:68:18
Sending on LPF/ath0/00:02:e3:48:68:18
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[dcubed]

what do you think about this:

[root@localhost vesa]# iwconfig ath0 essid default
[root@localhost vesa]# ifconfig ath0 up
[root@localhost vesa]# dhclient ath0
Internet Systems Consortium DHCP Client V3.0.3-RedHat
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/ath0/00:02:e3:48:68:18
Sending on LPF/ath0/00:02:e3:48:68:18
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 20
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Exactly what I get.

[Gallan]

what do you get with ifconfig and iwconfig?

here mine:

[root@localhost vesa]# iwconfig
lo no wireless extensions.

ath0 IEEE 802.11b ESSID:"default" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.472 GHz Access Point: Not-Associated
Bit Rate=11 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

[root@localhost vesa]# ifup ath0

Determining IP information for ath0... failed.
[root@localhost vesa]# ifconfig
ath0 Link encap:Ethernet HWaddr 00:02:E3:48:68:18
inet6 addr: fe80::202:e3ff:fe48:6818/64 Scope:Link
UP BROADCAST RUNNING 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:200
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Memory:d8920000-d8930000

eth0 Link encap:Ethernet HWaddr 00:0A:E4:B2:13:DC
inet addr:10.0.0.102 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:feb2:13dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:407 errors:0 dropped:0 overruns:0 frame:0
TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:183915 (179.6 KiB) TX bytes:25403 (24.8 KiB)
Interrupt:19 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:941 errors:0 dropped:0 overruns:0 frame:0
TX packets:941 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1637342 (1.5 MiB) TX bytes:1637342 (1.5 MiB)

[Gallan]

moreinfo:

[root@localhost vesa]# iwlist scan
lo Interface doesn't support scanning.

ath0 Failed to read scan data : Resource temporarily unavailable

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

[ihavenoname]

try this


iwconfig ath0 channel (your channel number) mode managed essid (your essid)
dhclient rausb0 (or dhcpcd rausb0 if you have it)

so it would look like this assuming ur wireless connection had an essid of default and it was using channel 7

iwconfig ath0 channel 7 mode managed essid default
dhclient ath0 (also you could just skip this step and instead go to Networking under System > Administration, make sure your wireless card is highlighte click edit go to Wireless Settings make sure it says mode managed and that your essid is typed in and the click ok click deactivate then activate and wait, do this if the first method fails)

[varspigil]

I figured I'd add my two cents as this issue is plaguing me as well.

I'm running Fedora Core 5 on a Thinkpad T42p using Livna wireless rpms (dual booting with XP) and Atheros a/b/g card.

I initially had problems with wireless after a kernel upgrade so I rebuilt the machine.

Now everything works perfectly (wired and wireless) as long as I'm at home (wireless is using MAC filtering on the router, no WEP encryption).

I'm traveling and now I find that my wireless connection sees other networks (using Network Manager) but cannot connect (this wireless network is not encrypted and is completely open (no MAC filtering), it simply doesn't get an IP address.

What's really disconcerting to me however; is that I try to plug in a wired connection and I get an IP but no name resolution.

I can run an nslookup through the terminal and I receive an appropriate answer, but my browser just spins and then states it can't connect to the website.

If I boot under XP I have none of these problems (so I'm fairly certain it's not hardware).

I'm thinking the the problems may be related. Any one have any ideas? I'm a bit of noob so I'm not real familiar with the tools I can use to troubleshoot so any help would be appreciated.

Oh, I've turned off SELinux and the firewall as part of troubleshooting as well...

Thanks for the time and attention.

[RandomLogic]

After I upgraded to FC5 (Yes, I did an upgrade rather than a fresh install!), my wireless connection via NetworkManager simply stopped working. This was the closest thread that I could find that discussed the problem, but it didn't provide an answer.

What finally solved my problem is the following: run system-config-network (as root). Delete the wireless connection. Then save your changes and close the application.

After restarting the network service, I found that NetworkManager was now working correctly. In retrospect, this makes a certain amount of sense. The whole purpose of NetworkManager is to dynamically create a network connection for eth0 (or eth1) based on the available wireless networks that it detects. If you have a static wireless definition for eth0 (or eth1), then some kind of conflict occurs, preventing NetworkManager from working.

This was not the behavior in FC4, but it certainly seems to be the behavior in FC5.

[ihavenoname]

hmm that sounds about right, when i get home ill try that..just to deviate slightly here, when u upgraded did you experience many problems beyond the network manager problem? i was under the impression that Upgrading would almost certainly result in a massive amount of pain.


Edit: I tried it, it did not work...

[dtmilano]

Some Atheros based wireless cards don't work with the NEW madwifi. Download the sources for madwifi-old (now there are two madwifi's),rebuild the modules and should work as before.
madwifi-old available from svn:
svn checkout http://svn.madwifi.org/branches/madwifi-old madwifi-old

[Gallan]

is this ok when I have wifi lines in dmesg? should tehy be ath lines?

[root@localhost ~]# dmesg |grep ath
ACPI Error (nsxfeval-0242): Handle is NULL and Pathname is relative [20060127]
ACPI Error (nsxfeval-0242): Handle is NULL and Pathname is relative [20060127]
ACPI Error (nsxfeval-0242): Handle is NULL and Pathname is relative [20060127]
ACPI Error (nsxfeval-0242): Handle is NULL and Pathname is relative [20060127]
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath_rate_sample: 1.2 (svn 1475)
ath_pci: 0.9.4.5 (svn 1475)
ath0: no IPv6 routers present
[root@localhost ~]# dmesg |grep wifi
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 7.8 phy 4.5 radio 5.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0xc0200000, irq=16
wifi0: no IPv6 routers present

iwlist scan says that "no scan results" and ifconfig:

[root@localhost ~]# ifconfig
ath0 Link encap:Ethernet HWaddr 00:02:E3:48:68:18
inet6 addr: fe80::202:e3ff:fe48:6818/64 Scope:Link
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:0A:E4:B2:13:DC
inet addr:10.0.0.102 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e4ff:feb2:13dc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3092 errors:0 dropped:0 overruns:0 frame:0
TX packets:1953 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1553947 (1.4 MiB) TX bytes:273083 (266.6 KiB)
Interrupt:19

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:931 errors:0 dropped:0 overruns:0 frame:0
TX packets:931 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1637014 (1.5 MiB) TX bytes:1637014 (1.5 MiB)

wifi0 Link encap:Ethernet HWaddr 00:02:E3:48:68:18
inet6 addr: fe80::202:e3ff:fe48:6818/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:19120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:0 (0.0 b) TX bytes:946440 (924.2 KiB)
Interrupt:16 Memory:d8920000-d8930000

and iwconfig:

[root@localhost ~]# iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"default" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
Bit Rate=11 Mb/s Tx-Power:16 dBm Sensitivity=0/3
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.

sit0 no wireless extensions.

I have these in my modprobe.conf:

alias ath0 ath_pci
options ath_pci autocreate=sta
alias wifi0 ath_pci

I really hope someone can see the problem I have now tried to get this work for "weeks"

[dtmilano]

This is my dmesg and scan:

[diego@nemo ~]$ dmesg | grep 'ath'
ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413)
ath_rate_sample: 1.2
ath_pci: 0.9.6.0 (EXPERIMENTAL)
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: H/W encryption support: WEP AES
ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3
ath0: Use hw queue 0 for WME_AC_BE traffic
ath0: Use hw queue 0 for WME_AC_BK traffic
ath0: Use hw queue 0 for WME_AC_VI traffic
ath0: Use hw queue 0 for WME_AC_VO traffic
ath0: Use hw queue 8 for CAB traffic
ath0: Use hw queue 9 for beacons
ath0: Atheros 5211: mem=0xe0000000, irq=10
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
ath0: no IPv6 routers present
[diego@nemo ~]$ iwlist scan
-bash: iwlist: command not found
[diego@nemo ~]$ /sbin/iwlist scan
lo Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:90:4B:8A:34:60
ESSID:"SpidzenMansion"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=10/94 Signal level=-85 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Cell 02 - Address: 00:13:10:05:15:AA
ESSID:""
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=4/94 Signal level=-91 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
...
hope that it helps you.

[Gallan]

what you have in /etc/modprobe.conf

I think there's have to be something wrong in that wifi0 lines!?! and where have you get those madwifi drivers?

[RandomLogic]

.just to deviate slightly here, when u upgraded did you experience many problems beyond the network manager problem? i was under the impression that Upgrading would almost certainly result in a massive amount of pain.
I don't want to take this thread too far off-topic, but briefly:

I upgraded my wife's machine first. Hers is fairly generic, with very little in the way of extra software. The only problem she had was the livna repository being misconfigured in yum.

On my machine, the upgrade kept crashing as soon as I selected "Upgrade". This turned out to be because of an entry that I had in /etc/fstab for playing Diablo II. When I temporarily disabled the entry, the upgrade worked. I fixed the livna problem, ran "yum update", and worked on the wireless issue. Everything else is working fine.

EDIT: I didn't mention this earlier, but my wireless card uses IPW2200.

[ihavenoname]

ThanxRandom logic.

Hmm i use the rt2570 drivers for my wireless which apparently are not fully supported w/network manager, that might be my problem but do you think that if i were to use ndiswrapper instead that i would have a better chance at getting Network Manager working? Because i remeber that in FC4 Network Manager worked rather well w/ ndiswrapper (however not so well with the rt2570 drivers) maybe Ndiswrapper would help alot of you who are having this problem..just a though

[dtmilano]

Relevant lines of modprobe.conf:
alias ath0 ath_pci
# Added by DTM
# only for new madwifi
#options ath_pci autocreate=sta

My wireless card doesn't work with new madwifi but works perfect with madwifi-old and NetworkManager.

[varspigil]

Two more cents...

I'm back home and the wireless network and wired network detect and function fine.

Not quite sure what's going on, but I'll see if I can't hit a HotSpot in the next couple of days to further troubleshoot the wireless connection.

[Gallan]

I have to try that madwifi old and networkmanager.

I have read from few forums about this fujitsu amilo a1650g computer that wlan card is not turning on...can this be true? So I can't get IP but if I run "iwlist channel" I can see channels so if card is not on how can I do that!?! I don't think so but...any comments?

[trondhuso]

It could be that dbus isn't running. I have had that problem from time to time. If it isn't running, you'll notice this by not having any networks available in NM-applet.

I haven't found out why dbus isn't starting. I am getting an error message saying "Unknown username "named" in message bus configuration file.
Found the solution for the last sentence. All I had to do was to install Bind and I was OK.

br
trond

[KillaKell]

I had quite a few problems with my wifi connection after freshly installing FC5 on a Dell Latitude 110L. finally got the ndiswrapper loaded and loaded the proper inf file from dell to make it work. but every time I boot I have to run
$iwconfig wlan0 essid Killas
$ifconfig wlan0 up
$dhclient wlan0

After all of that I will get a valid IP from the router and be able to browse. Have noticed some issues with going back and shutting the card down and bringing it back up. Once I bring it back up with the exact commands listed above it gets an address from the router but will not get onto the net. Cant even ping the default gateway that my ISP gives me. I am able to ping the router though. Just an odd piece of info that I cant figure out yet. The real question here thou is can I setup the card so that I dont have to type those lines in the shell everytime I boot up? This may stem from not being able to get the wifi card recongnized by the GUI that I am running. It only shows the eht0 connection and when I go to add the wifi card(in the GUI mind you) it does not list the ndiswrapper that I am using. Any suggestions would be greatly appreciated.

[ihavenoname]

you know ive noticed that many people have been having their problems with Network Manager, has anyone filed a bug report about this??? and also if the devs dont want to deal with it why dont we all do something about it? patch NM or even make simple scripts that do most of the tedious commands for us? Like a simple program that runs iwlist for us and then displays the networks that are available and allows us to choose one and then it uses iwconfig and dhclient or dhcpcd to connect? isnt that pretty much what NM is supposed to do but consistently fails at? Im not very good at programing so im not sure how do able this is so if anyone could elaborate on this idea it would be helpful. (What I am trying to say is that one of greatest things about linux is it's ability to come together to produce solutions to problems, so why dont we all come together and put whatever skills and knowledge we have to work to help all of us. :D
p.s. if u have any critisims or any ideas that would be great. sry is this a bit off topic? I dunno i just thought that it would provide solutions to the problems being discussed here :D

[KillaKell]

A script would be great, thats kinda what I was hoping to get in response. I am very new to linux so I'm not real certain on how to go about doing alot of even the simpler things. I tried making a batch file(not sure if thats wat they are called in linux or not) to run instead of having to open a terminal and tpye those commands that I listed in previous post everyime at bootup. Unfortunetly I have had litte success in getting the batch file to execute the commands so far.

I have in the file

#!
$iwconfig wlan0 essid Killas
$ifconfig wlan0 up
$dhclient wlan0

And that doesnt work. I believe I'm close but no cigar yet.

[KillaKell]

GOT IT! After messing with it quite abit I finally got wireless to start with bootup of the kernel. What needs to be done is an edit of the ifcfg-wlan0(or whatever your card shows as) file in the /etc/sysconfig/network-scripts/ directory. TYPE= should be set to wireless(mine had it listed twice and I had to change both places before it would work) and it helps if you also add the ESSID= with your wifi network name. ONBOOT= obviously also needs to be set to yes as well. Going to try setting it up with multiple networks in the ESSID field when I get back to school on Friday and see if I can make it connect to which ever connection is present. Hope this helps.

[pwalden]

Did you get it to work with multiple networks?

If so how?

[pwalden]

I am seeing a Jan 06 MadWiFi patch (http://madwifi.org/changeset/1380) that fixes a problem with NetworkManager. Something about "patch creates sysfs device links for athX interfaces".

I cannot tell if the livna repos has that version of MadWiFi in it yet.

[wneumann]

KillaKell: if you can't ping out dns is probably not working for you. It uses /etc/resolv.conf to know where to look for nameservers. When you do things it what fedora thinks is a nonstandard way the dhcp script can get confused and you end up with a messed up /etc/resolv.conf file. If that is the problem, just edit it back to what it should be by hand and things should work again.

[pwalden]

I found a linva bugzilla bug (http://bugzilla.livna.org/show_bug.cgi?id=990) and it confirms that the livna MadWiFi is broken with NetworkManager.

Subcribe to this bug to find out when livna MadWiFi will work with NetworkManager.