# Internet Kill Switch for VPN Policy based on Client **URL:** \ **Category:** Router\ **Created:** [October 10, 2024, 5:35am UTC](https://forum.gl-inet.com/t/internet-kill-switch-for-vpn-policy-based-on-client/48853 "2024-10-10T05:35:08Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![j2zero](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/7ea924/32.png) [@j2zero](https://forum.gl-inet.com/u/j2zero)\ **Post date:** [March 31, 2025, 7:17am UTC](https://forum.gl-inet.com/t/internet-kill-switch-for-vpn-policy-based-on-client/48853/5 "2025-03-31T07:17:22Z")
Here is how I achieved what you are after. > [@Suggestion\* Killswitch for VPN when VPN is disabled](https://forum.gl-inet.com/t/suggestion-killswitch-for-vpn-when-vpn-is-disabled/43391): > > I have the same desire as other users on this forum with regards to the "Killswitch" functionality. If I am using policy based routing (allowing only certain Mac addresses to access the VPN) I assume that if the Wireguard client was disabled (turned off) then the the policy based devices that are specified to go via the VPN would NOT hit the clearnet (WAN) that to me is a Killswitch. However, if the Wireguard client has been disabled / turned off then devices will use the WAN, only when the Wi… "Block Non-VPN Traffic" is left toggled off. --- _[View the full topic](https://forum.gl-inet.com/t/internet-kill-switch-for-vpn-policy-based-on-client/48853)._