On Mon, May 23, 2016 at 03:44:37PM -0400, Ryan Mullen wrote:
Hello,
On Mon, May 23, 2016 at 3:36 PM, Dutch Ingraham <stoa@gmx.us> wrote:
enp0s25 Link encap:Ethernet HWaddr 00:1E:4F:B0:F4:DA inet addr:169.254.169.134 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40671 errors:0 dropped:0 overruns:0 frame:0 TX packets:1309 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2721326 TX bytes:217356 Interrupt:21 Memory:fe9e0000-fea00000
This doesn't help you solve your problem, but 169.254.0.0/16 indicates a link-local address, meaning dhcpcd failed to get a lease from your DHCP server. If you run dhcpcd manually, do you learn anything from its output?
Ryan
Thanks, Ryan. I did miss the link-local address. However, running dhcpcd manually isn't providing much info. For example, I tried the options (seperately) -N (to renew the lease), -l (to specify a lease time), -E (to attempt to use the last lease obtained by dhcpcd), and -d for debug. Each time dhcpcd responded with "sending commands to master dhcpcd process" and that's it. Interestingly, this box boots up without delay, but I would expect to see the 30-second default delay for obtaining a lease if no lease was able to be obtained. I'll try creating a seperate log file to capture any relevent output, because I'm not finding anything in the standard logs.