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've had dhcpcd working correctly but then moved the HDD to another machine with the same hardware, initially eth0 didn't work as udev had renamed it because the MAC address was different; I've now edited the udev rules to reflect the new MAC address and removed the entry for the renamed NIC. Now eth0 starts up and dhcpcd shows that my DHCP sever offered a valid IP address but dhcpcd waits for a while then reverts to using a 169.xxx.xxx.xxx address as if it failed to contact the DHCP server; /var/log/messages shows:
dhcpcd [pid]: eth0: offered 192.168.0.199 from 192.168.0.1
dhcpcd [pid]: eth0: timed out
dhcpcd [pid]: eth0: probing for an IPV4LL address
dhcpcd [pid]: eth0: checking 169.254.242.112 is available on attached network
dhcpcd [pid]: eth0: using IPV4LL address 169.254.242.112
The hardware is a Sun Ultra 10 and it's running Gentoo, kernel 2.6.29.gentoo-r1 in case it's relevant.
After wasting hours trying to get the floppy to work I gave up :-(
I manually configured the network (several times as I forgot to kill dhcpcd which was backgrounded) and used ssh to pull the logfile from tcpdump (the machine in question isn't running X and posting here using links is just too hard!)
This is the output generated when running dhcpcd:
192.168.0.1 is the router and dhcp server on my network, 08:00:20:a2:f6:15 is the MAC address of the machine I'm trying to get dhcpcd working on.
I'm not familiar enough with the protocol to figure out what's (not) going on but it seems that the machine is just ignoring the lease offer and requesting an address several more times. I'd be grateful for any insite or suggestions as to what to try next.
After trying to upgrade dhcpd I was getting messages about not being able to open the dhcpd.leases file on /var/db/ , I checked /var and found it empty and df showed it had a capacity of 0; I rebooted the server and found the HDD that /var was mounted on had died! After regressing dhcpd to the original version, modifying fstab to remove the mountpoint for /var then recreating /var , /var/lib/ , /var/lib/dhcp/ and touching /var/lib/dhcp/dhcpd.leases , I was able to start dhcpd and the client machine now correctly obtains an IP address.