Your message dated Sat, 17 Feb 2018 13:52:54 +0100
with message-id <[email protected]>
and subject line Re: connman: Failed to set domainname
has caused the Debian Bug report #883926,
regarding connman: Failed to set domainname
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
883926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883926
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: connman
Version: 1.35-2
Severity: normal
Tags: patch


I am using connman with ethernet only. journalctl reports

 Failed to set domainname to lan

Adding CAP_SYS_ADMIN to CapabilityBoundingSet in the service file
does set the domainname and other machines on the local network
can now be contacted.

Regards,

Brian.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.14.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages connman depends on:
ii  dbus          1.12.2-1
ii  iptables      1.6.1-2+b1
ii  libc6         2.25-3
ii  libdbus-1-3   1.12.2-1
ii  libglib2.0-0  2.54.2-1
ii  libgnutls30   3.5.16-1
ii  libreadline7  7.0-3
ii  libxtables12  1.6.1-2+b1
ii  lsb-base      9.20170808

Versions of packages connman recommends:
pn  bluez          <none>
pn  ofono          <none>
ii  wpasupplicant  2:2.6-13

Versions of packages connman suggests:
pn  connman-vpn  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Brian,

thanks for your suggestion - imho givin CAP_SYS_ADMIN as default is not
the very best of all ideas - please see the upstream discussions about.
(https://lists.01.org/pipermail/connman/2017-August/022037.html ff )

For what it is worth, the domainname update fuctionality is deprecated
iirc, i hope for a clean solution with the upcoming connman release.

Cheers Alf

--- End Message ---

Reply via email to