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 have a subnet at home using DHCP. Everything connects wireless except my linux box which is hardwired on eth0 (the only one). I have never needed to configure anything and it always works fine.
The other day I suffered a couple power outages and now it won't connect. It just times out waiting for a response from the server.
I put a different machine (Windoze) on the hardline and it obtained an IP and connected no problem.
The light on the NIC and the light on the modem are on to indicate there is traffic on the wire.
Running ethtool gives me all the info on my adapter including "Link detected: yes."
I modified my syslog to send output to /var/log/dhcpcd.log.
It might be worth noting that it was trying to renew x.x.x.4, when it's last known address was x.x.x.5, so fearing it might be some kind of caching issue as a result of a cold boot I emptied resolv.conf and removed the .cache and .info files from /etc/dhcpc.
That didn't do anything except stop from trying to obtain it's old IP. It only sends DHCP_DISCOVER and times out waiting for the response.
One time just now as I write this, it got a DHCP_OFFER from a DHCP_DISCOVER, but then timed out on the DHCP_REQUEST. Now it's back to normal again.