On Fri, 2014-12-19 at 10:12 +0000, Pasi Sjöholm wrote: >> 3) Connect and query service from connman and you will see 2001::1 and >> 2001::2 plus slaac&dhcpv6 provided nameservers 2001::3 and 2001::4. >> With the patch applied, the nameservers at point 3 will be only the >> slaac&dhcpv6 provided 2001::3 and 2001::4. >So what is the problem then of having nameservers 1, 2, 3 and 4 in use >at the same time? Is it that: >- 1 and 2 don't respond when connecting via DHCPv6/autoconfiguration?
They might or might not depending on the configuration on the operators side. >- the specification says 1 and 2 must not be used for whatever reason > when 3 and 4 are provided by DHCPv6/autoconfiguration? I don't think there is such specification. :) They could even be the same as 1 and 2 depending on how they are presented. E.g. 2001:0:0:0:0:0:0:1 vs. 2001::1 (at least connman accepts both as valid configuration). > And do we even care about that if 1 and 2 work anyway? IMO, it is just that it is old configuration from non-active context which we should not keep around. Other thing which I have to consider is that those nameserver will be queried in any way and in a roaming case that means extra costs even it's small-minded but it is still costing for the end user. >If DHCPv6/autoconfiguration does not give any nameservers, the one >pushed from oFono are suddenly really good to have... Yes, especially in a case where the ipv4 dns-addresses are not provided. >It is not ofono but connman using the outdated information. >The nameserver information is not "outdated" if it comes from the oFono >plugin and the proper D-Bus message. If nameservers 1 and 2 are not >supposed to be used with DHCPv6/autoconfiguration, then oFono should not >be sending this information in the first place. It is the information from ipv6-pdp connection which has been disconnected, then the configuration has been changed in ofono to setup dual/ipv4v6 session instead. So it is outdated information from a previous session.. ofono will not maintain information about the previously sent nameservers and will not resend them. The nameservers 1/2 are not included in the new message received when the context is re-activated/connected after the pdp-type has been changed to dual/ipv4v6. >It is not the >responsibility of the application (== ConnMan) to interpret which parts >of the message to use; all information provided by oFono will be >exploited to the full extent possible. The main problem is that the configuration used is from a previous active context and not the current context. If you see the Patch 6/6 it works out the very same issue on interface ip-addresses/gateway-level.. if we do not set the method to _UNKNOWN the connman will use the old configuration values from previous contexts. Eg. connman would setup ipv6-address from previous context after user has changed the pdp-type from ipv6 to ip(v4). The only valid configuration is what ever is sent on each context-activation, and connman needs to drop the old configuration values. Br, Pasi _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
