@Clive_A You are missing the point. Based on your reply, I am sure you barely understand your company and product goals. Otherwise your reply would be more in line with providing good customer...

@aerubik The problem here is not a new feature. The real issue is that TP-Link does not want to solve a bug in their firmware. I implemented a kill switch can through routing policies and firewall...

Hi @pablosaad, I agree with you. This is a security bug that the TP-Link dev team should take seriously. The routing and firewall rules should work immediately when the VPN connection is down instead...

As mentioned in this thread, I am testing different solutions to choose the one that provides the best security, reliability, and lowest cost. @Clive_A, I assume that since you work for TP-link you...

@Clive_A Cisco also has support for a kill switch in some models and if it is not available it is possible to use routing policies and firewall rules to accomplish the same result without any leaks....

I found a solution using routing rules with "only option" and firewall rules to block any access to my local ISP when the VPN is disabled or the remote ER605 modem is down. That solution partially...