Comment 8 for bug 291564
Revision history for this message
| Stephan Trebels (ncubede) wrote Re: [intrepid] network manager must be restarted after every boot | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> 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.