Problem with automatic start NIC adapters after update Dapper Drake Flight CD3

Bug #30220 reported by UbuPetr
10
Affects Status Importance Assigned to Milestone
netcfg (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I installed Kubuntu Dapper Drake Flight CD3 and everything worked well. I think, there was a hotplug (I hope, it was there) and in /etc/netwok/interfaces I had for booth NIC cards allow-hotplug, for automatic start after boot Operating System. Next day I made aptitude update; aptitude upgrade and NIC cards do not start automatic after boot Operating System and look at that: I think that hotplug was repalced with hal daemon (if hotplug and hal daemon is equal in functions) and happening this now: If we add in booth NIC cards auto eth0 and auto eth1 (replaced from older allow-hotplug eth0 and allow-hotplug eth1), so NIC cards start automatic, but packet traffic is freeze. Route tables, DNS, gateways, ... everything is filled correctly, but no packet traffic (this do not help: ifdown NICs, ifup NICs and modprobe -r net_drivers and again modprobe net_drivers). And continue listening: If we remove auto eth0 a auto eth1 and after booting Operating System we manually type ifup eth0 and ifup eth1, so NIC cards starts and everything working right. Do You know, where is the problem? It is injured by hal daemon, or beceasue hotplag is disappered? I think, there is a bug, because with manual start without auto eth0 and auto eth1 NIC cards working - I think, something do bad things, that driving this commands auto eth0 and auto eth1 in /etc/network/interfaces. It was happend in Kubuntu Dapper Drake Flight CD3 after aptitude update; aptitude upgrade. Your's Sincerely, Petr Novák `'ubu (dot] petr /at\ seznam [dot) cz". PS: Excuse me for my bad english.

Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

I think I'm having the same problem. When I boot my machine I don't have net access. I have to:
sudo dhclient

to get it working.

Revision history for this message
mon (javiermon-deactivatedaccount) wrote : some output: ifconfig before and after sudo dhclient.

some output: ifconfig before and after sudo dhclient. I also include the dhclient output.

Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

I'm also using kubuntu dapper up to date

Petr Tomeš (ptomes)
Changed in hal:
status: Unconfirmed → Confirmed
Revision history for this message
UbuPetr (ubu-petr) wrote :

Maybee something bad in mii-diag and mii-tool. And now if I try to use IP from DHCP:

Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

/etc/dhcp3/dhclient.conf line 1: no option named dhcp-class-identifier
send dhcp-class-identifier "NetcfgDHClient"
     ^
/etc/dhcp3/dhclient.conf line 1: semicolon expected.

^

/etc/dhcp3/dhclient-script: line 45: syntax error near unexpected token `then'
/etc/dhcp3/dhclient-script: line 45: `syntax error near unexpected token `then'

Revision history for this message
Martin Pitt (pitti) wrote :

Recently fixed:

netcfg (1.23) unstable; urgency=low

  * Don't propagate NetcfgDHClient class identifier to installed system.

 -- Colin Watson <email address hidden> Tue, 17 Jan 2006 12:51:16 +0000

Changed in hal:
status: Confirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

To fix it for you, please just remove the single line from /etc/dhcp3/dhclient.conf. New installs (or upgrades from Breezy to current Dapper) will not have that bug.

Revision history for this message
mon (javiermon-deactivatedaccount) wrote :

Hi

This bug was fixed on my machine, but recently has re-appeared. I have to manually start dhclient to get network access on my machine.

Using kubuntu dapper up to date.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.