Comment 104 for bug 279262

Really the easiest way is to just do a ip address reservation for your
NIC's MAC address on your DHCP server. That way when this long drawn
out bug is finally fixed, you won't have to do any special re-config
of anything.

On Thu, Dec 4, 2008 at 9:14 AM, Alexander Sack <email address hidden> wrote:
> On Sat, Nov 08, 2008 at 07:44:40PM -0000, Dave Jakeman wrote:
>> Just back from wiping/installing 8.10 (full) and trying to set up my
>> static wired connections.
>>
>> On the first attempt, I configured my connections and they were accepted
>> without a "read-only" error.  Couldn't get onto the internet though.
>> Went back to check, and both connection definitions had vanished.
>> Reconfigured them again and this time renamed them from "auto eth0" and
>> "auto eth1" to "Wired Ethernet 1" and "Wired Ethernet 2".  This time,
>> they were stored and I could surf with Firefox.  On reboot though, both
>> the connections had disappeared again.
>>
>
> Auto connections are read-only. Its a bug that you dont get an
> error. You need to create new connections if you want to do your own stuff.
>
>
>  - Alexander
>
> --
> [regression] devices/interfaces not set to "auto" in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)
> https://bugs.launchpad.net/bugs/279262
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “network-manager” source package in Ubuntu: Triaged
> Status in network-manager in Ubuntu Intrepid: Won't Fix
>
> Bug description:
> the regression here is that devices are unmanaged even though they dont have a "auto eth0" line in /etc/network/interfaces
>
> Here an example of an interfaces configuration that should not set the devices in unmanaged mode
> https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/279262/comments/14
>
> To reproduce:
> use the /etc/network/interfaces configuration from the above comment and see that after restart the device is unmanaged in intrepid, but managed in hardy (0.6).
>
> The code we shipped in NM 0.6 that shows that auto connections were blacklisted is:
>
>        for (curr_b = ifparser_getfirst (); curr_b; curr_b = curr_b->next) {
>                if ((!strcmp (curr_b->type, "auto") || !strcmp (curr_b->type, "allow-hotplug"))
>                    && strstr (curr_b->name, iface))
>                        blacklist = TRUE;
>        }
>
> The proposed patch is committed to the ubuntu.0.7 branch (see Related Branches section in this bug) and can be seen here:
>  http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu.0.7/annotate/2957?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
>
> Test packages with that patch are available: https://edge.launchpad.net/~network-manager/+archive
>
> Impact:
> 1. no impact for new users
> 2. no impact for users that installed in gutsy or later and didnt modify their /etc/network/interfaces (e.g. through gnome network-admin)
> 3. users with dhcp that installed before that will most likely see their interface as being "unmanaged" and "not upped on startup" even though those interfaces were previously managed by NM. Note: we transitioned those old installs in gutsy to NM by commenting just the "auto ethX" lines in /etc/network/interfaces.
>
> Risk:
> + patch appears reasonable minimal
>
>
>

--
Brian VanMeeteren
Technical Specialist
ConsultSYS
135 Root Trail #3
Palm Beach, FL 33480
(561) 273-1142
<email address hidden>