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

dhcp static mapping not working

version 9.353-4  on a sophos 220

we have dhcp scopes set  with the tick box   "Clients with static mappings only"

we have hosts defined in definitions and userss >network defintions 

the dhcp is giving out the ip addresses reserved for static hosts

so 2 problems

1. the rule static mappings only is not working

2. it is ignoring the static mappings also



This thread was automatically locked due to age.
  • Here's another one. Host is assigned 1.101 in the the static only pool range and somehow grabbed 1.159

     

    2019:09:28-09:57:55 gw2 dhcpd: Dynamic and static leases present for 192.168.1.101.
    2019:09:28-09:57:55 gw2 dhcpd: Remove host declaration REF_NetHosPiwcwks101 or remove 192.168.1.101
    2019:09:28-09:57:55 gw2 dhcpd: from the dynamic address pool for REF_DefaultInternal
    2019:09:28-09:57:55 gw2 dhcpd: uid lease 192.168.1.159 for client 34:97:f6:36:26:24 is duplicate on REF_DefaultInternal
    2019:09:28-09:57:55 gw2 dhcpd: DHCPREQUEST for 192.168.1.101 from 34:97:f6:36:26:24 via eth0
    2019:09:28-09:57:55 gw2 dhcpd: DHCPACK on 192.168.1.101 to 34:97:f6:36:26:24 via eth0

     

    Again 1.101 is not in the dynamic pool range

    ranges on int. Internal:

    50-198 set to static mappings only

    200-249 dynamic

     

    Why did 34:97:f6:36:26:24 have 1.159?

  • 2019:09:28-09:57:55 gw2 dhcpd: Dynamic and static leases present for 192.168.1.101.

    Some other device still has .1.101 leased.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA