ISP Modem restart ends up with connection issue

ISP Modem restart ends up with connection issue

ISP Modem restart ends up with connection issue
ISP Modem restart ends up with connection issue
Friday
Model: ER706W  
Hardware Version: V1
Firmware Version: 1.2.2 Build 20250821

Hello,
I’m experiencing a recurring connectivity issue that occurs approximately once per month when my ISP modems receive new IP addresses.
Setup Description:
I’m operating two different configurations:
    1.    Setup A: Gateway behind modem → WireGuard tunnel → Controller
    2.    Setup B: Gateway behind modem → Direct connection to externally reachable remote controller (also uses WireGuard)
Problem Description:
After either modem obtains a new IP address (typically during ISP-initiated reboot), the following connections fail to re-establish automatically:
    ∙    WireGuard tunnel connections (both setups)
    ∙    Remote controller connection (Setup B)
Current Behavior:
    1.    ISP modem receives new IP address
    2.    Gateway detects the IP change correctly
    3.    However, existing connection states are not reset
    4.    Setup A: WireGuard tunnel to controller remains down
    5.    Setup B: Both WireGuard tunnel AND remote controller connection remain unreachable
    6.    Rebooting the gateway does NOT resolve the issue
Root Cause Analysis:
The gateways appear to recognize the IP address change, but connection states are not being properly cleared. This causes stale NAT/connection tracking entries that prevent re-establishment of:
    ∙    WireGuard tunnels (both configurations)
    ∙    Remote controller connections
Proposed Solutions:
I believe this could be resolved by implementing automatic state reset on IP change detection:
    1.    WireGuard: Force source port randomization when upstream IP change is detected
    2.    Controller connection: Reinitialize connection with new source port
    3.    Gateway: Clear all NAT/connection tracking states upon detecting modem IP changes
Questions:
    1.    Is there currently a workaround available for this issue?
    2.    Can this be escalated to the development team for a permanent fix?
    3.    Would implementing source port randomization on the gateway side potentially resolve this without firmware changes?
Since the gateway already detects the IP change, it should theoretically be able to trigger a connection state reset automatically.
Thank you for your assistance!

  0      
  0      
#1
Options
1 Reply
Re:ISP Modem restart ends up with connection issue
Yesterday

Hi  @olli_foxtech 

Thank you so much for taking the time to post the issue on the TP-Link community!

 

To better assist you, I've created a support ticket via your registered email address and escalated it to our support engineer to look into the issue. The ticket ID is TKID260151156 please check your email box and ensure the support email is well received. Thanks!

 

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

 

Many thanks for your great cooperation and patience!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options