ubuntu edgy dhclient problem

Denis McMahon · External Since: Mar 04, 2007 Posts: 8

Hi

whenever my box boots up, the network interface fails to configure.

In syslog I have something like:

NetworkManager: <information> starting...
NetworkManager: <information> eth0: Driver 'ne2k-pci' does not support
carrier detection. You must switch to it manually.
NetworkManager: <information> nm_device_init(): waiting for device's
worker thread to start
NetworkManager: <information> nm_device_init(): device's worker thread
started, continuing.
NetworkManager: <information> Now managing wired Ethernet (802.3) device
'eth0'.
NetworkManager: <information> Deactivating device eth0.

If "sudo dhclient" then it goes away and gets a lease and is happy.

Is there anything I can do (i.e. a file / script I can edit) to
effectively tack a "sudo dhclient" on at the end of system bootup so
that when my nephews turn the machine on, they don't need an su password
or my presence to use apps like firefox and gaim.

I'm guessing there must be a script somewhere that I can edit for system
startup commands.

Denis McMahon

Liam O'Toole · External Since: May 11, 2006 Posts: 42

On Fri, 23 Mar 2007 03:56:58 GMT
Denis McMahon <denis.mcmahon.TakeThisOut@ntlworld.com> wrote:

> Hi
>
> whenever my box boots up, the network interface fails to configure.
>
> In syslog I have something like:
>
> NetworkManager: <information> starting...
> NetworkManager: <information> eth0: Driver 'ne2k-pci' does not
> support carrier detection. You must switch to it manually.
> NetworkManager: <information> nm_device_init(): waiting for device's
> worker thread to start
> NetworkManager: <information> nm_device_init(): device's worker
> thread started, continuing.
> NetworkManager: <information> Now managing wired Ethernet (802.3)
> device 'eth0'.
> NetworkManager: <information> Deactivating device eth0.
>
> If "sudo dhclient" then it goes away and gets a lease and is happy.
>
> Is there anything I can do (i.e. a file / script I can edit) to
> effectively tack a "sudo dhclient" on at the end of system bootup so
> that when my nephews turn the machine on, they don't need an su
> password or my presence to use apps like firefox and gaim.
>
> I'm guessing there must be a script somewhere that I can edit for
> system startup commands.
>
> Denis McMahon

On Debian-based systems you can place your command in the
file /etc/init.d/rc.local. I doubt that the 'sudo' prefix is necessary.

Alternatively, could you just dispense with NetworkManager (looks to me
like it's buggy) and use static networking information
in the file /etc/network/interfaces instead?

--

Liam

Denis McMahon · External Since: Mar 04, 2007 Posts: 8

Liam O'Toole wrote:
> On Fri, 23 Mar 2007 03:56:58 GMT
> Denis McMahon <denis.mcmahon.TakeThisOut@ntlworld.com> wrote:
>
>> Hi
>>
>> whenever my box boots up, the network interface fails to configure.
>>
>> In syslog I have something like:
>>
>> NetworkManager: <information> starting...
>> NetworkManager: <information> eth0: Driver 'ne2k-pci' does not
>> support carrier detection. You must switch to it manually.
>> NetworkManager: <information> nm_device_init(): waiting for device's
>> worker thread to start
>> NetworkManager: <information> nm_device_init(): device's worker
>> thread started, continuing.
>> NetworkManager: <information> Now managing wired Ethernet (802.3)
>> device 'eth0'.
>> NetworkManager: <information> Deactivating device eth0.
>>
>> If "sudo dhclient" then it goes away and gets a lease and is happy.
>>
>> Is there anything I can do (i.e. a file / script I can edit) to
>> effectively tack a "sudo dhclient" on at the end of system bootup so
>> that when my nephews turn the machine on, they don't need an su
>> password or my presence to use apps like firefox and gaim.
>>
>> I'm guessing there must be a script somewhere that I can edit for
>> system startup commands.

> On Debian-based systems you can place your command in the
> file /etc/init.d/rc.local. I doubt that the 'sudo' prefix is necessary.

> Alternatively, could you just dispense with NetworkManager (looks to me
> like it's buggy) and use static networking information
> in the file /etc/network/interfaces instead?

I guess I need to remove one or maybe two packages:

network-manager
network-manager-gnome

Hmm, need to work out what to put in interfaces as well, presumably I
can find most of what I need from ifconfig once the interface is
actually working.

If that doesn't work, I'll try the /etc/init.d/rc.local fix

Denis McMahon

Liam O'Toole · External Since: May 11, 2006 Posts: 42

On Fri, 23 Mar 2007 11:15:37 GMT
Denis McMahon <denis.mcmahon RemoveThis @ntlworld.com> wrote:

> Liam O'Toole wrote:

[...]

> > On Debian-based systems you can place your command in the
> > file /etc/init.d/rc.local. I doubt that the 'sudo' prefix is
> > necessary.
>
> > Alternatively, could you just dispense with NetworkManager (looks
> > to me like it's buggy) and use static networking information
> > in the file /etc/network/interfaces instead?
>
> I guess I need to remove one or maybe two packages:
>
> network-manager
> network-manager-gnome
>
> Hmm, need to work out what to put in interfaces as well, presumably I
> can find most of what I need from ifconfig once the interface is
> actually working.

With DHCP it's really easy. Just add the following two lines to the
file:

auto eth0
iface eth0 inet dhcp

I am assuming that eth0 is the relevant network interface.

>
> If that doesn't work, I'll try the /etc/init.d/rc.local fix
>
> Denis McMahon

--

Liam

Martin Gregorie · External Since: Jan 29, 2007 Posts: 26

Denis McMahon wrote:
> Hi
>
> whenever my box boots up, the network interface fails to configure.
>
> In syslog I have something like:
>
> NetworkManager: <information> starting...
> NetworkManager: <information> eth0: Driver 'ne2k-pci' does not support
> carrier detection. You must switch to it manually.
> NetworkManager: <information> nm_device_init(): waiting for device's
> worker thread to start
> NetworkManager: <information> nm_device_init(): device's worker thread
> started, continuing.
> NetworkManager: <information> Now managing wired Ethernet (802.3) device
> 'eth0'.
> NetworkManager: <information> Deactivating device eth0.
>
> If "sudo dhclient" then it goes away and gets a lease and is happy.
>
> Is there anything I can do (i.e. a file / script I can edit) to
> effectively tack a "sudo dhclient" on at the end of system bootup so
> that when my nephews turn the machine on, they don't need an su password
> or my presence to use apps like firefox and gaim.
>
> I'm guessing there must be a script somewhere that I can edit for system
> startup commands.
>
I don't know ubuntu, but in a Fedora installation there's a script,
/etc/rc.d/rc.local which is meant for just that sort of thing. As issued
in my distro, it contains comment lines and nothing else. It's executed
as root after all the other init scripts, so you could just edit

/sbin/dhclient

into it as the last line.

--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |

Denis McMahon · External Since: Mar 04, 2007 Posts: 8

Liam O'Toole wrote:

> With DHCP it's really easy. Just add the following two lines to the
> file:
>
> auto eth0
> iface eth0 inet dhcp

Yep, removing network manager and doing that worked fine.

I think network manager wasn't. Sad

Denis McMahon