Re: NMClient.IP4Config get_addresses() not always populated when signal 'notify::ip4-config' is fired

[Sylvain Garaud <garaud gmail com>]

Hello Dan,

Yes this is working good. I will implement the s

Connecting to wlp5s0
Connecting to enp4s0
Connecting to lo
(wlp5s0) notify IP4Config (state 100)
(wlp5s0) IPv4 addresses
    192.168.0.6/24  192.168.0.1
(lo) notify IP4Config (state 10)
(lo) IPv4 addresses
    127.0.0.1/8  0.0.0.0
(lo) IPv4 addresses
    127.0.0.1/8  0.0.0.0
(enp4s0) notify IP4Config (state 100)
(enp4s0) IPv4 addresses
    192.168.0.5/24  192.168.0.1

On Tue, Mar 31, 2015 at 5:12 AM, Dan Williams <dcbw redhat com> wrote:

On Thu, 2015-03-26 at 12:33 -0500, Dan Williams wrote:
> On Thu, 2015-03-26 at 12:29 -0500, Dan Williams wrote:
> > I've attached an updated notify-ips.py script that shows what should be
> > done here.  Let me know if you have any questions!
>
> Apologies, I attached the wrong version of the script.  The correct one
> is now attached.

Any luck with this script?

Dan