[SOLVED] Latest 14.2 network manager fails to get route
Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Was set to yes, but removing it changes nothing.
I just noticed that I have a :
Aug 22 21:16:15 darkstar NetworkManager[1244]: <warn> [1471900575.3462] device (eth0): failed to find device 3 'eth0' with udev
As I tweaked udev the problem can be there, I'll check that.
Thanks for your answer.
For an unknown reason, using dhclient now works. Not dhcpcd still... Only the update batch changed.
You can try changing the settings for dhcpcd. I don't find it particularly reliable either but I think it's more of a local issue with a dodgy switch I have:-
Within /etc/rc.d/rc.inet1 make sure that zeroconf is disabled:
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,646
Rep:
If it is an dhcpcd vs. dhclient problem you could also try to uncomment the line with clientid from /etc/dhcpcd.conf and comment the one with duid. Otherwise it won't work with my router.
If it is an dhcpcd vs. dhclient problem you could also try to uncomment the line with clientid from /etc/dhcpcd.conf and comment the one with duid. Otherwise it won't work with my router.
I will try that, but the problem I have is agnostic to DHCP clients. Even PXE booting and the DHCP client within U-Boot times out on the first try, but succeeds immediately on the 2nd. It only started happening when I had to replace a switch due to a fan failure.
I did them at the time you told me but nothing changed.
As of dhclient, it "magically" got the DNS yesterday.
I tested with a minimal set of tweaks (like key mapping).
I closed the issue because I now have a workaround, but I'll keep an eye on this. I can test on another ARM devices.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.