[FS#1290] Additional dhcp-range not created in dnsmasq.conf
LEDE Bugs
lede-bugs at lists.infradead.org
Tue Jan 23 05:30:16 PST 2018
A new Flyspray task has been opened. Details are below.
User who did this - Kurgan- (Kurgan-)
Attached to Project - OpenWrt/LEDE Project
Summary - Additional dhcp-range not created in dnsmasq.conf
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - I have created 3 interfaces I want to run a DHCP server on.
The first is the default LAN, then there are 2 more: "camera" and "management".
In /etc/config/dhcp.conf I have the interfaces defined properly (I suppose):
config dhcp 'lan'
option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
config dhcp 'management'
option start '100'
option leasetime '12h'
option limit '150'
option interface 'management'
config dhcp 'camere'
option interface 'camere'
option start '100'
option leasetime '12h'
option limit '150'
list dhcp_option '6,192.168.42.1'
Anyway, when I look at the generated dnsmasq.conf file (/var/etc/dnsmasq.conf.cfg02411c), I can see only ONE dhcp-range definition, for LAN interface. There is NO OTHER dhcp-range entry.
dhcp-range=lan,192.168.0.100,192.168.0.249,255.255.255.0,12h
So, dnsmasq does not serve dhcp to the other two interfaces.
If I manually add ranges to /etc/dnsmasq.conf, then DHCP works on the other interfaces too.
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=1290
More information about the lede-bugs
mailing list