@Sheep_Dog , IP v4 exhaustion is definitely a concern at the global level and NAT is a critical part of addressing it. From the WAN side, the details of the LAN are unknown. Range, number of...

@Clive_A , By the way, I suspect none of these limits are documented (designed for 60-80, hard fail at ~250). I also suspect the failure didn't generate any logs. Wouldn't it be nice if end customers...

@FPAddict , Per Controller documentation: MSP (Managed Service Provider) mode allows you to know the status of your customers at a glance, and manage customers in the Omada platform. As I understand...

@FPAddict , You and me both... See: Logging & Monitoring of ACL rules - Business Community (tp-link.com) Some of the attack/defense built-in rules generate log entries. All of but one kind as...

@Sheep_Dog , Isn't the main point of NAT to reduce IP exhaustion and hide the details of the LAN? And yet you use mappings to give each LAN client an IP on the WAN side? As is, that's 3 layers of NAT...

@FPAddict , Believe it or not, it's currently not possible for us mere end customers. I've been told it's available in MSP mode (network managed by 3rd party) and that TP-Link is looking at expanding...