On 21 October 2015 at 13:27, Daniel Wagner <w...@monom.org> wrote: > On 10/21/2015 12:19 PM, Patrik Flykt wrote: > > Looks like there are two ways to tame this: have a main.conf entry or > > retry without sending a hostname. In the latter case people expecting > > their host name to be added to DNS will be surprised if there is > > something else going wrong in the network at the same time and their > > hostname is therefore not sent to the server. > > > > The first option will be clearer (will it?) to the user that no > > hostnames are sent and DNS therefore cannot be expected to work > > automatically. But of course this is now an option that hits all DHCP > > connection, not the presumably "faulty" one. OTOH with this main.conf > > one can prevent hostnames to be sent altogether. > > My take is to gather some traces from Windows and see how they solve > this kind of problem. Though someone else has to do it. Is someone > living in Utah and accesses to a CenturyLink DSL WiFi modem?
My recollection on this is that Windows does not use option 12 at all: clients do not request a hostname and servers won't provide it. My experience is from a few years ago (and might have been on an older OS even then) so testing that might still be useful. - Jussi _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
