Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend

[Ajay Garg]

which actually brings me back to my original question ::

"""
Why is it so that putting the 'disable-mesh-script' in the 'start()' method
of '/etc/init.d/Networkmanager' works (always) for (re)boot; but never
works for resume-upon-suspend?
"""


Regards,
Ajay

On Tue, May 1, 2012 at 8:07 PM, Ajay Garg <ajay at activitycentral.com> wrote:

> Thanks Paul.
>
> On Tue, May 1, 2012 at 8:03 PM, Paul Fox <pgf at laptop.org> wrote:
>
>> ajay wrote:
>>  > Any ideas please, regarding the two latest queries :) ?
>>  >
>>  > Regards,
>>  > Ajay
>>  >
>>  > On Mon, Apr 30, 2012 at 1:00 PM, Ajay Garg <ajay at activitycentral.com>
>> wrote:
>>  >
>>  > > 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?
>>  > >> >
>>  > >>
>>  >
>> http://git.sugarlabs.org/dextrose-platform/mainline/blobs/master/etc/powerd/post
>>  > resume.d/disable_mesh.sh
>>  > >> >
>>  > >> > If so, you should remove it IF there is no way to guarantee that
>> it
>>  > >> will run
>>  > >> > 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 ::
>>  > >
>>  > >
>>  > > a)
>>  > > 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?
>>
>> it's the same as that for eth0.
>>
>
> Does that mean, that banning eth0-mac-address prevent the loading of
> wifi-hardware-device as well (in obvious addition to mesh) ?
> This seems very pricky.
>
>
>
>
>
>>
>>  > > b)
>>  > > Are mac address for XO-1s, EXACTLY same, for every XO-1 on this
>> planet?
>>
>> of course not.  how would they tell one another apart?
>>
>
> Alright.
> But my first doubt (same mac address for mesh-hardware and wifi-hardware)
> has put me in topspin :~
>
>
>
> Regards,
> Ajay
>
>
>
>
>
>>
>> paul
>>
>>  > >
>>  > >
>>  > > Looking forward to a reply.
>>  > >
>>  > >
>>  > >
>>  > > Thanks and Regards,
>>  > > Ajay
>>  > >
>>  > >
>>  > >
>>  > >>
>>  > >> 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
>>  > >>
>>  > >> plugins=ifcfg-rh,keyfile
>>  > >>
>>  > >> Then add a section that looks like this.
>>  > >>
>>  > >> [keyfile]
>>  > >> 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.
>>  > >>
>>  > >> -Jon
>>  > >>
>>  > >
>>  > >
>>  > part 2     text/plain                 129
>>  > _______________________________________________
>>  > Devel mailing list
>>  > Devel at lists.laptop.org
>>  > http://lists.laptop.org/listinfo/devel
>>
>> =---------------------
>>  paul fox, pgf at laptop.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20120501/ed6de6e3/attachment.html>