dhcpd has problems getting IP... dhclient works
Hi there!
I was tracking down crazy problems with getting an IP on my RPi3. After seriously trying to find an HW error (custom HAT, JTAG debugger,... attached) I ended up searching for problems in the software. It seems NetworkManager has problems with dhcpd (default in slackware) to get an IP. This was already documented in: https://www.linuxquestions.org/quest...er-4175576144/ 5 reboots gave at least 1 problem in getting an IP. Changing to dhclient resulted in a stable system. Btw the router runs 14.2 and manages the nets with dnsmasq. Anyone knows of any drawbacks of using dhclient??? 73 |
I've been using dhclient for two years now. Had problems with Networkmanger right out of the box when 14.2 was released, Changing to dhclient solve the problem.
|
well, then why does slackware prefer dhcpd???
73 |
Quote:
|
Hmm...
So there are already a bunch of people having troubles... maybe we should reconsider the default NetworkManager configuration ???? 73 |
dhcpd is a DHCP server, not a client.
|
One could try to uncomment clientid and comment out duid in /etc/dhcpcd.conf:
Code:
# Use the hardware address of the interface for the Client ID. HTH rob |
Are you sure you used dhcpcd and not dhcpd?
dhcpcd is a dhcp client (like dhclient) whereas dhcpd is a dhcp server daemon as mentioned by smallpond. |
Quote:
When you do have trouble, it isn't that difficult to find the client which works is it? |
Quote:
I also tried getting dhclient to work without luck. In the end I disabled NM and reverted to dhcpcd being called directly from the rc scripts, where I have control over the command line operators. |
Quote:
You can hook into /etc/NetworkManager/dispatcher.d to view and maybe manipulate NetworkManager's environment. (I've only done the former and not the latter.) |
Quote:
I would have never ever thought about dhcpcd (sorry for this typo...) being a problem... or at least being troublesome/unstable when used with NM in certain combinations... However, more interesting is IMHO the fact that none of my other 14.2 boxes showed problems so far... I need to get a paper done till september... after that I'll go and put -current on one of my x86 boxes to check for similar behaviour. reverting back to plain rc-scripts for the headless rpi boxes... well might be an option 73 |
Most of my home network uses the rc.inet1 script to manage their connections. My laptops use NetworkManager for their wireless connections; I haven't seen problems talking to my gateway with them, but I'm running bind and dhcpd versus dnsmasq.
There's also wicd in /extras, IIRC. Quite a few people have used it and many still do. |
All times are GMT -5. The time now is 08:30 AM. |