Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Stale Wifi service and network not being destroyed?
(Daniel Wagner)
2. Re: IFA_F_PERMANENT always set (Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Sun, 10 Mar 2019 19:53:52 +0100
From: Daniel Wagner <[email protected]>
To: Henrik Persson <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: Stale Wifi service and network not being destroyed?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi Henrik,
On Thu, Feb 28, 2019 at 11:17:12AM +0000, Henrik Persson wrote:
> network->{driver,device} being NULL explains why -EIO is returned. I'm
> thinking
> that should not happen. I also found another connman_network when digging
> into what the supplicant interface was seeing, and that's not the same network
> that the service holds a reference to..
network->driver is set to NULL in network_remove(). I don't thin
network_probe() is involved in your scenario. That would indicate that
wpa_s decided to remove the network.
> Any pointers, suggestions, comments, etc that could either tell me that
> I'm doing something wrong interacting with connman, or where to look
> further?
I think trying to get hold on the logs would be a good starting point,
so the connman log and the wpa_supplicant log. Furthermore, set the
CONNMAN_SUPPLICANT_DEBUG environment variable. That should give you
what ConnMan thinks wpa_supplicant is doing.
BTW, which version of wpa_s are you using?
> I'm on connman 1.35 btw because of reasons, but I didn't find anything
> in the connman history since that point that should have fixed this. But
> I'm gladly proven wrong.
I suggest to give the current HEAD a try, we never know :)
Thanks,
Daniel
------------------------------
Message: 2
Date: Sun, 10 Mar 2019 19:56:28 +0100
From: Daniel Wagner <[email protected]>
To: Nuno Gon?alves <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: IFA_F_PERMANENT always set
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
Hi Nuno,
On Fri, Mar 08, 2019 at 05:35:24PM +0100, Nuno Gon?alves wrote:
> I noticed that unlike other network managers, connman always sets ifa_flags
> = IFA_F_PERMANENT, regardless if DHCP is in use.
>
> Because of this, ip addr, for example, never reports "dynamic" for the IPv4
> address when DHCP is in use.
>
> Is there a reason for this?
No, I don't think so. It is likely just a 'missing' feature. It looks
no one cared to fix up the code path from the DHCP source to the code
snippet where we set the flag.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 41, Issue 11
***************************************
