@sugar0 

Oh man, they fu@€)ing did it after 2 years!! 🤣 update to 1.4.1 OTA ( the update sais installation is wrong but update is OK) and the option find in client vpn ->  edit -> activate kill switch! congratulations TPLink

  @Rhaziel what router do you have ? i dont even find my actual fw in the support page, not even my actial one in the photo aboce. they stopped updating new fw?

I would also like to know if this feature will be added on BE550 or I will have to return it back.

@aerubik

I've searched thoroughly, but I still can't find this feature. This thread is about the TP-Link ER605 router, and after installing the latest firmware updates on both of my units, the kill switch is nowhere to be found. It seems TP-Link may have reserved this functionality for their AX series—possibly to compete more directly with ASUS and CUDY's AX offerings.

As discussed earlier in this thread, a kill switch is a valuable feature, but its behavior can be emulated using routing policies. The real issue is that these policies don't activate immediately. Before the firmware update, the routing rules would disable internet access within 15–20 seconds of a VPN failure. After today's update, I tested the same scenario—VPN server down—and the delay is even worse. My local IP remains exposed for 30 seconds or more before the internet is finally cut off.

I'll be uploading a video to YouTube soon to demonstrate this vulnerability. TP-Link VPN routers still suffer from this issue, and after more than two years, the company has yet to address it. While a kill switch would be ideal, it's absolutely critical that routing policies take effect instantly when the VPN connection drops. This delay is a serious security flaw that needs urgent attention.

  @aerubik Maybe firmware is still in beta