Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I pasted my 128 WEP key (starred out because my parents would shoot me if I pasted the actual key, even though I admin the router) in several places just in case. The
WIRELESS_AUTH_MODE variable is the one that I think is the troublesome one, but if anyone knows otherwise, let me know.
Well, if you have associated with the access point, please post the output of both 'iwconfig' and 'ifconfig'. When posting the output of iwconfig, don't forget to obfuscate your key again, please.
Looks like you are associated and have an IP, which is very good. Is your hardwired network card (eth0) connected to anything? If not, try 'ifconfig eth0 down' and then try to ping again.
I had the same trouble with this card on Suse 9.2. I figured out that I had to set the DNS and Routing info even tho I had it set to get that info from dhcp. For me this setting was easy Network Device or DNS and Hostname modules in Yast. Hope this helps. I only found this out because KInternet told me it couldnt find any DNS or routing info.
get ping to the internet directly working first, rather than use DNS as its adds a whole layer of potential problems.
Try 158.152.1.65 which is Demons primary DNS server, its always there.
If this fails you have a routing problem so forget DNS for the second.
If you can ping your internet router which I'm guessing is 192.168.1.1 then probably the problem is that the Wireless software seems to have trouble translating the Default Gateway provided by DHCP to a default route in the routing table. If you do 'route' you'll probably find that 0.0.0.0 is missing.
If so do 'route add default gateway 192.168.1.1' and it should all work.
My eth0 is working fine, in fact my other posts were made using the eth0 device, but the problem is the wlan0. I also have other wireless computers working on the network.
Ok, I scrapped SuSE 9.3 on my laptop, but.... I just installed it on my mom's laptop, and I can connect to the internet, 64.233.161.104 brings me to google in my browser, and I can ping other sites, but..... I can't use DNS. I'm smart enough to read what you said about DNS, but I have no idea how to configure it. As always any help appreciated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.