Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend
ajay at activitycentral.com
Mon Apr 30 03:30:15 EDT 2012
Thanks Martin and Jon for the replies.
On Sun, Apr 29, 2012 at 3:04 PM, Jon Nettleton <jon.nettleton at gmail.com>wrote:
> On Sun, Apr 29, 2012 at 10:04 AM, Martin Abente
> <martin.abente.lahaye at gmail.com> wrote:
> > Are you guys still using this?
> > If so, you should remove it IF there is no way to guarantee that it will
> > before NM picks up the device. At least it will avoid the crash...
> > I would ask in the NM community if there is a better way to disable a
> > particular device, like banning a device(?).
> Edit /etc/NetworkManager/NetworkManager.conf
> Add a line to the [main] section like
> no-auto-default=xx:xx:xx:xx:xx (obviously replacing the x's with the
> mac-address of your mesh device.)
This should be a lot cleaner solution.
However, two queries ::
Doing "ifconfig" on the XO-1, only shows information for "eth0" and "lo"
(no mesh device listed).
So, how can the mac address for the mesh device be found?
Are mac address for XO-1s, EXACTLY same, for every XO-1 on this planet?
Looking forward to a reply.
Thanks and Regards,
> This does not stop NM from managing your device, but does stop it from
> auto-connecting the device. You would still be able to go into NM and
> manually enable the mesh network. If you want NM to completely leave
> the device alone you can go one more step.
> Also in /etc/NetworkManager/NetworkManager.conf
> change the plugins line to
> Then add a section that looks like this.
> unmanaged-devices=mac:xx:xx:xx:xx:xx:xx (Where X's are the mac address
> of the device you want to ignore)
> Hope that helps, let me know if you have further questions.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel