Hello,

I believe I have found a bug affecting the ER707-M2.

Environment

• ER707-M2 v1.20
• Firmware 1.4.2
• Omada Software Controller 6.2.10.17
• Controller running in Docker using host networking
• Single WAN configuration
• WAN type: DHCP
• No load balancing
• No link backup
• DDNS enabled (issue still occurs with DDNS disabled)

Issue

Whenever the gateway receives a configuration update or is reprovisioned, the ER707 intentionally releases its WAN DHCP lease and obtains a new public IP address.

This causes a brief internet outage and often results in a completely different public IP being assigned by the ISP.

Reproduction Method 1

1. Open Omada Controller.
2. Modify any gateway setting (for example Online Detection Interval).
3. Click Apply.
4. Gateway status changes:
   • Configuring
   • Adopting
   • Connected
5. Approximately 10-30 seconds later the following appears in the gateway logs:

2.5G WAN1: DHCP client releasing IP address succeeded
DHCPS initialization succeeded
2.5G WAN1: DHCP client getting IP succeeded

The WAN IP changes.

Reproduction Method 2

1. Restart Omada Controller.
2. Devices reconnect.
3. Gateway reconnects.
4. Gateway enters:
   • Configuring / Adopting
5. Gateway logs show:

2.5G WAN1: DHCP client releasing IP address succeeded
DHCPS initialization succeeded
2.5G WAN1: DHCP client getting IP succeeded

The WAN IP changes again.

Expected Behaviour

Gateway configuration changes should not force a WAN DHCP RELEASE unless the WAN configuration itself has changed.

Restarting the controller should not cause the WAN interface to be torn down and recreated.

Additional Notes

• DDNS was enabled then disabled during testing and the issue still occurred.
• Only a single WAN is configured.
• The behaviour is reproducible every time.
• The WAN DHCP client is explicitly sending a DHCP RELEASE rather than performing a normal renewal.

Could TP-Link please confirm whether this is expected behaviour or a firmware issue in ER707-M2 firmware 1.4.2?