Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread wkitty42
On 12/20/2016 07:26 PM, Markus Hartung wrote: $ cat /var/lib/misc/dnsmasq.leases 1482365715 3e:XX:XX:XX:XX:02 192.168.1.184 * 01:3e:XX:XX:XX:XX:02 1482334524 00:YY:YY:YY:YY:67 192.168.1.133 hostname * I have masked the MAC-address, MACs are only good on the local link... once through a router

Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread Markus Hartung
On 2016-12-20 12:14, Toke Høiland-Jørgensen wrote: Well, arguably the Windows 10 behaviour is a feature - RFC7217 was written because the EUI-64 based approach has privacy issues (the client will use the same address on every network). So I would expect more and more clients to adopt the privacy

[Dnsmasq-discuss] odd dhcp server issue and confused by dhcp-option

2016-12-20 Thread Paul J R
Hi All, Im on an ubuntu 16.04 machine and was trying to setup a quick dhcp server for a test with some wifi equipment that needs a custom dhcp option (43) and ran into two problems I couldn't find my way around. The first was serving dhcp in the first place. Had two ethernet interfaces in th

Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread Ziggy SpaceRat
Toke Høiland-Jørgensen wrote: > will use the same address on every network). So I would expect more and > more clients to adopt the privacy-preserving approach. I believe > NetworkManager has support for it on Linux, but am not sure if it's > enabled by default. New installations of Debian and Ubu

Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread Pali Rohár
On Tuesday 20 December 2016 12:14:19 Toke Høiland-Jørgensen wrote: > Markus Hartung writes: > > On 2016-12-19 06:18, Toke Høiland-Jørgensen wrote: > >> Markus Hartung writes: > >> > >> ... > >> My guess is that Windows 10 implements RFC7217: > >> https://tools.ietf.org/html/rfc7217 > >> > >> If

Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread Toke Høiland-Jørgensen
Markus Hartung writes: > On 2016-12-19 06:18, Toke Høiland-Jørgensen wrote: >> Markus Hartung writes: >> >> ... >> My guess is that Windows 10 implements RFC7217: >> https://tools.ietf.org/html/rfc7217 >> >> If this is the case, there is no way for dnsmasq to predict the IPv6 >> address of a new

[Dnsmasq-discuss] ProxyDHCP replies on invalid range

2016-12-20 Thread Alkis Georgopoulos
Hi, I've filed this as a bug report in launchpad, but I'm forwarding it here as well upon request: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1651044 In Ubuntu 16.04, I've configured dnsmasq to reply on subnet=10.160.37.0/24, yet it replies even when it gets an IP on subnet=10.161

Re: [Dnsmasq-discuss] Windows ipv6 hostname

2016-12-20 Thread Michael Stilkerich
Hello Markus, Windows 10 by default uses randomized identifiers instead of the MAC address. You can turn this off using the following command in an admin shell: netsh interface ipv6 set global randomizeidentifiers=disabled In addition to that, make sure that the Windows computer replies to