This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UID lease xxx.xxx.xxx.xxx for client xx:xxx:xx:xx:xx:xx is duplicate on 192.168.1.0/24

Hello,

Today, something strange happens with the DHCP of my SOPHOS UTM.

All my clients do not receive anymore their ip address from the DHCP. They have all a static mapping configured.

These static mappings are ofcourse all defined outside the range of the dhcp allocation = 1->99).

 

2017:12:30-19:46:38 wolfgatefw dhcpd: uid lease 192.168.1.25 for client f0:24:75:f3:fd:3d is duplicate on 192.168.1.0/24
2017:12:30-19:46:38 wolfgatefw dhcpd: DHCPDISCOVER from f0:24:75:f3:fd:3d via eth1
2017:12:30-19:46:38 wolfgatefw dhcpd: DHCPOFFER on 192.168.1.109 to f0:24:75:f3:fd:3d via eth1
 
My firmware version is 9.506-2.
 
[Update 31/12]
My problems seemed to have appeared after I've applied the last firmware updates (I have applied two updates at once till the v9.506-2). 
 
I've cleared my file /var/chroot-dhcps/var/state/dhcp/dhcpd.leases and I've restared the dhcpd server. The problem is still there. The static mapping does not work anymore and the DHCP tries to offer an ip address in the DHCP range (does not work neither). 
 
I've isolated the UTM and I connect now with only one device for my tests. In the DHCP Log i can see now looping the two following lines.
The device LAPTOP01 never gets its IP address from the DHCP.

2017:12:31-13:57:10 wolfgatefw dhcpd: DHCPDISCOVER from 3c:97:0e:de:ac:51 (LAPTOP01) via eth1
2017:12:31-13:57:10 wolfgatefw dhcpd: DHCPOFFER on 192.168.1.32 to 3c:97:0e:de:ac:51 (LAPTOP01) via eth1
2017:12:31-13:57:26 wolfgatefw dhcpd: DHCPDISCOVER from 3c:97:0e:de:ac:51 (LAPTOP01) via eth1
2017:12:31-13:57:26 wolfgatefw dhcpd: DHCPOFFER on 192.168.1.32 to 3c:97:0e:de:ac:51 (LAPTOP01) via eth1
...
 
If i give myself the ip and all the network configuration on the device, then I can connect on the internet.
 
Maybe someone can help me please?
 
Thank you!
 
Fred


This thread was automatically locked due to age.
  • I could solve my problem.

    I did exactly the same mistake that the user les_garten did. We obviously both use a NETGEAR manageable switch and we decided to click and set to ON the "Admin mode" in the DHCP filtering menu! I did that the same day when i decided to update my UTM firmware. I have to admit that those updates were not in relation with my problem.

    les_garten reply of 8 juin 2014 3:17
    community.sophos.com/.../dhcp-not-working