On Monday 26 December 2016 14:50:41 Markus Hartung wrote:
> >For dhcpv6 I have own dnsmasq patches which assign ipv6 address
> >bases on
> >mac address...
>
> That could be interesting with such patch. Is there any reason it
> haven't been accepted?
See discussion:
Hello,
On 26 December 2016 10:29:26 GMT+01:00, "Pali Rohár"
wrote:
>On Friday 23 December 2016 10:39:20 Markus Hartung wrote:
>> Is there a way to flush the lease database in dnsmasq? I have tried
>> removing the line in /var/lib/misc/dnsmasq.leases and restart dnsmasq
>>
On Friday 23 December 2016 10:39:20 Markus Hartung wrote:
> Is there a way to flush the lease database in dnsmasq? I have tried
> removing the line in /var/lib/misc/dnsmasq.leases and restart dnsmasq
> but my laptop still gets the same IP-address. Or is it that dnsmasq
> uses the mac-address to
Hey guys.
On 2016-12-22 19:14 wrote:
By default the windows firewall blocks ICMPv4 and ICMPv6 ECHO
requests, not ICMP in general. This causes several issues, so whenever
I setup a Windows machine this is one of the first thing to disable.
Markus' mails were initially saying that he uses
Hi,
> > Windows hosts generally have 2 problems, so assigning a DNS name with
> > IPv6 address using "ra-names" only works under the following
> > circumstances:
> >
> > - The Windows firewall must allow ICMP Echo (PING) requests to go
> > through (IPv6). And here comes the problem: By default
lf Of Pali Rohár
> > Sent: Thursday, December 22, 2016 1:49 PM
> > To: Markus Hartung <m...@hartmark.se>
> > Cc: dnsmasq-discuss@lists.thekelleys.org.uk
> > Subject: Re: [Dnsmasq-discuss] Windows ipv6 hostname
> >
> > On Thursday 22 December 2016 11:24:53 Mark
016 1:49 PM
> To: Markus Hartung <m...@hartmark.se>
> Cc: dnsmasq-discuss@lists.thekelleys.org.uk
> Subject: Re: [Dnsmasq-discuss] Windows ipv6 hostname
>
> On Thursday 22 December 2016 11:24:53 Markus Hartung wrote:
> > On 2016-12-21 14:08, Michael Stilkerich wro
On 2016-12-22 13:48, Pali Rohár wrote:
Windows Vista has (good quality) support for DHCPv6 and IIRC new
versions of Windowses uses same/similar implementation. So I think
Windows 10 should work (no idea if some advanced configuration is
needed)... Also at that time Windows Vista had correct
On Wednesday 21 December 2016 01:26:15 Markus Hartung wrote:
> On 2016-12-20 12:53, Pali Rohár wrote:
> > Another option is to stop using SLAAC and start using DHCPv6 where
> > you have full control of assigned IPv6 addresses.
> >
> > Such feature like host will "randomly" chose address is
On Thursday 22 December 2016 11:24:53 Markus Hartung wrote:
> On 2016-12-21 14:08, Michael Stilkerich wrote:
> > Well, dnsmasq needs to get the hostname to assign to a machine from
> > someplace. I don't know
> > all the possible places (search the manual page for that), but I
> > can
> >
> >
On 2016-12-21 14:08, Michael Stilkerich wrote:
Well, dnsmasq needs to get the hostname to assign to a machine from
someplace. I don't know
all the possible places (search the manual page for that), but I can
think of:
1) Dnsmasq configuration (dhcp-host options)
2) /etc/ethers if enabled
On 2016-12-21 01:26, Markus Hartung wrote:
So I guess the automatic creation of -records doesn't work any
more if I enable privacy extensions.
Your IPv6 host can (and usually does) have several IPv6 addresses at a
time.
Disabling the use of randomized identifiers ensures that one of
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
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
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
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:
> >>
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
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
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 client (which is what
Markus Hartung writes:
> Hello,
>
> Anyone here that is more knowledgeable about IPv6 and Windows 10 hosts?
>
> I have set up my dnsmasq as a authoritative DNS server and have enable ra with
> these options:
>
> enable-ra
>
20 matches
Mail list logo