Connman cannot be used in production of beaglebone wireless systems

In Jessie we have connman - and it causes severe problems if you try to build a number
of identical embedded systems, connman will assign a new service name to each processor.
So the settings directory has to be handcrafted separately for each. Even if you have a static
ip which is the same in all of them.
I have been unable to find a reliable way to get back to the /etc/network/interfaces paradigm.

Can somebody help? I’m unexpectedly against the wall.

Are you talking about the eth0 name that get's auto-generated?

That would be systemd, we force "net.ifnames=0" on the cmdline to fix this..

debian@beaglebone:~$ sudo ifconfig -a eth0
eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500
        inet 192.168.0.132 netmask 255.255.255.0 broadcast 192.168.0.255
        inet6 fe80::5265:83ff:feca:9234 prefixlen 64 scopeid 0x20<link>
        ether 50:65:83:ca:92:34 txqueuelen 1000 (Ethernet)
        RX packets 1636 bytes 256963 (250.9 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 91 bytes 12117 (11.8 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
        device interrupt 189

Or something else?, just "sudo apt remove connman --purge"...

Regards,

Can’t remove connman as the service will stop and ssh is dead. There might be a way to do things after disabling connman service but I don’t know what to do.

If you stop using conman, you can use /etc/network/interfaces, and that will give you a script you can use to configure all your network connections. If you use:-

man interfaces

it will tell you how to do it.

David