Hi Patrik, We do not need DNS on other interfaces when ConnMan is running on an nfsroot. We cannot tether as eth0 is ignored, so this is less of a concern for us. For now, DNS is not handled by ConnMan properly so we get a blank /etc/resolv.conf with 'Generated by Connection Manager' which will overwrite our /etc/resolv.conf which was previously populated from procfs.
I have submitted an alternate patch which allows /etc/resolv.conf to be saved in another location Sam ________________________________________ From: connman <[email protected]> on behalf of Patrik Flykt <[email protected]> Sent: 07 September 2015 13:36 To: [email protected] Subject: Re: [PATCH] resolver: allow writing to /etc/resolv.conf to be disabled Hi, On Fri, 2015-09-04 at 14:29 +0000, Sam Nazarko wrote: > When OSMC uses an nfsroot, we ignore the primary interface (eth0), as > the kernel is handling the network connection itself. Currently, > without this patch, ConnMan will try and update /etc/resolv.conf, but > may not have sufficient 'knowlege' to be able to accurately do so. We > still want ConnMan to handle other technologies on the system, such as > Bluetooth. Whether we used DHCP for DNS servers or configured it > statically, it is obtainable from procfs. For DHCP we can > use /proc/net/pnp and for static configuration we can populate > via /proc/cmdline. How is DNS handled when ConnMan uses Bluetooh, WiFi etc. other networks than the primary eth0 ethernet? /proc/net/pnp and /proc/cmdline are only relevant for the primary eth0 nfsroot interface. Cheers, Patrik _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
