Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    VPN Kill switch needed?

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    2 Posts 2 Posters 352 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Steg
      last edited by

      is there a need to create a floating rule to kill the internet connection if the vpn drops out?
      i used to have one but currently i don't have any rules to my WAN port anymore, only to the vpn gateways

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        If you don't have any outbound NAT rules on the WAN and your internal subnets are private IPs then nothing routable will leave. No connections can be made from internal clients out of the WAN directly.

        The term 'kill switch' to refer to that is absurd though. Kill switch implies something you set to kill all the traffic. The term 'fail safe' fits that rule setup far better. If the VPN is disconnected the systems fails. Safe. But I guess it wasn't suffciently buzz-wordy for the VPN marketers. 🙄

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.