packages/net/isc-dhcp/files, branch masterMirror of packages feedhttps://git-03.infra.openwrt.org/feed/packages/atom?h=master2026-02-11T18:02:24Zisc-dhcp: don't die when a network restart happens2026-02-11T18:02:24ZPhilip Prindeville2026-01-08T00:42:39Zurn:sha1:6a9f2bcda761a2da3f140f106a2ea817ee770e68
Our triggering code was using the logical network name and
not the ifname as required.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: replacing automatic empty needs addzone2026-02-03T03:48:47ZPhilip Prindeville2026-02-02T20:17:10Zurn:sha1:f171043ce8a433afaaa456afc4a6db965b321f03
Since the RFC-1918 in-addr.arpa empty zones are automatically created,
they will exist, but we can't use modzone on them because that's not
how things work.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: fix startup issues with RFC-1918 PTR RRs2025-12-13T19:26:38ZPhilip Prindeville2025-12-10T22:03:41Zurn:sha1:a050b08db2edf2290d28a3834065cf6c4aa127dd
If isc-dhcp gets restarted, it might have to deal with RFC-1918 zones
being previously populated by an earlier instance. In that case, we
need to know if we're modified versus initially adding the zones.
The special handling of RFC-1918 zones in Bind is quirky, and there
should be a patch soon to make it more friendly, but in the meantime
you might have to use:
disable-empty-zone 168.192.in-addr.arpa;
Or similar depending on which address block you poach.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: use modzone not addzone so in-addr.arpa works2025-12-02T17:03:24ZPhilip Prindeville2025-12-01T23:09:26Zurn:sha1:27f55cdbda2259bcd8ab3f0b7c56aca12931689f
Updates to in-addr.arpa are being rejected with:
update failed: REFUSED
because we create an empty zone, and then try to add it again
when it already exists. So use modzone instead to update it.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: Missing trailing dot on SRV RRs2025-11-15T07:02:02ZPhilip Prindeville2025-11-15T02:27:51Zurn:sha1:13ea3654c3343361157e87d4128b555c58dff4c4
When generating SRV RRs we're omitting the trailing dot that
roots the domain.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: create zones using rndc2025-09-13T20:36:41ZDavid Härdeman2025-08-03T20:10:53Zurn:sha1:dc68b6679767ac80b182389bf73ce81066645446
This changes isc-dhcp's init script to create bind zones using the tools
bind provides for that scenario instead of crafting separate zone
configuration by hand.
At the same time, remove the use of /tmp/bind/named.conf.local and add
permissions for dynamic zone creation to bind.
Signed-off-by: David Härdeman <david@hardeman.nu>
isc-dhcpd: quote filenames for safety2025-08-15T03:43:00ZPhilip Prindeville2025-08-09T03:48:06Zurn:sha1:ae8a2d515df8f3638d03b3dbf7f412bca3f17c3f
Per best practices, we should protect against wildcards in
variable expansions.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: fix spacing on forced parameters2025-08-15T03:43:00ZPhilip Prindeville2025-08-04T01:40:44Zurn:sha1:824a344a4a17f913c9722b5204a31ee2eef1df32
If there's a "forced_send" option, then put spaces between multiple
parameter codes.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: distinguish between hexstrings and strings2025-08-15T03:43:00ZPhilip Prindeville2025-06-07T20:38:26Zurn:sha1:a97218b6c77e4caf27c0013a84318ed79e29b68d
It's a minor difference and they're handled the same, but that
might change as we move to Kea.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
isc-dhcp: clean up 'if' formatting2025-08-15T03:43:00ZPhilip Prindeville2025-08-11T23:59:00Zurn:sha1:3d2a8e3f8cd8a329158d5d61d00438c84c1cce28
We don't use a consistent format of bracket-semicolon, so fix it.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>