Ubuntu – How to automate a root command after (not during) startup

12.04bashdhclientethernetroot

I'm using Ubuntu 12.04 LTS, but I need to run the following command:

sudo dhclient

after startup to acquire a stable ethernet connection. I am running dhclient during startup already, through the /etc/rc.local file.

Someone please help me run this command after-startup automatically (by removing it's requirement for root, or some other means), or suggest a different way of troubleshooting my ethernet connection.

Best Answer

One workaround would be to use rc.local with a sleep command. Put the following into /etc/rc.local:

(sleep 60; dhclient) &

This will make the command wait for 60 seconds before being executed, which should allow enough time for your machine to finish booting.

Related Solutions

Ubuntu – How does dhclient get called under 12.04

This ended up being caused by network-manager. My /etc/NetworkManager.conf file looked like this :

[main]
plugins=ifupdown,keyfile
dns=dnsmasq

[ifupdown]
managed=false

This config file was set like this when the machine was built (this may be a bug). By the fact that "managed" was set to false, NetworkManager wasn't initiating dhclient for the interface, and it wasn't considering the wired connection to be a real connection and so it wouldn't initiate the VPN either.

I changed "managed" to "true" and restarted the system. It works just as I'd hope now, runs dhclient, VPN works etc.

And to answer some of my own questions :

This is what the wired connection tab in a standard NetworkManager Network Connections dialog should look like : http://i.imgur.com/TgUs8.png
dhclient is kicked off my NetworkManager and then stays running while the connection is up

Ubuntu – How to get a Qualcomm Atheros Killer E2200 gigabit ethernet card working

I got information from another source that kernel 3.10 had support for this networking card. So what I did was install the kernel using this guide

http://www.ubuntubuzz.com/2013/07/how-to-install-linux-kernel-3101-on.html

First thing first, you have to download ALL deb files which are appropriate for your system architecture (32bit or 64bit), then put them in same folder for easy process.

Note: This answer is an updated version of the original post:

You need this one for sure:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc7-saucy/linux-headers-3.11.0-031100rc7_3.11.0-031100rc7.201308252135_all.deb

And then depending on your architecture grab the next 2:

64bit:

32bit:

Once downloaded, simply run the following command to install:

sudo dpkg -i linux*.deb

In case, you want to remove this version of Kernel, run this command:

 sudo apt-get purge linux-image-3.11*

Very simple and the connection started working right away after update and restart. I haven't experienced any problems with the new kernel yet so as long as I don't I will stick with this solution. It seems though as the thread you linked to me described the same problem and I'm sure that would've fixed the problem as well.

For those of you who might want to follow the instructions in that thread, on the top of page 7 there is a post from someone who had made a patch for this issue (not sure exactly how it worked but I guess it was to simplify and reduce the manual hacking as described in the first post).

An infinite thank you to all of those who helped me!

Best Answer

Related Solutions

Ubuntu – How does dhclient get called under 12.04

Ubuntu – How to get a Qualcomm Atheros Killer E2200 gigabit ethernet card working

Related Question