Need to change bootp config to dhcp_request when upgradig SmartCenter to R80.x

peter_schumache — Fri, 17 May 2019 08:53:47 GMT

The pre_upgrade_verifier of R80.x gives a warning, that we use the service "bootp" in our existing R77.30 policies, and that we should replace it with the new dhcp_xxx services.

Our gateways DO NOT ACT as DHCP Relays, they just forward unicast bootp requests, which were relayed on routers behind the firewall.

Is it therefore correct that we can just replace all instances of the "bootp" service with "dhcp_request"

Re: Need to change bootp config to dhcp_request when upgradig SmartCenter to R80.x

Wolfgang — Fri, 17 May 2019 11:19:36 GMT

Peter,

using the new DHCP services is not mandatory.

Using the bootp like you does, there is no need to change to the new dhcp services.

Configuration of IPv4 BOOTP/DHCP Relay using new services describes really good the new DHCp services and there need or not.

For youre use case, snip from the document:

"For backwards compatibility, the legacy DHCP (BOOTP/DHCP) services can still be used with newer Security Gateways and Security Management Servers."

The new DHCP services allows an improved configuration of the rules for DHCP relay.

Wolfgang

topic Need to change bootp config to dhcp_request when upgradig SmartCenter to R80.x in Firewall and Security Management

Need to change bootp config to dhcp_request when upgradig SmartCenter to R80.x

Re: Need to change bootp config to dhcp_request when upgradig SmartCenter to R80.x