10:52 a.m.
On Feb 26, 2016, at 1:57 AM, connman-request(a)lists.01.org wrote:
On Thu, 2016-02-25 at 10:52 -0800, wangfe-nestlabs wrote:
> Background information.
>
> Connmand will not use fallback name servers when some name servers are
> provided by DHCP reply. But in some cases, the ISP provided its own
> name servers can?t be down, then DNS won?t work. So some requirement
> is to use some fallback name severs such as 8.8.8.8, 8.8.4.4 for
> backup.
>
> Add the option flag ?AlwaysUseFallbackNameservers?. Which it is
> enabled, the fallback name servers are appended to name server list,
> and will be used. The duplicate servers will be filtered out in the
> __connman_service_nameserver_append.
NACK. FallBackNameservers are just that, a list of servers to use when
there are zero nameservers provided otherwise. Every service has already
a Nameservers.Configuration attribute which takes precedence over the
ones provided by DHCP.
Patrik,
It’s easy to see how this is done one-off, statically for a provision or via a
per-service-specific configuration setting using Nameservers.Configuration.
However, what’s the recommended way to ensure that nameservers can be configured, via
Nameservers.Configuration, and applied to all services, without regard to their technology
type or the service name?
The use case here is that a particular ISP supplies DNS servers in DHCP. However, their
DNS servers are notoriously flaky and non-responsive (i.e. failed average response rate is
high). Consequently, given how conman’s DNS proxy functions, statically-configured servers
are a stopgap guarantee that will work even when the DHCP-provided servers do not.
Best,
Grant
2:27 a.m.
New subject: [PATCH] Add AlwaysUseFallbackNameservers flag in the configuration file.
Hi,
On Fri, 2016-02-26 at 07:52 -0800, Grant Erickson wrote:
It’s easy to see how this is done one-off, statically for a
provision
or via a per-service-specific configuration setting using
Nameservers.Configuration.
However, what’s the recommended way to ensure that nameservers can be
configured, via Nameservers.Configuration, and applied to all
services, without regard to their technology type or the service name?
The use case here is that a particular ISP supplies DNS servers in
DHCP. However, their DNS servers are notoriously flaky and
non-responsive (i.e. failed average response rate is high).
Consequently, given how conman’s DNS proxy functions,
statically-configured servers are a stopgap guarantee that will work
even when the DHCP-provided servers do not.
So your use case actually continues that all services on the device end
up using the same ISP and it's flaky DNS servers, right?
Usually different WiFi, ethernet and cellular serivces end up using
different ISPs and therefore different DNS servers, leaving only a
subset of the services to be of the flaky kind. For these the option is
to configure them a priori through .config files or after empirical
evidence via D-Bus, as you pointed out.
Cheers,
Patrik
1:07 p.m.
New subject: [PATCH] Add AlwaysUseFallbackNameservers flag in the configuration file.
Hi Patrik,
The device only supports wifi service. The DNS servers got from ISP through DHCP is
flaky. To make DNS work better, user can specify some backup DNS servers.
And this feature is configurable, by default it is turned off. Only some users
experienced such problem can turn it on.
Thanks,
Feng
On Feb 28, 2016, at 11:27 PM, Patrik Flykt
<Patrik.Flykt(a)linux.intel.com> wrote:
Hi,
On Fri, 2016-02-26 at 07:52 -0800, Grant Erickson wrote:
> It’s easy to see how this is done one-off, statically for a provision
> or via a per-service-specific configuration setting using
> Nameservers.Configuration.
>
> However, what’s the recommended way to ensure that nameservers can be
> configured, via Nameservers.Configuration, and applied to all
> services, without regard to their technology type or the service name?
>
> The use case here is that a particular ISP supplies DNS servers in
> DHCP. However, their DNS servers are notoriously flaky and
> non-responsive (i.e. failed average response rate is high).
> Consequently, given how conman’s DNS proxy functions,
> statically-configured servers are a stopgap guarantee that will work
> even when the DHCP-provided servers do not.
So your use case actually continues that all services on the device end
up using the same ISP and it's flaky DNS servers, right?
Usually different WiFi, ethernet and cellular serivces end up using
different ISPs and therefore different DNS servers, leaving only a
subset of the services to be of the flaky kind. For these the option is
to configure them a priori through .config files or after empirical
evidence via D-Bus, as you pointed out.
Cheers,
Patrik
3:09 a.m.
New subject: [PATCH] Add AlwaysUseFallbackNameservers flag in the configuration file.
Hi,
On Mon, 2016-02-29 at 10:07 -0800, wangfe-nestlabs wrote:
The device only supports wifi service. The DNS servers got from ISP
through DHCP is flaky. To make DNS work better, user can specify
some backup DNS servers. And this feature is configurable, by default
it is turned off. Only some users experienced such problem can turn
it on.
Perhaps Nameservers.Config or Nameservers in the .config file if the
service is provisioned can then be set to some useful values, as this
applies only to a certain ISP.
Cheers,
Patrik
1704
days inactive
1708
days old
3 comments
3 participants
participants (3)
-
Grant Erickson -
Patrik Flykt -
wangfe-nestlabs