Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I think this probably needs to be an FAQ. This sounds like the same problem I had initially, which was that I was getting connected to the AP and getting an address via DHCP, but not getting a default route for the wireless interface (eth1). Here's the catch: when dhcpcd starts up for multiple interfaces, it only accepts a default route on the <b>first</b> interface. Once I changed the wired (eth0) interface to come up manually instead of "onboot", the wireless worked fine.
Bring up YaST, go to "Network Devices", "Network Card". Select your wired card. Under the "advanced" settings, there's a dropdown menu for "Device Activation". It's probably set to "At Boot Time". Change it to "manually".
It means that you'r e not getting a DNS server address from your DHCP host. I don't know how your network is set up, but typically either
a) you have an all-in-one router/AP/firewall dingus, or
b) you have a router/firewall box and a separate WAP.
In either case, you typically have to tell whichever box is providing DNS for you to hand out a DNS server address. Usually the address is the router or WAP itself, and it just proxies DNS queries out to another system. But your Linux system seems to be doing everything it should be.
Sorry, I'm pretty much out of suggestions at hit point. Without knowing what your DHCP host is, I couldn't even venture a guess. The only useful suggestion I could give you at this point is to look at the documentation for your DHCP device and see if it says anything useful. Oh, one other thing you could do as a workaround for the moment: put the address of your DHCP device (which is almost certainly proxying DNS) directly into /etc/resolv.conf (man resolv.conf will tell you the format of the file). Good luck!