[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
an alternative would be to allow for a mapping to be treated as an iface for the hal device added callback. Then the system should also know that eth0 is a managed device. -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
in hal_device_added_cb the code only checks for exact matches in iface names. I suspect it'd make more sense to check by prefix, i.e. for a device of name "eth0" check for any iface_connection of name "eth0" or starting with "eth0-". As it is, there is no way to unmanage a device that does not have an iface line in /etc/network/interfaces -- [intrepid] network manager does not blacklist/unmanage mapped devices in managed=false mode https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
yes, it seems to. I tried it this morning. Then nm-applet shows, wireless appears and the mapped interfaces are showing in the nm-applet menu. In managed=false, this seems to be a race of some kind. I used sysv-rc to take NetworkManager out of the boot, and start it for the first time in an xterm, but everything just appeared. Maybe I should create a new runlevel, that is all boot stuff until NetworkManager and then try things in there. Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: autoconnect Nov 2 11:26:42 stephan-lap nm-system-settings:SCPluginIfupdown: management mode: unmanaged Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_11_43_75_eb_d0, iface: eth0) Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: devices added (udi: /org/freedesktop/Hal/devices/net_00_13_ce_e7_d9_f8, iface: eth1) Nov 2 11:26:42 stephan-lap nm-system-settings:Ifupdown: get unmanaged devices count: 1 Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: (152797424) ... get_connections. Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: (152797424) connections count: 6 Nov 2 11:26:42 stephan-lap nm-system-settings:Ifupdown: get unmanaged devices count: 1 Nov 2 11:26:42 stephan-lap nm-system-settings:SCPlugin-Ifupdown: end _init. look at the management mode: unmanaged und then the unmanaged devices count. Doesn't this look odd? Which device is managed, even though I set managed=false? -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
does managed=true help you in /etc/NetworkManager/nm-system- settings.conf ? -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
After boot there was no nm-applet icon in the GNOME notification area. I expected to see one there. The applet was running, I suppose, but was not showing in the notification area. At this time, all networking interfaces were killed by NetworkManager. After restart of NetworManager the nm-applet icon did show up (with the red cross indicating no connection), and offered me the mapped interfaces. I'd have expected this to happen after boot, or my interfaces be left alone. Ideal operation for me would have been: after boot nm-applet shows up, the mapping-selected wired connection is active, the others are available for selection, wireless is enabled. If that is not possible, I'd have liked to have NetworkManager handle just wireless, and leave my wired connections completely alone. If that is also not possible, I guess I'll just deinstall NetworkManager ;-) -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
what didnt you see? -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
I noticed by scanning the boot logs, that 1. the interfaces eth0 and eth1 were up and configured correctly by the time NetworkManager started. The NetworkManager startup was marked as fail, but the processes were running, which is why I did not see this. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: "after-activate.zip" http://launchpadlibrarian.net/19227082/after-activate.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: "after-nm-restart.zip" http://launchpadlibrarian.net/19227070/after-nm-restart.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
** Attachment added: "after-boot.zip" http://launchpadlibrarian.net/19227059/after-boot.zip -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
where is my screenshot? -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
it does what I consider to be the right thing: offer me all mapping ifaces and if I select one, it works fine. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
I agree that its a bug that the applet is visible when you restarted NM but not before. Could you also attach a screenshot how the applet looks like (when the dropdown is open) after restarting NM? I mean from what I see in the logs you shouldnt be able to do much there even after the restart. Screenshot would clarify that. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
> anyway, the other problem that your mapped interfaces do not autoconnect can > probably quite easily > be solved by propagating the autoconnect state of the "main"-connection to > the mapped connections > in the ifupdown legacy plugin. Not sure that would be a solution, right now all I want is NetworkManager to expose its state to nm-applet. > meaning: if you have multiple wifi configurations mapped (which probably > should be a common use > case of mapping), NM will just autoconnect to whatever of the configured > SSIDs it has in range ;). In my case I am ok with the wireless connectivity (or better I was until one of the later intrepid alphas). I use mappings for the wired connections, as the script determines whether I am physically related in our Portland office, my home office, out Amsterdam office, or whatever. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
> why do you want to use the applet? If you want to use them you should enable > managed=true in /etc/NetworkMananger/nm-system-settings.conf > otherwise you opt into using the old ifupdown - thats the feature. I would not have complained if that was really the case. The problem is that NetworkManager kills my eth0 and then nm-applet does not offer any way to get network connectivity back. If I restart NetworkManager later, it suddenly works, which is not consistent in its own right. I believe that NetworkManager should have two absolute requirements: 1. if any device is touched at all by NetworkManager, then nm-applet must be visible 2. a restart of NetworkManager may not change nm-applet's view of the NM state. BTW: my "wanted" operation mode for NM would be to leave my wired connection's initial state alone, or at least leave the /etc/network/interfaces decision on the default interface active. I'd like to use NM for wireless, and I'd be ok to use it for wired (if it'd work). -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
meaning: if you have multiple wifi configurations mapped (which probably should be a common use case of mapping), NM will just autoconnect to whatever of the configured SSIDs it has in range ;). -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
anyway, the other problem that your mapped interfaces do not autoconnect can probably quite easily be solved by propagating the autoconnect state of the "main"-connection to the mapped connections in the ifupdown legacy plugin. -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 291564] Re: [intrepid] network manager must be restarted after every boot
why do you want to use the applet? If you want to use them you should enable managed=true in /etc/NetworkMananger/nm-system-settings.conf otherwise you opt into using the old ifupdown - thats the feature. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- [intrepid] network manager must be restarted after every boot https://bugs.launchpad.net/bugs/291564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
