@world
i recently swapped hardware installed from scratch and imported my backup.
unfortunately this still happens. so far i thought it was my very old installation
causing this behaviour. but now?
is this ‘fixed’
also: DHCP hosts not reliably propagated to DNS - #61 by pavlos
jon
(Jon)
29 August 2022 14:27
2
This was fixed in CU 167 and the current stable release is CU 169.
Please see:
Can you add more details of the issues?
3 Likes
unfortunately it is not solved and i am not the only one
experiencing this error. to be honest only by chance i
have found the topic DHCP hosts not reliably propagated to DNS - #62 by current_user
and thought it is ‘normal’.
right now, seconds ago i got the error again!
however i posted the info in the original topic
gauthig
(Garrett Gauthier)
29 November 2022 19:26
4
Hi I have a new install and unbound-dhcp-leases-bridge does not get started at boot.
Running /etc/init.d/dhcp restart shows this:
Stopping DHCP Server… [ OK ]
Stopping Unbound DHCP Leases Bridge… Not running. [ WARN ]
Starting DHCP Server… [ OK ]
Only way to get leases into unbound is to manually run unbound-dhcp-leases-bridge
Any ideals?
IPFire 2.27 (x86_64) - core171
hvacguy
(Shaun HVAC)
29 November 2022 19:51
5
Welcome.
Perhaps a similar case as yours?
I’ve already resolved the issue, but just in case someone else runs into this.
I did a full backup to ISO and installed it on a new device (to replace my existing IPFire device). When I finished configuring the new interfaces (only RED and GREEN on both) to match the new adapters after a reboot the DHCP server was not starting.
What was missing was the symbolic link in the rc3.d directory:
# ls -l /etc/rc.d/rc3.d/S30dhcp
lrwxrwxrwx 1 root root 14 Feb 15 22:40 /etc/rc.d/rc3.d/S30dhcp ->…
hello world
silly me did an update from 171 to 173
three days ago and now, again i cant ping some dhcp clients
the clients in question are rebooted several times since the ipfire boot.
what to post to help the coding-ppl
EDiTH:
i already found out that dhcp-leases.conf is empty