Caveats for changing interface netmask?

Reply
Highlighted
L1 Bithead

Caveats for changing interface netmask?

I've got a client that wants to expand the network range on one of their interfaces for additional DHCP scope space, moving from a /24 to a /23.  I wanted to check if there are any caveats to this on the PAN side?  Will the update take effect as soon as the change is commited?

I'm currently scoping out the rest of the network to confirm if anything else needs to be updated as well for this to route/flow properly, but I wanted to confirm on this side, and I wasn't seeing much in the documentation on this.

Highlighted
Cyber Elite

Re: Caveats for changing interface netmask?

@John-Palmer,

This depends largely on how the firewall is actually configured and how the rest of the network is actually setup. For example, it matters quite a bit if the firewall interface in question is Layer2 or Layer3, and if the firewall is participating in the DHCP/DHCP-Relay configuration for the clients at all. 

Highlighted
L4 Transporter

Re: Caveats for changing interface netmask?

Could you please more details on where is client subnet which needs to be expected is located in network ?

 

SD-WAN | Cloud Networking | PCNSE | ICSI CNSS | MCNA | | CCNP | CCSA | SPSP | SPSX | F5-101 | CCIE-SEC-Attempted
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!