Thanks for the suggestion, but being that I am unfamiliar with suse, I'll
need a bit more guidance on 'how' to do that. This is on an RPi and is
headless as I am connected by ssh to it.
I am at a loss as to how to help resolve this and really want to help get
It appears that connman1.38 will initiate a scan via 'connmanctl scan wifi'
even though it does not report that it has scanned. The git version
(1.38.r23) will report on the cli that it has scanned. So, that is an
If I use either 1.38 (the current Arch Linux package) or build it from git,
I cannot ge tthe Rpi or my laptop to reconnect when the ssid is rebooted
even though the 'services' for the SSID
show that it is 'autoconnect' and monitor-connman shows that is 'ses' it.
Is there some main.conf setting that I have wrong?
FallbackNameservers = 18.104.22.168,22.214.171.124
DefaultAutoConnectTechnologies = ethernet,wifi
AllowHostnameUpdates = false
AlwaysConnectedTechnologies = ethernet,wifi
AutoConnectRoamingServices = true
As I said previously, the only modifications to the build of the connman
package under Arch are that it adds that dbus 'Agent' bits and also that it
deletes the tmpfiles.d in the package that calls out a /var/run directory
because Arch uses /run/. Other than that it is built under Arch as it is
called out in the git to be built.
From my testing, ./monitor-connman seems to 'see' the ssid return, but will
not reconnect after the router is rebooted.
If I use systemd-networkd and iwd, it reconnects every time. With connman
and iwd, I get no reconnect over a reboot.
How can I help resolve this? We have spent a lot of time and effort getting
our UI to work according to the connman manual and if it cannot reconnect
over a reboot is it kind of useless to us on our headless music player. I
have build capability and rpis and laptops with brcm as well as intel cards
to test things. I am willing to try stuff and can test and, hopefully,
respond with decent feedback, I just do not know how to modify connman to
On Wed, Sep 30, 2020 at 1:26 PM Michael Nazzareno Trimarchi <
On Wed, Sep 30, 2020 at 8:03 PM KeithG <ys3al35l(a)gmail.com> wrote:
> Tried installing opensuse on the RPi. It installs, but when I try to run
iwd, I get:
> Sep 30 12:56:35 localhost iwd: RC4 support not found
> Sep 30 12:56:35 localhost iwd: The following options are missing
in the kernel:
> Sep 30 12:56:35 localhost iwd:
> Sep 30 12:56:35 localhost iwd: CONFIG_CRYPTO_ECB
> Sep 30 12:56:35 localhost iwd: CONFIG_CRYPTO_ARC4
> I am unfamiliar with it. How would I set up connman/iwd on this minimal
You can re-package the kernel with that option enabled
> On Wed, Sep 30, 2020 at 8:52 AM Daniel Wagner <wagi(a)monom.org> wrote:
>> On Wed, Sep 30, 2020 at 07:40:43AM -0500, KeithG wrote:
>> > Hmmm, Agent as in 'connmanctl> agent on'?
>> > Which distro are you using?
>> I used for a long time Fedora, since a year Tumbleweed.
>> > On the RPIs, I do not believe that raspbian
>> > (whatever it is called now) has kernel support for iwd so I don't
>> > that it is a candidate for an investigation.
>> Raspian is likely not working out of the box. IIRC, Fedora and
>> Tumbleweed are available for RPIs, though I don't have any experience
>> with it. So I can't really say anything useful on it.
>> > I could be wrong, though and
>> > the current version might. I do have 2 laptops with Arch on them
>> > and can install something else on one of them. I find it strange that
>> > Arch Linux installs fail in this test and would like to see if a
>> > distro may behave differently. It would be preferable that it run on
>> > RPi, but I could put it on the laptop...
>> It's not strange. You can't assume upstream projects ship for every
>> distro the correct integration/configuration option. The udev/systemd
>> files in the ConnMan tree are examples which need to be tweak by the
> connman mailing list -- connman(a)lists.01.org
> To unsubscribe send an email to connman-leave(a)lists.01.org
Michael Nazzareno Trimarchi
Amarula Solutions BV
Cruquiuskade 47 Amsterdam 1018 AM NL