Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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'm running SuSE 9.2. This problem existed, for me, with SuSE 9.1 and 9.0. I have also had it with a few other distros.
The problem is dhcpcd. I have a wired cardbus nic card in a laptop. The card is typically plugged in before I fire the machine up. When the machine starts, it powers the nic, and dhcpcd seems to run as expected.
However, dhcpcd does not properly pick up the name server information (DNS) from the DHCP server. It picks up IP and subnet mask just fine. Depending on where I'm at, this DHCP server may be a Linksys "DSL Router" or ISC's DHCP server. The results are the same either way.
Once the machine is up, and I realize the DNS information isn't there, I do 'killproc dhcpcd' and then 'dhcpcd eth1' and it picks up the DNS information properly. I don't get why its doing that.
I prefer ISC's DHClient over dhcpcd, but I've never got dhclient working with SuSE's automatic if-scripts (at boot, or at hotplug). Right now, though... I just want something that works.