Hi Marcel, On Fri, Mar 11, 2011 at 02:13:33PM -0800, Marcel Holtmann wrote: > Hi Samuel, > > > > >> + boolean 6to4 [readonly] > > > >> + > > > >> + If set to true, the service will create > > > >> 6to4 > > > >> + tunnel if the service IPv4 address is > > > >> not > > > >> + private. Default value is false meaning > > > >> that > > > >> + 6to4 tunnel is not created. Only one > > > >> tunnel > > > >> + is created even if there are more than > > > >> one > > > >> + active service that have public IPv4 > > > >> address. > > > >> + Tunnel is created if it provides > > > >> internet > > > >> + connectivity. > > > > So I'd like to simplify that and really leave it as a readonly > > > > property. > > > > > > So user would not be able to disable 6to4 then, is this really what we > > > want to do? > > > > > Yes, I think that is fine. > > exposing these configuration capabilities to users is not helping us to > create a smooth IPv6 experience. > > However instead of this property we might do IPv6.Method = 6to4 to give > the UI a hint in how we have IPv6 setup. I agree this would somehow hide the 6to4 complexity from the user. However I found this slightly awkward as a) 6to4 is a subset of the autoconf method and b) we would expose an IPv6 method that is different from the default one or the one explicitely set by the user. Also, we'd have to special case the 6to4 method when saving it to our profile and convert it to an autoconf method.
Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ _______________________________________________ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
