| Summary: | BOOTP breaks the list of DHCP leases due to erroneous parsing | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | Man Grove <mw+ipfire> |
| Component: | --- | Assignee: | Michael Tremer <michael.tremer> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Aesthetic Issue | ||
| Priority: | - Unknown - | CC: | adolf.belka, michael.tremer |
| Version: | 2 | ||
| Hardware: | all | ||
| OS: | All | ||
Could you please test and verify that this patch fixes the problem?
> https://patchwork.ipfire.org/project/ipfire/patch/20240515132003.1788345-1-michael.tremer@ipfire.org/
(In reply to Michael Tremer from comment #1) > Could you please test and verify that this patch fixes the problem? > > https://patchwork.ipfire.org/project/ipfire/patch/20240515132003.1788345-1- > michael.tremer@ipfire.org/ Tested and verified fixed. Great! Thank you! Patch has been merged into Cu186 Testing (master) https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=6515a2780201e9209e370cd4562bef5cb771f1a5 Core Update 186 has been released https://www.ipfire.org/blog/ipfire-2-29-core-update-186-released |
When activating BOOTP and actually having such a device on the network the dynamic list disappears completely in the GUI when an IP is fetched. This is due to malfunctioning parsing, somewhere, of the /var/state/dhcp/dhcpd.leases file. A BOOTP client will generate a section like this (BOOTP has no end time): lease 192.168.0.1 { starts 2 2024/05/14 22:32:51; ends never; cltt 2 2024/05/14 22:32:51; binding state active; next binding state free; rewind binding state free; dynamic-bootp; hardware ethernet de:ad:be:ef:ac:dc; } The line "ends never;" breaks the parsing of the list. Changing that line manually to, for example, "ends 3 2024/06/15 02:14:02;" fixes it again. Related forum threads: https://community.ipfire.org/t/list-gets-borked-when-a-bootp-client-gets-its-ip/11607 https://community.ipfire.org/t/dhcp-dynamic-clients-not-showing-as-expected/8910 And, amusingly, https://redmine.pfsense.org/issues/3945?tab=history ;-)