Static entry bug?

Question

You have a static entry configured in the DHCP scope of subnet A. You move the client to subnet B, and make it static from the 'DHCP leases' tab using the 'use an existing host' option. The outcome is that the host record now contains the IP from subnet B, but when the DHCP OFFER is sent to the client, the IP address is correct, but the default gateway is from the network configured on the original static entry, subnet A. As such, the client has a DG it can't reach. The behaviour is consistent. 
 if you create a new host for management via DHCP, you can't save it if the address is not in the chosen DHCP range - you get (e.g.) "IP 192.168.1.150 is not in network 192.168.2.0/24 of the chosen interface." 
 is this intended behaviour or a bug?

FormerMember · Accepted Answer

Hi dirkkotte 
 Thank you for reporting this, but it is not a bug but an expected behavior. If the existing host is in network 192.168.1.0/24 and interface eth0, when you try to add new IP which is not part of that network and interface, UTM will present you the error message to correct the interface/DHCP server. 
 The interface/DHCP server and IP address of the static host should be in the same network. 
 To avoid an IP address clash between regularly assigned addresses from the DHCP pool and those statically mapped make sure that the latter are not in the scope of the DHCP pool. For example, a static mapping of 192.168.0.200 could result in two systems receiving the same IP address if the DHCP pool is 192.168.0.100 &ndash; 192.168.0.210. 
 Thanks,

dirkkotte · Answer

Yes, That's a bug within the GUI. 
 If you try to add the new IP/MAC to existing host, the IP for this host is changed, but not the DHCP Server/Scope/Subnet. 
 If you open the network object afterwards, you are unable to save until you correct this error.

dirkkotte · Answer

Hi H_Patel , 
 the problem is, the GUI don't correct me ... 
 First ... you have a host-definition with dhcp settings from yesterday. yesterday the host is connected to Subnet A. DHCP settings (IP&DHCP-Scope) are from Subnet A. 
 Today you connect host to subnet B. Host receive correct IP & Subnet data for Subnet/scope B. 
 If you now show the list of dynamically assigned IP-adresses and select "make static" the host (currently using dynamic assigned address from subnet B) is assigned a IP from subnet B but keeps the dhcp server/scope from IP assigned before (subnet A). .... there is no option to change this at this point. 
 So the next DHCP answer send IP from sunbet B and gateway from subnet A. 
 if you open the host definition you have to correct IP and DHCP-Scope before you are able to save.