Modify

Opened 5 years ago

#13687 new defect

dnsmasq: hex network name breaks dhcp-range configuration

Reported by: killerbees19 <openwrt-dev@…> Owned by: developers
Priority: normal Milestone: Attitude Adjustment 12.09.1
Component: packages Version: Attitude Adjustment 12.09
Keywords: Cc:

Description

A hex network name like "ce" or "a0" (created with LuCI) doesn't support DHCP. That's because the network name is the first part for dhcp-range setting in dnsmasq.conf and interpreted as IPv6 address. And because it's a wrong syntax or it doesn't match any local network address, dnsmasq ignores it silently. Example line: dhcp-range=ce,10.0.0.100,10.0.0.249,255.255.255.0,12h

After restarting dnsmasq you'll see the following line for each DHCP IP address range. This part is missing for our hex names network: daemon.info dnsmasq-dhcp[*]: DHCP, IP range 10.0.0.100 -- 10.0.0.249, lease time 12h

As a result the next DHCP request in that network generates this warning: daemon.warn dnsmasq-dhcp[*]: no address range available for DHCP request via br-ce

The current workaround is a new network name with at least one other character than [0-9A-F]. But that isn't a solution. There must be a way to escape such network names for dnsmasq.conf or a global non-hex prefix like "openwrt-", final result: openwrt-ce (that should fix it too!)

I think that could be fixed somewhere in /etc/init.d/dnsmasq where our temporary dnsmasq.conf file is generated on-the-fly.

Attachments (2)

dhcp.config (131 bytes) - added by killerbees19 <openwrt-dev@…> 5 years ago.
network.config (165 bytes) - added by killerbees19 <openwrt-dev@…> 5 years ago.

Download all attachments as: .zip

Change History (2)

Changed 5 years ago by killerbees19 <openwrt-dev@…>

Changed 5 years ago by killerbees19 <openwrt-dev@…>

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.