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.
I am using SUSE 9.3 and I am trying to move away from KDE and switch to blackbox. My wireless card works fine using ndiswrapper (it is a Dell TrueMobile 1350 card), I get an IP from dhcp on boot, etc. The thing that has me stumped is that in order to resolve names after I boot, I have to run KInternet, choose the Wireless Adapter, go in find the AP, and hit the connect button. It seems silly, and I imagine there is a simple work around. I don't like having to load the KDE libraries when I go into blackbox just so I can do that one thing - the whole point of switching was for speed...
So to reiterate, I get an IP, I can ping by IP, but in order to resolv names, I have to go through hoops to hit the connect button - I'm sure there is some magical command line that I can stick in a startup script somewhere to effectively do the same thing.
probably not, cause using ndiswrapper you usually have to associate to the ap before running dhcpcd, which will update your resolv.conf, ip address, and gateway. it is probably the gateway that is doing it. but it is usual. the manual way to do it is the use iwconfig and give the essid like this:
#iwconfig wlan0 essid linksys
then bring up the wireless card with:
#ifconfig wlan0 up
if you want to get the gateway put in by hand, just use route:
It turns out that it was /etc/resolv.conf. As the system was configured, none of the commands mentioned above did anything because all of that stuff was already working on boot. What was missing was the nameserver entries in resolv.conf.
To test, I opened resolv.conf and added some nameservers - voila - everything worked fine. I went in to X, and ran kinternet, to see what resolv.conf looked like. There was a giant comment area saying that this was a temporary resolv.conf written by dhcpcd. What's strange to me is that dhcpcd had already run, I already had an IP and I could ping by IP just fine without touching the system; but once you click that connect button in kinternet, for some reason it grabs more info from dhcpcd...
Either way, adding my nameservers to resolv.conf solves this problem.
For anyone looking for details, a minimal resolv.conf can probably look like:
well, that is odd cause dhcpcd should update your resolv.conf. if you are using a router, then you probably need to put the dns servers into the router statically. cuase when you run dhcpcd the router should give you a 192.168.x.x to use for dns... if it is, but it isnt working, they you need to hard code them into it. cuase, unless yast is doing someitng wierd, when you run dhcpcd again it will overwrite what you put into resolv.conf. so to keep you from having to put it in everytime, just put it into the router.