connman to replace ceni

[paxmark2]

systemd-220 and  debian bug # 787263.  Connman is suggested as  an option to using ceni in a posting

Going to the connman webpage and the "Who It's for" section is a bit deterring

ConnMan is utilized primarily by operating system vendors, system builders (including system Integrators and Original Device Manufacturers) who are building customized Linux solutions.

However the documentation from the git pages is quite readable and seems to be a fit for an IPV4 box using openvpn  wlan0 and ethh0.   

Is anyone else utilizing connman here and is the editing of the .config files straightforward?    My tentative plan of aciton is to go to connman and then sometime in the next week dist-upgrade to systemd-220


Sigh, I first used ceni for a wheezy-testing #! netbook, I like ncurses and it worked.  But things change. 

EDIT addition.  I tried connman on a 220gb hdd that I have debian testing on with weston and wayland (no X).  Worked perfect with no interreaction on my part on a eth0 only network testing amd64

[krisbee]

Short Anwser – No ,I'm not considering connman at the moment.  I'd only need it for a wired connection.

Long Answer – As of today, I've not moved from systemd 215-18 to systemd 220 due to the ceni bug, which may get a fix soon (?).  I've just reverted to Network Manager, but this seemed to introduce added latency to web surfing.  Assuming this problem was real, and not just my imagination, I decided to go back to ceni and wait.  But now ceni doesn't want to work! WTF! No hardware devices are displayed on the first ceni screen.  My workaround for now was to configure /etc/network/interfaces but hand,then just put “ifup eth0” in /etc/rc.local and let systemd's rc-local.service do to its thing so the connection is up before login to desktop.

[melmarker]

waiting until the fixed packages hit sid will solve that problem

[krisbee]

waiting until the fixed packages hit sid will solve that problem

Not for me.  I purged Network Manager, then did a full D-U:

Code: [Select]

apt-cache policy systemd
systemd:
  Installed: 220-3
  Candidate: 220-3
  Version table:
 *** 220-3 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status


But I'm still left with the Ceni problem.  Ceni doesn't show any hardware interfaces & cannot be used to configure anything.

[ see : http://postimg.org/image/isdqf0cc7/ ]

[der_bud]

krisbee, perhaps you hit exactly the sync and udev didn*t update? Or you forgot to reboot ?

[krisbee]

krisbee, perhaps you hit exactly the sync and udev didn*t update? Or you forgot to reboot ?

Nope, I rebooted and udev is latest and udev rule  "/etc/udev/rules.d/70-persistent-net.rules" has not changed:

Code: [Select]

apt-cache policy udev
udev:
  Installed: 220-3
  Candidate: 220-3
  Version table:
 *** 220-3 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        100 /var/lib/dpkg/status

So I've no idea what's happened to ceni.  Guess, I'll just reinstall Network Manager for now, while I try to make sense of systemd-networkd.

[paxmark2]

As it often is Arch wiki has info

https://wiki.archlinux.org/index.php/Connman

For the github to get more info on connman

https://git.kernel.org/cgit/network/connman/connman.git/tree/doc

apt-get install connman wiped most (maybe not all) of network-manager on a debian testing (sparkyLinux) KDE setup on an atom netbook. A shutdown started the connmand daemon.   Additon of the siduction lxqt reopository to sources  and apt-get install cmst gave a functional QT5 gui to connman.    wifi set up was easy. 

One thing I forget is that the interactive part of connman is connmanctl 

edit added  later.  I installed connmand and cmst to my favourite siduction lxqt Indian Summer - still at systemd 215-18  Unable to get wifi up, it talks about a bus problem.  Unable to accomplish in cli or in cmst.  With  "connmanctl monitor" running in a root terminal and triggering the error message in cmst, no error logged in terminal.  Going to lurk for a bit, other plans for weekend.  Nice thing about connman is that it is quite good at setting up eth0 (which it calls ethernet)  automagically.  Back to ceni and still at systemd 215-18. 

[melmarker]

paxmark2: cmst is available from extra - p.s.o/lxqt is a repo for sid-users compiled without any siduction dependencies

[paxmark2]

systemd-220.5 and connman works in Siduction with lxqt. I was unsuccessful with systemd-220.18 and do not know what the problem(s) was, but it may have been dbus related. It just works now with systemd-220  Prior it also worked with systemd-215-18 on two versions of testing on 2 other computers.

I start my vpn up in tty2 as I did with ceni, still trying to figure out connman-vpn   

I was stumped at getting wifi up via cli.  The command "connmanctl agent on" did not work.  Going into the shell mode "connmanctl" and then after seeing conmanctl> entering "agent on" did work.

EDIT:  I have had no problems with cmst in Sparky testing -KDE. In Siduction the (dbus?) thing in systemd-215-18 was not a cmst bug and cmst works quite well with 220-5.

I needed cli for connman for my net-install wayland-weston to set up a usb-wifi.   I doubt if  cmst is ready for bare wayland-weston yet.  Thanks melmarker.

[melmarker]

if something with cmst don't work - please file a bug @ https://github.com/andrew-bibb/cmst