Kubuntu Gutsy "network settings" does not save settings, interfaces come up when they shouldn't

Bug #189369 reported by alrac
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I have a PC with two wired Ethernet interfaces, running Kubuntu Gutsy. One interface is not configured. However, it always come up at boot. This is incorrect behavior- unconfigured interfaces should not come up at boot. I read in the release notes that NetworkManager takes charge of unconfigured interfaces, and decides that it knows better than the user what their network interfaces should do. So I gave the interface a minimal configuration in /etc/network/interfaces. I tried both of these:

iface eth0 inet manual

and

iface eth0 inet static
        address 192.168.2.25
        netmask 255.255.255.0
        network 192.168.2.0
        broadcast 192.168.2.255

Neither of these configurations should cause the interface to come up at boot- this requires the line "auto eth0". However, on Kubuntu Gutsy it does.

Next, I tried using Kubuntu's "system settings -> network settings", and un-checked "Activate when the computer starts." This has no effect- eth0 still comes up at boot.

Network management on Kubuntu Gutsy is a mess. "Network Settings" doesn't save profiles (bug #73788, reported 2006-11-29 and still broken), the Help file is still broken (bug #57831, reported 2006-08-26 and still broken) and untangling NetworkManager, HAL, udev, ifupdown, and the interfaces file to try to figure out who's doing what is a beastly job.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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.