Help: Change Current WAN with new ISP Public IP

[pon]

Hello. I am relatively new to OPNsense. An ISP has acquired our current ISP and need to change public IP information. I have tried to configure the current WAN but get the message that the IP doesn't meet the current range with editing a new Gateway (as its already set for the current range). We have two WAN interfaces for primary and secondary connections. This is being done in the GUI.

What is the best practice to get the current WAN used changed to new IP? Will deleting the WAN interface to configure a new one with new IP and Gateway allow to set the new IP range (as I am not able to edit that range in place)? sorry if this is obvious as I am not wanting to make a config unless I know the outcome and limit any disturbance.

thank you

[pon]

I guess I just need to know if I either am able to edit that current WAN and edit the DHCP Leases for that new IP/gateway range I need to change to or deleting that WAN interface completely and configuring a new one allows me to configure the range of that new IP and gateway. I have been looking around and can't seem to find a definite answer for changing current WAN interface vs setting up a new one on installation in regards to ISP changes.

[Demusman]

Is the new ISP using DHCP?
If so, you don't have to change anything. Just release and renew IP.

If they give you a static IP, you'll need to set it manually.

If PPPOE, you'll have to set it manually.

Which is it?

[pon]

Its Static so I am trying to change the old IP thats set with provided gateway. I put in the correct IP and set the new Gateway But I get that error for

"gateway address does not lie within one of the chosen interface's IPv4"

Does resetting that WAN and creating a new one reset IPv4 for me to set the range for that new IP? or can I edit that range under "Services" first before I edit the WAN Interface I need changed?

[Demusman]

Just set the current WAN to static, then set the address right there.
Don't delete the interface.

[HamiltonWDS]

When changing the WAN Static IP, for the Gateway, have you tried with creating a new Gateway from within the WAN Interface?
That is, at the WAN Interface Config page, scroll down to IPv4 Upstream Gateway (I assume IPv4), and click the Plus sign (+).
- Select Default Gateway (checked)
- Provide a unique name (ex: WAN_GW_New)
- Gateway IPv4, set to the ISP's Gateway IP

This may work rather than creating a Gateway in the Gateways Menu (within System).

[pon]

That was the 2nd attempt after trying to create the Gateway separately when getting that error and got the similar message. I will be attempting to change it today again and will see if there was a step I missed changing the Gateway within the WAN interface to avoid that error. For me I would assume if changing IP/Gateway would then have a new range to be set with that process but under the Services it still would show the current IP range with no way to change it (not sure if that matters but thought it was odd). Thats where I was thinking if deleting that WAN interface and creating a new one within the Wizard would allow me to set the IP range with the new Public IP and Gateway. I will provide screenshots later. Thanks for the replies as this is really helping work through it.

[pon]

So I was finally successful on changing IP and Gateway for new ISP. After doing alot of digging with the "gateway address  does not lie within one of the chosen interface's IPv4 subnets.", it appears you have to select "Far Gateway" first for it to work and then take it off later (some were saying its a bug. I am on 21.1.3_3) This allowed to save the WAN interface IP along with saving new Gateway information. This in return updated the WAN DHCPIPv4 section under Services with proper Subnet, Mask and Range.

I then had to go into the failover settings to then assign the new WAN to a Tier for the failover policy for our 2 connections as it will take it off since the old WAN interface no longer in use. (If anyone has this setup for Failover)

thanks for the help

[HamiltonWDS]

Ah, glad you got it working.
I would recommend though to update to the latest version, unless there are legacy reasons not to of course.