network card configured, but still can't connect to router!
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
network card configured, but still can't connect to router!
I'm using FC4 and have configured my laptop's wireless card to the extent that I know how. I installed ndiswrapper, got the windows drivers, loaded the drivers into ndiswrapper, modprobe'd ndiswrapper, verified the existence of wlan0, successfully set the essid on wlan0, and brought up the interface using ifconfig. I also turned off wep on my router and on the card.
Everything seems to be working fine--except that I can't connect to the network. I first tried dhclient wlan0. When I do that, I get a series of 'DHCPDISCOVER' lines, followed by a line that reads "No DHCPOFFERS received."
When that didn't work, I tried to go static. I turned off DHCP on my router and configured my card with a static address. I also added the correct gateway and subnet mask. I still couldn't see (i.e., ping) the router or other computers on my network.
I have also tried bringing the interface up and down, using alternate drivers, and cycling the machine.
iwconfig, as well as the graphical tools (e.g., kwifimanager) show strong signal strength. I also see the lights flashing on my router, especially when I'm fishing for an IP lease. I am also associated with my router's ssid.
I'm at a total loss of what to try next. Clearly the card is substantially configured (though my problem might be due to an obscure setting). I am also certain that the devices are within range and in some sort of contact (otherwise the card wouldn't be able to see/associate with the ssid). I am typing on a windows machine that is right beside the FC4 machine; the windows machine has a dynamic ip from the router.
I have noticed a couple of quirks that might have something to do with my problem. First, dmesg lists a series of ndiswrapper errors that read "setting bit rate failed (C00000BB)." The command "iwlist wlan0 rate" says that I have five available bit-rates: 5, 6, 9, 12, 18, and 48 Mb/s. It also says that my current rate is 54 Mb/s (which obviously isn't in the list). I have tried, without success, to change the 54 to one of the options in the list. Might this be a problem?
dmesg also lists the following error: "wlan0: no IPv6 routers present." I don't know what that means or if it might identify a problem.
OK, I've added about as much as I can. Please help!
Edit: I have also turned off my firewall and the extra FC4 security feature (can't remember the name).
I had a problem similar to yours over the summer and I suggest you try to find some linux native drivers. I went around in circles trying to get ndiswrapper to work. I updated it, tried different versions of the windows drivers and basically did so many different things I can't even recall them right now. It was a fuzzy period. In the end, iwconfig would see my router but ifconfig wouldn't get a lease. I was able to get it to work for a couple of minutes but it then took my keyboard hostage.
I then finally just got a linux driver for my Linksys WMP54G (which, by the way, was the first solution I found while googling my problem but I decided to bypass it because ndiswrapper seemed simpler!) and everything has been peachy.
Thanks for the suggestion. I have used ndiswrapper with success in the past, but for some reason I am having a lot of problems this time (though my problems might not be with ndiswrapper). Unfortunately, my card is by broadcom, and they have not released native linux drivers for it. Broadcom has released native linux drivers for other models, so maybe I'll try those for kicks...
Have you tried a different version of the Windows driver? Google for (model number) ndiswrapper and you may find reports of win32 driver versions known to work with ndiswrapper and win32 driver versions known to have problems with ndiswrapper.
sigh, cancel that last post. This is really, really strange. I updated the dhclient and immediately got an ip address from my router. This has *never* happened before. So, I put eth0 down and even unplugged my ethernet cable to verify that I had a working connection on wlan0. Sure enough, it was working, and I browsed the Internet for about an hour.
Then I rebooted. When my system came back up, I was once again unable to get an ip address. I even tried uninstalling and reinstalling the updated rpm. No luck. Once again, I can't get an ip address.
Does this recent phenomenon give anyone any ideas?
Ok, it seems that you have not tried the basics here. The problem, based on your description, would have nothing to do with DHCP at all. It seems that your wireless card is not associating with the access point. Try these steps to find out more information
1. After attempting to connect with your wireless card just type "iwconfig" on its own and check that there is a mac address next to "Access Point" in the output. If the address is just zeros then you have not associated with your access point/router
2. If you were unsuccesful with step 1, check dmesg ( just type dmesg in a shell ) and check that there aren't any error messages relating to ndiswrapper. Do you see any errors when you just type "ndiswrapper -l" ( although you probably wouldn't have got this far if there are ).
3. If you were successful and there is a mac address associated with the access point, double check in the interface to your router that your mac address is listed as connected. It will depend on router how you do this if it your router has such options.
4. It would be really good to see what commands you are using and the out put from them. For example, what parameters are you supplying to iwconfig to make it work? What is the output of iwconfig after you run iwconfig with out parameters? Are you always executing and "ifconfig <internface> up" after running iwconfig?
Updating RPM's and trying new drivers is pointless. You can't fix the problem if you don't know what is wrong and guessing is only going frustrate you more.