Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe 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. Compatibility with Avahi question (KeithG)
----------------------------------------------------------------------
Date: Sun, 10 May 2020 17:37:59 -0500
From: KeithG <[email protected]>
Subject: Compatibility with Avahi question
To: [email protected]
Message-ID:
<cag17s_nenca3oitt5g7xgw8jarrbhdqxi1z9qaxychn4yi2...@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="0000000000009119dd05a552e2b5"
--0000000000009119dd05a552e2b5
Content-Type: text/plain; charset="UTF-8"
I am working on an open source Arch Arm based audio player. We used to sue
netctl, but that was a bit sloppy and slow. We then investigated
connman/iwd and have been impressed with the simplicity, speed, connection
reliability and also the 'just works' nature of it.
We have noticed that it does not seem to work very well with avahi, though.
Our device advertises itself on the LAN via avahi-daemon and will be
connected in this manner as well. What we notice is that mDNS access is
very slow and unuse-able in most cases. This will not fly for us. Is there
some setting or other incompatibility causing this or is it something
beyond connman that I just cannot figure out?
What I have tried and done:
1) Disabled systemd-resolved and enabled avahi-daemon - This seems to
interfere with avahi even if mDNS is disabled. If I use mDNS enabled with
systemd-resolved and enable the mDNS on the link, I can ping the host and
even connect to it, but still get broken javascript. For fastest IP based
connection as I have seen in the Firefox Console, I use
/run/connman/resolv.conf as a soft link to /etc/resolv.conf and have as my
nsswitch.conf hosts line this:
hosts: files mdns [NOTFOUND=return] dns
this gives very fast access via ip either v6 or v4, but broken web page
displays via *.local.
2) Enabled systemd-resolved and disabled avahi-daemon. This is slightly
faster to access the device, but the js is still broken and does not
display the page correctly. But this is not a solution as systemd-resolved
does not advertise any services, so it is a non-starter for this particular
project, so any mdns browse does not detect the server.
My next trick it to try systemd-resolved with iwd and see if it is any
better.
Basically: Is there any basic incompatibility with avahi and connman? I see
that connman can turn on mDNS on a per connection basis, but it is only
compatible with systemd-resolved according to this:Connman Config
<https://kernel.googlesource.com/pub/scm/network/connman/connman/+/master/doc/config-format.txt>.
Is there a reason for this?
Regards,
Keith
--0000000000009119dd05a552e2b5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>I am working on an open source Arch Arm based audio p=
layer. We used to sue netctl, but that was a bit sloppy and slow. We then i=
nvestigated connman/iwd and have been impressed with the simplicity, speed,=
connection reliability and also the 'just works' nature of it. <br=
></div><div>We have noticed that it does not seem to work very well with av=
ahi, though. Our device advertises itself on the LAN via avahi-daemon and w=
ill be connected in this manner as well. What we notice is that mDNS access=
is very slow and unuse-able in most cases. This will not fly for us. Is th=
ere some setting or other incompatibility causing this or is it something b=
eyond connman that I just cannot figure out? <br></div><div><br></div><div>=
What I have tried and done:</div><div>1) Disabled systemd-resolved and enab=
led avahi-daemon - This seems to interfere with avahi even if mDNS is disab=
led. If I use mDNS enabled with systemd-resolved and enable the mDNS on the=
link, I can ping the host and even connect to it, but still get broken jav=
ascript. For fastest IP based connection as I have seen in the Firefox Cons=
ole, I use /run/connman/resolv.conf as a soft link to /etc/resolv.conf and =
have as my nsswitch.conf hosts line this:<br></div><div>hosts: files mdns [=
NOTFOUND=3Dreturn] dns</div><div>this gives very fast access via ip either =
v6 or v4, but broken web page displays via *.local.</div><div>2) Enabled sy=
stemd-resolved and disabled avahi-daemon. This is slightly faster to access=
the device, but the js is still broken and does not display the page corre=
ctly. But this is not a solution as systemd-resolved does not advertise any=
services, so it is a non-starter for this particular project, so any mdns =
browse does not detect the server. <br></div><div><br></div><div>My next tr=
ick it to try systemd-resolved with iwd and see if it is any better. <br></=
div><div><br></div><div>Basically: Is there any basic incompatibility with =
avahi and connman? I see that connman can turn on mDNS on a per connection =
basis, but it is only compatible with systemd-resolved according to this:<a=
href=3D"https://kernel.googlesource.com/pub/scm/network/connman/connman/+/=
master/doc/config-format.txt">Connman Config</a>. Is there a reason for thi=
s? <br></div><div><br></div><div>Regards,</div><div><br></div><div>Keith<br=
></div></div>
--0000000000009119dd05a552e2b5--
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list -- [email protected]
To unsubscribe send an email to [email protected]
------------------------------
End of connman Digest, Vol 55, Issue 5
**************************************
