On Tue, May 23, 2023 at 12:05:08AM +0100, Simon Kelley wrote: > On 22/05/2023 12:18, Linyih Teng wrote: > > In the manual page is written: > > > -X, --dhcp-lease-max=<number> > > > Limits dnsmasq to the specified maximum number of DHCP > > > leases. The default is 1000. This limit is to prevent DoS > > > attacks from hosts which create thousands of leases and use > > > lots of memory in the dnsmasq process. > > > > Hello, > > > > I'm using dnsmasq2.89 and testing the maximum lease count of the DHCPv6 > > server with the *dhcp-lease-max* option. > > > > For the testing, I'm using below configuration: > > > > *dhcp-lease-max* = 512 > > *dhcp-range*=tag:pool0,2022::1,2022::1f:ffff:ffff:fffe,64,120m > > tag-if=set:pool0,tag:intfv0 > > > > > > However, when the number of clients reaches the maximum number, the > > server still provides IPs to clients. Is this the expected behavior of > > DHCPv6? > > > There's a possible difference between the number of clients and the number > of DHCP leases, since leases can expire to be deleted by the client. > > Are you saying that the number of simultaneous DHCP leases increases without > bound, or that the 513th client gets a lease? Have you checked the number of > leases in the dnsmasq.leases file?
Original Poster has yet to say what the expected behaviour should be. Thing I am saying: Why limit dhcp-range by dhcp-lease-max? Regards Geert Stappers -- Silence is hard to parse _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
