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
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.
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
Furthermore, not only ethernet interfaces should be addressed.