@RF_Dude 

Starlink IP addresses are leased for 5 minutes at a time. However that doesn't mean your IP will change every 5 minutes. Starlink will try to maintain your IP for as long as the device is connected and has a public IP

You would expect a router to attempt to renew the IP once 50% of the lease time has expired, which is exactly what its doing.

I also see this in my logs after the last firmware update to ER7206, I'm not bothered about the short lease time but would be useful to disable the logging for this event as its filling the logs up, I cant see a config option for this event in logging.

  @RF_Dude I am seeing exact same behavior. I have Starlink on WAN port of ER605 Router v2.0 2.1.2 (Build 20230210 Rel.62992). Turning off WAN online detection makes no difference. 

1    2024-01-05 14:29:39    DHCP Client    NOTICE    WAN: DHCP client renewing IP succeeded. (IP-Address=100.80.107.???, Mask=255.192.0.0, Gateway=100.64.0.1)
2    2024-01-05 14:29:35    DHCP Client    NOTICE    WAN: DHCP client lease expired. Began renewing the lease.
3    2024-01-05 14:27:18    DHCP Server    NOTICE    DHCP Server allocated IP address 192.168.0.130 for the client[MAC: 12:65:06:1f:86:55].
4    2024-01-05 14:27:08    DHCP Client    NOTICE    WAN: DHCP client renewing IP succeeded. (IP-Address=100.80.107.???, Mask=255.192.0.0, Gateway=100.64.0.1)

  @RF_Dude 

see this thread https://community.tp-link.com/en/business/forum/topic/648928 for how to disable the logs

  @RF_Dude sorted, why coudln't I find that !, been through those log settings several times. Filling the log with that every 10 minutes means something useful will be missed.

Clive_A wrote

 So our test team is interested in this issue. Can you guys use Wireshark and mirror the WAN port and monitor the DHCP lease time from Starlink?

 

How to capture packets using Wireshark on SMB router or switch

How to Use Port Mirror to Capture Packets in the Controller

  @Clive_A 

I'm not quite sure what use Wireshark logs would be. There's ample evidence out there ( I cant post links since this forum doesnt allow external links!) that Starlink use a 5 min DHCP lease time ( just google 'starlink dhcp lease time' its the first hit ). It's normal ( and quite correct ) for a DHCP client to request a lease renewal once 50% of the lease time expires. The only issue is that the DHCP renewal is logged by default by the router.

If your test team wish to investigate further, then just set up a local DHCP server with a 5 min lease time!!

  @Clive_A I will look into this on the weekend and if successful, both with the WireShark capture, and learning how to filter all the other stuff it captures, can send this to you directly next week.  I hope others with this sniffing ability can attempt this and provide you the result.  I guess this to confirm that the TP-LINK router is initiating the lease renewal at 2.5 minutes, rather than SL at 5 minutes and nothing unusual is going on... like loosing or confusing client traffic in this process.    

I have other issues in the WDS (10 APs) that may or may not be related to the above (clients randomly but eventually locking down to dial up speeds until their connection is reset) and 1 other issue that will require some intensive Wireshark investigation.  We learn as we go and traverse these troubleshooting hurdles.