Bug #2994
Dhcp server doesn't use all range available
Status: | CLOSED | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | nethserver-dnsmasq | |||
Target version: | v6.5 | |||
Security class: | Resolution: | |||
Affected version: | v6.5-final | NEEDINFO: | No |
Description
Configuring a wide dhcp range like this:
[root@HotSpot ~]# db dhcp show eth0=range DhcpRangeEnd=10.100.10.253 DhcpRangeStart=10.100.10.5 status=enabled
Dnsmaqs uses a maximum of 150 IP out of 248
cat /var/lib/dnsmasq/dnsmasq.leases | wc -l
150
This value is a default configuration by dnsmasq, see dhcp-lease-max
.
Might be useful adjust this value according to the range configured, if bigger then 150
Related issues
Associated revisions
dnsmasq.conf: add dhcp-lease-max options. Refs #2994
History
#1 Updated by Alessio Fattorini over 6 years ago
- Description updated (diff)
As workaround I created a template-custom like this
cat /etc/e-smith/templates-custom/etc/dnsmasq.conf/81dhcp-lease-max
dhcp-lease-max=256
And expanded the template with:
signal-event nethserver-dnsmasq-update
#2 Updated by Giacomo Sanchietti over 6 years ago
- Tracker changed from Enhancement to Bug
- Description updated (diff)
- Category set to nethserver-dnsmasq
- Status changed from NEW to TRIAGED
- Target version set to v6.5
- % Done changed from 0 to 20
- Affected version set to v6.5-final
The value of dhcp-lease-max
should be calculated from DhcpRangeEnd
and DhcpRangeStart
properties.
#3 Updated by Giacomo Sanchietti over 6 years ago
- Description updated (diff)
#4 Updated by Giacomo Sanchietti over 6 years ago
- Description updated (diff)
#5 Updated by Giacomo Sanchietti over 6 years ago
- Description updated (diff)
#6 Updated by Giacomo Sanchietti over 6 years ago
- Status changed from TRIAGED to ON_DEV
- % Done changed from 20 to 30
#7 Updated by Giacomo Sanchietti over 6 years ago
- Assignee set to Giacomo Sanchietti
#8 Updated by Giacomo Sanchietti over 6 years ago
- Status changed from ON_DEV to MODIFIED
- % Done changed from 30 to 60
#9 Updated by Giacomo Sanchietti over 6 years ago
- Status changed from MODIFIED to ON_QA
- Assignee deleted (
Giacomo Sanchietti) - % Done changed from 60 to 70
Package in nethserver-testing:
- nethserver-dnsmasq-1.4.1-1.1gitea732a1.ns6.noarch.rpm
- Check the bug is not reproducible
#10 Updated by Alessio Fattorini over 6 years ago
- Assignee set to Alessio Fattorini
#11 Updated by Alessio Fattorini over 6 years ago
- db dhcp show
eth0=range
DhcpRangeEnd=192.168.5.254
DhcpRangeStart=192.168.5.1
status=enabled
- cat /etc/dnsmasq.conf | grep lease-max
dhcp-lease-max=253
VERIFIED
#12 Updated by Giacomo Sanchietti over 6 years ago
- Status changed from ON_QA to VERIFIED
- Assignee deleted (
Alessio Fattorini) - % Done changed from 70 to 90
#13 Updated by Giacomo Sanchietti over 6 years ago
- Status changed from VERIFIED to CLOSED
- % Done changed from 90 to 100
Released in nethserver-updates:
- nethserver-dnsmasq-1.4.2-1.ns6.noarch.rpm
#14 Updated by Giacomo Sanchietti over 6 years ago
- Related to Bug #3014: Dnsmasq doesn't start: illegal repeated keyword at line 82 of /etc/dnsmasq.conf added