On Wed, Apr 19, 2023 at 12:55 PM Petr Menšík <pemen...@redhat.com> wrote:
> Are you aware that 80 on the end of dhcp-range is lease time, not any
> prefix size? Consider using of constructor:tapvm4qyj3a instead of manual
> end address. If I see correctly the end address is the same as the start
> address. Not sure how this should behave, but I would not be surprised
> if it did not work.
>
Hmm, my read of the manual page suggests it should be the prefix length?
-F,
--dhcp-range=[tag:<tag>[,tag:<tag>],][set:<tag>,]<start-
IPv6addr>[,<end-IPv6addr>|constructor:<interface>][,<mode>][,<prefix-
len>][,<lease time>]
As far as I can tell, it worked as expected, though I was experimenting
with a few things so I am not sure at this time.
I thought about using the constructor feature, but I was trying to figure
out if there was some way to get dnsmasq to respond to the DHCP query
without occupying space in the /64 I'd like the VM to use (e.g. by
listening and responding to DHCP via link local addresses. In such a case
the address range would have to be telegraphed rather than read from the
interface. As seen in my example, one address suffices for the one VM that
is free to bind anything in the /80.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
