I upgraded to 9.105 (from 9.006) over a day ago, and everything was fine until I tried to move an existing (from 9.0x) definition/static mapping to a different DHCP server (different VLAN / DMZ).
Editing the definition seemed OK, but when I restarted the interface on the client, there was no response from the dhcp server.
Soon after that, I noticed my AP30 was offline.
I power-cycled the AP and rebooted the UTM and still had no luck.
Then, I started seeing emails about "Dhcpd not running - restarted" and I knew something was wrong with the static mapping / definition.
I disabled the 2 DHCP servers for the DMZs that the definition was in before, and is in now. After that, the AP30 came back online.
Then, I tried turning on one of the DHCP servers again. A popup appeared saying "IP 192.168.210.9 is not in network 192.168.211.0/24 of the chosen interface".
I checked the definition/static mapping again. It was wrong, so I fixed it.
Then, I could restart one DHCP server but not the other; a similar popup message appeared.
I tried switching the definition back to the other dhcp server and the old IP address. Again, one dhcp server would not start.
I tried to delete the definition, and got the following message in a popup:
Network Services → DHCP → Servers:
The host object 'prestaDEV.X.net' is still used by the DHCPv4 server object '192.168.211.240 on Untrusted'. Proceed with object deletion anyway?
Network Services → DHCP → Servers:
The host object 'prestaDEV.X.net' is still used by the DHCPv4 server object '192.168.210.241 on DMZ'. Proceed with object deletion anyway?
I went ahead and deleted the definition, restarted the dhcp servers (no errors!), and re-created the static mapping, and it's working now.
This was a real pain, and I'm worried that I will have more problems as I have lots more static mappings/definitions from 9.0x and I don't know if I can trust them.
Any advice?
Thanks,
Barry
This thread was automatically locked due to age.
