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. connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway (KARBOWSKI Piotr)
2. Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway (Vasyl Vavrychuk)
3. Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway (KARBOWSKI Piotr)
4. Re: [PATCH v1 0/5] Retry NTP servers periodically on startup
(Daniel Wagner)
5. Re: [PATCH 0/3] Fixes and extensions for WPS support
(Jose Blanquicet)
6. Re: [PATCH 0/3] Fixes and extensions for WPS support
(Jose Blanquicet)
7. Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway (Daniel Wagner)
8. Re: [PATCH v2 0/3] Fixes and extensions for WPS support
(Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Sat, 20 Jan 2018 22:21:51 +0100
From: KARBOWSKI Piotr <[email protected]>
To: [email protected]
Subject: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
I have connman built with `--disable-ethernet`. However, every time I
start connmand, the configuration of eth0 interface is wiped.
Is there a way to make connman not touch my wired interfaces? I tried to
set 'Enabled' option in /var/lib/connman/settings to both true and false
in the '[Wired]' part, but nothing changed, connman keeps wiping my
runtime configuration.
-- Piotr.
------------------------------
Message: 2
Date: Sat, 20 Jan 2018 23:26:40 +0200
From: Vasyl Vavrychuk <[email protected]>
To: KARBOWSKI Piotr <[email protected]>
Cc: [email protected]
Subject: Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway
Message-ID:
<cagj4m+6zjcytcpuk-1adssogovwckcx4om6ujzzakhycdio...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Have you tried putting eth to blacklist in connman conf file? Check
'man connman.conf' for details.
On Sat, Jan 20, 2018 at 11:21 PM, KARBOWSKI Piotr
<[email protected]> wrote:
> Hi,
>
> I have connman built with `--disable-ethernet`. However, every time I start
> connmand, the configuration of eth0 interface is wiped.
>
> Is there a way to make connman not touch my wired interfaces? I tried to set
> 'Enabled' option in /var/lib/connman/settings to both true and false in the
> '[Wired]' part, but nothing changed, connman keeps wiping my runtime
> configuration.
>
> -- Piotr.
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
------------------------------
Message: 3
Date: Sat, 20 Jan 2018 22:37:03 +0100
From: KARBOWSKI Piotr <[email protected]>
To: Vasyl Vavrychuk <[email protected]>
Cc: [email protected]
Subject: Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 01/20/2018 10:26 PM, Vasyl Vavrychuk wrote:
> Have you tried putting eth to blacklist in connman conf file? Check
> 'man connman.conf' for details.
Blacklisting eth0 does work, however I'd consider it a workaround rather
than a way to do it. Shouldn't connman touch only wireless interfaces
whe there's --disable-ethernet? I noticed it also does wipe my bridges.
-- Piotr.
------------------------------
Message: 4
Date: Sun, 21 Jan 2018 16:24:08 +0100
From: Daniel Wagner <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [PATCH v1 0/5] Retry NTP servers periodically on startup
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 01/17/2018 08:50 AM, Daniel Wagner wrote:
> This is the attempt to fix the outstanding CM-636 bug. This is still
> not completely finished. There is some more potential to cleanup the
> timeserver code. But I thought maybe someone wants to test it. You can
> install a iptables rule to see if the retry logic works.
>
> iptables -A OUTPUT -p tcp --dport 123 -j DROP
> iptables -A OUTPUT -p udp --dport 123 -j DROP
>
> This should do the trick.
After some more debugging and removing of the unnecessary DBG() I
applied this.
Thanks,
Daniel
------------------------------
Message: 5
Date: Sun, 21 Jan 2018 17:02:48 +0100
From: Jose Blanquicet <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: Robert Tiemann <[email protected]>, [email protected]
Subject: Re: [PATCH 0/3] Fixes and extensions for WPS support
Message-ID:
<cafc8ijjikcio15zb2pframrajg4eq+e3yo9kbt51d9xl7by...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
On Wed, Jan 17, 2018 at 9:03 AM, Daniel Wagner <[email protected]> wrote:
> Any objection to Robert's v2? Apart of the comment thingy it looks ready to
> be merged.
No, looks fine to me too.
Cheers,
Jose
------------------------------
Message: 6
Date: Sun, 21 Jan 2018 17:50:09 +0100
From: Jose Blanquicet <[email protected]>
To: Robert Tiemann <[email protected]>
Cc: [email protected], Daniel Wagner <[email protected]>
Subject: Re: [PATCH 0/3] Fixes and extensions for WPS support
Message-ID:
<CAFC8iJKi3n=3upqAX6tNGouvU1oz+K+TKSSiMddP+=z=orb...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Robert,
On Wed, Jan 17, 2018 at 9:27 AM, Robert Tiemann <[email protected]> wrote:
>> If we will go ahead, I think that maybe it's worth to generate a
>> PropertyChanged signal to notify Security property has changed when
>> wps_adversing is added/removed.
>
> This would be helpful indeed. My current client code constantly scans
> for WLANs and reads out all data of all services on _any_ change
> reported. Not very efficient, but it turned out to be the most
> reliable way to keep up with changes.
I would say that avoid doing that is exactly the reason why signals are used :)
> Alternatively, wps_advertising could be turned into a property in its
> own right, outside of Security in case Security is not supposed to
> change. I just thought it would make sense to put it into Security.
I would rather add it into the Security property. Let's see what
Daniel thinks about it.
> I guess to generate the PropertyChanged signal, a function similar to
> strength_changed() would be needed which calls
> connman_dbus_property_changed_array(), right?
Yes.
> Shall I prepare two patches (one for the signal, one for the docs)?
Yes, please divide it into two patches.
Thanks,
Jose
------------------------------
Message: 7
Date: Sun, 21 Jan 2018 19:42:16 +0100
From: Daniel Wagner <[email protected]>
To: KARBOWSKI Piotr <[email protected]>, Vasyl Vavrychuk
<[email protected]>
Cc: [email protected]
Subject: Re: connman built with `--disable-ethernet` wipe ethernet
interface configuration on start anyway
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Piotr,
On 01/20/2018 10:37 PM, KARBOWSKI Piotr wrote:
> On 01/20/2018 10:26 PM, Vasyl Vavrychuk wrote:
>> Have you tried putting eth to blacklist in connman conf file? Check
>> 'man connman.conf' for details.
>
> Blacklisting eth0 does work, however I'd consider it a workaround rather
> than a way to do it. Shouldn't connman touch only wireless interfaces
> whe there's --disable-ethernet? I noticed it also does wipe my bridges.
One of ConnMan's expectation is to control all interfaces. This is why
it tries to wipe all configuration at startup to avoid configuration
collisions.
src/device.c:
static void cleanup_devices(void)
{
/*
* Check what interfaces are currently up and if connman is
* suppose to handle the interface, then cleanup the mess
* related to that interface. There might be weird routes etc
* that are related to that interface and that might confuse
* connmand. So in this case we just turn the interface down
* so that kernel removes routes/addresses automatically and
* then proceed the startup.
*
* Note that this cleanup must be done before rtnl/detect code
* has activated interface watches.
*/
[...]
}
The ignore interface is the simplest way to avoid the cleanup code.
plugins/ethernet.c is not compiled in when --disable-ethernet is used
and there is no connection to the code snippet above. That is why
ConnMan wipes your configuration.
Not sure what the best way is to address this.
Some ideas:
1) The ignore device code is already there and works. So no more code
needed, no code bloat and works.
2) Adding a no-ethernet plugin which adds all ethernet interfaces to the
ignore list. Do we want to support interface renaming?
3) Teaching the core to ignore the ethernet devices when
--disable-ethernet is used (filter devices out with
CONNMAN_DEVICE_TYPE_ETHERNET).
Furthermore, not only ethernet interfaces should be addressed.
Thoughts?
Thanks,
Daniel
------------------------------
Message: 8
Date: Sun, 21 Jan 2018 19:51:51 +0100
From: Daniel Wagner <[email protected]>
To: Robert Tiemann <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH v2 0/3] Fixes and extensions for WPS support
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Robert,
On 01/15/2018 10:15 AM, Robert Tiemann wrote:
> Allow clients to identify WPS registrars.
>
> Note that I am actually not quite happy with patch 3 because I have
> copied some parts from network_added() to network_changed() in
> plugins/wifi.c. Maybe it would be good to refactor it later to avoid
> code duplication.
>
> v2:
> - Improve commit message.
> - Fix warnings reported by checkpatch.pl.
All patches applied (updated the comment in patch #3).
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 27, Issue 17
***************************************
