| 2008-10-06 20:01:46 |
marcobra (Marco Braida) |
bug |
|
|
added bug |
| 2008-10-06 20:07:47 |
marcobra (Marco Braida) |
description |
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
Thank you |
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
|
| 2008-10-06 20:33:10 |
marcobra (Marco Braida) |
title |
[intrepid] after reboot network is totally broken |
After reboot network is totally broken |
|
| 2008-10-06 21:16:18 |
marcobra (Marco Braida) |
title |
After reboot network is totally broken |
network-manager After reboot network is totally broken |
|
| 2008-10-06 23:32:41 |
Alexander Sack |
None: status |
New |
Incomplete |
|
| 2008-10-06 23:32:41 |
Alexander Sack |
None: bugtargetdisplayname |
Ubuntu |
network-manager (Ubuntu) |
|
| 2008-10-06 23:32:41 |
Alexander Sack |
None: bugtargetname |
ubuntu |
network-manager (Ubuntu) |
|
| 2008-10-06 23:32:41 |
Alexander Sack |
None: statusexplanation |
|
please post your /etc/network/interfaces and your /etc/NetworkManager/nm-system-settings.conf.
Also consider to read /usr/share/network-manager/README.Debian.
|
|
| 2008-10-06 23:32:41 |
Alexander Sack |
None: title |
Bug #279262 in Ubuntu: "network-manager After reboot network is totally broken" |
Bug #279262 in network-manager (Ubuntu): "network-manager After reboot network is totally broken" |
|
| 2008-10-07 18:17:16 |
blakamin |
network-manager: status |
Incomplete |
Confirmed |
|
| 2008-10-07 18:17:16 |
blakamin |
network-manager: statusexplanation |
please post your /etc/network/interfaces and your /etc/NetworkManager/nm-system-settings.conf.
Also consider to read /usr/share/network-manager/README.Debian.
|
|
|
| 2008-10-16 00:26:13 |
Alexander Sack |
title |
network-manager After reboot network is totally broken |
network-manager unmanaged mode causes confusion |
|
| 2008-10-16 00:26:55 |
Alexander Sack |
title |
network-manager unmanaged mode causes confusion |
network-manager unmanaged mode causes confusion (Devices not managed after reboot) |
|
| 2008-10-16 00:48:42 |
Alexander Sack |
network-manager: importance |
Undecided |
Low |
|
| 2008-10-16 00:48:42 |
Alexander Sack |
network-manager: statusexplanation |
|
ok, i renamed this bug to be more specific. if that doesnt really match your issue, please file a new bug. This definitly includes when you have problems getting access to network.
Anyway, i see several issues reported so far here, which I would like to comment on now:
1. the original reporter (marcobra) was confused by the result of the managed=true setting in /etc/NetworkManager/nm-system-settings.conf and uninstalled. This issue should be fixed.
2. Dazzer, you apparently want to manage your ips in /etc/network/interfaces. if you do that you cannot do that in NM anymore. There was a bug that made all apps start in offline mode when you configured your devices like that, but that is fixed now.
3. Claudio, you were struck by the same bug that should be fixed now. With any device being unmanaged we will tell the applications that you are CONNECTED. so fixed too.
4. Kadafi, you didnt provide any info on what behaviour you see. if its exactly what the original reporter described, then its fixed for you too.
5. sheka, Ryan, mrbean, Raimund, Sokraates, lohmatyi your bug is fixed like i said in 2. and 3. above.
6. Bryson, the ifupdown plugin is ment for support of old configurations and not to edit it. You should remove your configuration from interfaces. then you can use managed=true or managed=false, just as you wish.
7. Claudio, Sergey, please file a bug about the not honoured config values and provide sample configuration.
8. Shirish, Jeffrey, please file an individual, proper bug too.
Thanks. Closing this bug.
|
|
| 2008-10-22 12:08:21 |
Alexander Sack |
network-manager: status |
Confirmed |
Triaged |
|
| 2008-10-22 12:08:21 |
Alexander Sack |
network-manager: statusexplanation |
ok, i renamed this bug to be more specific. if that doesnt really match your issue, please file a new bug. This definitly includes when you have problems getting access to network.
Anyway, i see several issues reported so far here, which I would like to comment on now:
1. the original reporter (marcobra) was confused by the result of the managed=true setting in /etc/NetworkManager/nm-system-settings.conf and uninstalled. This issue should be fixed.
2. Dazzer, you apparently want to manage your ips in /etc/network/interfaces. if you do that you cannot do that in NM anymore. There was a bug that made all apps start in offline mode when you configured your devices like that, but that is fixed now.
3. Claudio, you were struck by the same bug that should be fixed now. With any device being unmanaged we will tell the applications that you are CONNECTED. so fixed too.
4. Kadafi, you didnt provide any info on what behaviour you see. if its exactly what the original reporter described, then its fixed for you too.
5. sheka, Ryan, mrbean, Raimund, Sokraates, lohmatyi your bug is fixed like i said in 2. and 3. above.
6. Bryson, the ifupdown plugin is ment for support of old configurations and not to edit it. You should remove your configuration from interfaces. then you can use managed=true or managed=false, just as you wish.
7. Claudio, Sergey, please file a bug about the not honoured config values and provide sample configuration.
8. Shirish, Jeffrey, please file an individual, proper bug too.
Thanks. Closing this bug.
|
ok. i think the regression is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
If you have auto eth0/wlan0 or something and a iface eth0/wlan0... line in your interfaces the behaviour is the same as in hardy. e.g. NM doesnt manage such devices.
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 |
|
| 2008-10-22 12:08:54 |
Alexander Sack |
network-manager: importance |
Low |
High |
|
| 2008-10-22 12:08:54 |
Alexander Sack |
network-manager: statusexplanation |
ok. i think the regression is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
If you have auto eth0/wlan0 or something and a iface eth0/wlan0... line in your interfaces the behaviour is the same as in hardy. e.g. NM doesnt manage such devices.
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 |
we have an identified regression here, so importance: high. |
|
| 2008-10-22 12:11:52 |
Alexander Sack |
description |
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
Original:
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
|
| 2008-10-22 12:11:52 |
Alexander Sack |
title |
network-manager unmanaged mode causes confusion (Devices not managed after reboot) |
[regression] network-manager unmanaged mode sets devices to unmanaged that were previously managed |
|
| 2008-10-22 12:12:28 |
Alexander Sack |
title |
[regression] network-manager unmanaged mode sets devices to unmanaged that were previously managed |
[regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy and before |
|
| 2008-10-22 12:12:59 |
Alexander Sack |
title |
[regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy and before |
[regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy |
|
| 2008-10-22 17:13:25 |
Alexander Sack |
description |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
Original:
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
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;
}
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
|
| 2008-10-22 17:15:35 |
Alexander Sack |
description |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
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;
}
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
|
| 2008-10-22 17:16:58 |
Alexander Sack |
title |
[regression] network-manager unmanaged mode sets devices to unmanaged that were managed in hardy |
[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) |
|
| 2008-10-22 17:18:45 |
Alexander Sack |
description |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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
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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
|
| 2008-10-22 17:19:16 |
Alexander Sack |
description |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
=== Original Description: ====
After update/upgrade/dist-upgrade of Ubuntu Intrepid today ( 6 Oct 2008 )
My network layer is not working more if i try to configure it (now is disabled) from top right icon
i get:
nm-ifupdown-connection.c 82
connection update not supported (read only)
The system dont' ask me for a (sudo) password if i try to edit connections.
Thank you |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
|
|
| 2008-10-22 17:19:36 |
Alexander Sack |
network-manager: statusexplanation |
we have an identified regression here, so importance: high. |
|
|
| 2008-10-22 17:19:36 |
Alexander Sack |
network-manager: milestone |
|
ubuntu-8.10 |
|
| 2008-10-22 17:20:15 |
Alexander Sack |
description |
the regression here is that devices are unmanaged even though they dont have a "auto eth0" line for instance.
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
|
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
|
|
| 2008-10-22 19:54:12 |
Alexander Sack |
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:
place the 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/2956?file_id=012ifupdownunmanagea-20081022120139-7rgnlk84604f1ysu-1
|
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:
place the 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
|
|
| 2008-10-23 09:35:42 |
Alexander Sack |
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:
place the 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
|
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ users with dhcp that installed before that will most likely see their interface as being "unmanaged" and "no up" even though those interfaces were previously managed. Note: we transitioned those old installs in gutsy to NM by commenting just the ethX lines in /etc/network/interfaces.
Risk:
+ patch appears reasonable minimal
|
|
| 2008-10-23 09:36:52 |
Alexander Sack |
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ users with dhcp that installed before that will most likely see their interface as being "unmanaged" and "no up" even though those interfaces were previously managed. Note: we transitioned those old installs in gutsy to NM by commenting just the ethX lines in /etc/network/interfaces.
Risk:
+ patch appears reasonable minimal
|
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ 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 ethX lines in /etc/network/interfaces.
Risk:
+ patch appears reasonable minimal
|
|
| 2008-10-23 09:37:13 |
Alexander Sack |
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ 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 ethX lines in /etc/network/interfaces.
Risk:
+ patch appears reasonable minimal
|
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ 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
|
|
| 2008-10-23 09:40:03 |
Alexander Sack |
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:
place the 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
Impact:
+ no impact for new users
+ no impact for users that installed in gutsy or later and didnt tweak their /etc/network/interfaces
+ 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
|
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:
place the 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
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
|
|
| 2008-10-23 09:49:54 |
Alexander Sack |
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:
place the 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
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
|
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:
place the 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
|
|
| 2008-10-23 09:54:23 |
Alexander Sack |
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:
place the 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
|
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
|
|
| 2008-10-23 12:40:01 |
Alexander Sack |
network-manager: statusexplanation |
|
|
|
| 2008-10-23 12:40:01 |
Alexander Sack |
network-manager: milestone |
ubuntu-8.10 |
|
|
| 2008-10-29 21:06:29 |
Martin G Miller |
bug |
|
|
added attachment 'syslog.txt' (syslog.txt) |
| 2008-11-04 02:21:24 |
Alexander Sack |
network-manager: status |
Triaged |
Won't Fix |
|
| 2008-11-04 02:21:24 |
Alexander Sack |
network-manager: statusexplanation |
|
wont fix in intrepid. |
|
| 2009-03-23 01:38:36 |
Alexander Sack |
removed subscriber Alexander Sack |
|
|
|
| 2009-06-12 07:12:25 |
Kadafi |
removed subscriber Kadafi |
|
|
|
| 2009-07-01 07:44:07 |
Olivier Cortès |
removed subscriber Olivier Cortès |
|
|
|
| 2009-12-13 18:40:03 |
cristian |
removed subscriber cristian |
|
|
|
| 2010-04-15 08:24:01 |
mrbean71 |
removed subscriber mrbean71 |
|
|
|
| 2010-04-21 13:58:23 |
pelagic |
removed subscriber pelagic |
|
|
|
| 2010-06-16 17:15:39 |
Filipe Sousa |
removed subscriber Filipe Sousa |
|
|
|
| 2011-01-06 20:53:12 |
Adam Porter |
bug |
|
|
added subscriber Adam Porter |
| 2011-03-31 15:01:46 |
Alexey Kotlyarov |
removed subscriber Alexey Kotlyarov |
|
|
|
| 2011-05-01 03:24:01 |
Adam Porter |
summary |
[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) |
Ethernet unusable after Maverick-Natty upgrade; device unmanaged; no way to change it |
|
| 2011-05-01 03:29:35 |
Adam Porter |
network-manager (Ubuntu): status |
Triaged |
Confirmed |
|
| 2011-05-02 01:45:30 |
thecure |
bug |
|
|
added subscriber thecure |
| 2012-02-14 07:48:15 |
Kai Kasurinen |
removed subscriber Kai Kasurinen |
|
|
|
| 2012-04-25 16:25:13 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2012-04-25 16:33:17 |
lohmatyi |
removed subscriber lohmatyi |
|
|
|
| 2012-04-30 14:08:13 |
Alexander Makarov |
bug |
|
|
added subscriber Alexander Makarov |
| 2012-05-27 16:14:46 |
margaret yeager |
network-manager (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2013-03-13 03:05:13 |
it support |
network-manager (Ubuntu): assignee |
|
it support (itsupport-x) |
|
| 2013-03-13 03:05:28 |
it support |
network-manager (Ubuntu): assignee |
it support (itsupport-x) |
|
|
