[{"data":1,"prerenderedAt":202},["ShallowReactive",2],{"blog:kill-switch-explained":3},{"zh-CN":4,"en":109},{"blocks":5,"faq":93},[6,9,11,13,17,19,21,23,26,28,35,37,40,42,44,47,49,51,54,73,75,78,80,82,84,86,89,91],{"type":7,"html":8},"p","断网保护(常见的英文名是 Kill Switch)做的事只有一件：隧道意外断开的瞬间，先把整台设备的网络掐掉，不让流量偷偷绕回那条没加密的路。",{"type":7,"html":10},"它解决的是一个很具体的空档期。平时连接正常的时候，这个功能什么都不做，完全感觉不到；只有隧道突然断开、还没重新建好的那几秒钟，它才会跳出来，把网络暂时锁住。少了这一步，那几秒钟看起来好像只是「卡了一下」,实际上流量可能已经走回了没加密的默认路线。",{"type":7,"html":12},"这篇讲清楚它具体在什么情况下触发、真正防住了什么、为什么有时候显得很烦人，以及它管不到的那部分。",{"type":14,"id":15,"html":16},"h2","bp-what","断网保护具体做的是哪件事",{"type":7,"html":18},"VPN 建立的隧道不是永远稳定的，断网、换节点、系统休眠唤醒，都可能让隧道瞬间掉线。正常情况下，设备会立刻退回到没有加密的普通网络连接，这个过程通常又快又安静，快到很多人根本没注意到中间有这个空档。",{"type":7,"html":20},"断网保护插在这个空档上。它会一直确认隧道是不是还活着，一旦发现隧道掉了，不等系统自己决定怎么处理，直接把整个网络访问权限先收回来，直到新的隧道建好才恢复。中间这段时间，设备看起来像是没网了，但换来的是流量不会悄悄走回那条没加密的路。",{"type":7,"html":22},"这个名字里的「Kill」听起来有点狠，但它切断的只是网络，不影响设备本身，也不会丢失正在填写的表单或者本地存的文件——恢复连接之后，大部分场景接着用就行，顶多是刚才那个页面要刷新一下。",{"type":14,"id":24,"html":25},"bp-trigger","什么情况下会触发",{"type":7,"html":27},"几种最常见的场景：",{"type":29,"items":30},"list",[31,32,33,34],"手动切换节点，旧隧道关闭、新隧道还没建好的那一两秒","Wi-Fi 和移动数据之间自动切换，网络接口重新初始化的瞬间","电脑或手机从休眠中唤醒，系统网络栈还没完全恢复","所在网络本身不稳定，隧道被动断开又重新协商",{"type":7,"html":36},"这几种场景的共同点是：断开都很短暂，大多数情况下几秒内会自动恢复，但恢复之前那一小段时间，风险和平时连接稳定的时候完全不一样。判断一次断线属于哪一种，其实不难——如果是自己手动切节点或者刚从锁屏解锁，大概率是前两种；如果什么都没动、网络却突然没了，更可能是所在网络本身不稳定，这种情况即使换了节点也可能反复出现。",{"type":14,"id":38,"html":39},"bp-protects","它真正防住的是什么",{"type":7,"html":41},"防住的就是这个空档期里的流量泄露。没有断网保护，隧道一断，浏览器、App 该发的请求不会等，它们会直接改走没加密的默认网络——你的真实 IP、访问的域名，这几秒里都可能直接暴露在外面，而你很可能根本没察觉，因为网页可能还是打开了，只是走了另一条路。",{"type":7,"html":43},"断网保护把这个空档从「悄悄漏出去」变成「先没网，等安全了再恢复」。代价是短暂的不方便，换来的是这几秒钟不会成为例外。",{"type":14,"id":45,"html":46},"bp-annoyance","为什么有时候显得很烦",{"type":7,"html":48},"断网保护不区分正在发生的连接是不是敏感的，它管的是全局。这意味着一次很平常的网络切换，比如你从家里的 Wi-Fi 走到电梯里切到移动数据，期间下载到一半的文件、正在播的视频、后台同步的邮件，都会跟着一起断一下。",{"type":7,"html":50},"对赶时间的人来说，这几秒钟的「突然没网」很容易被当成故障，尤其是频繁在 Wi-Fi 和移动数据之间切换的使用场景，断网保护触发的频率会明显更高。比较极端的例子是坐地铁——信号在有和没有之间来回跳，系统不停地在 Wi-Fi、数据、断网之间切换，断网保护跟着一起频繁动作，体验上会觉得特别烦。这也是为什么它通常做成一个可以自己决定开关的选项，而不是强制一直开着。",{"type":14,"id":52,"html":53},"bp-steps","该怎么用它",{"type":55,"items":56},"steps",[57,61,65,69],{"title":58,"body":59},"弄清楚是「全局断网」还是「只挡新连接」",[60],"不同实现方式的严格程度不一样：有的是彻底断网，已经建立的连接也会被切断；有的只挡新发起的连接，已经在传的数据不受影响。两种都叫断网保护，严格程度却完全不是一回事，看清楚当前用的是哪一种，再决定要不要开。",{"title":62,"body":63},"只在需要严格保护的时候打开",[64],"日常刷手机、看视频，断线几秒钟自动恢复就好，不一定非要开断网保护。处理转账、登录重要账号这类操作之前，提前打开会更放心，多等几秒钟总比流量走漏那一下更值得。",{"title":66,"body":67},"配合自动重连一起用",[68],"断网保护解决的是断线瞬间不泄露，自动重连解决的是尽快把隧道建回来。两个一起开，体验是「短暂没网，很快恢复」,只开断网保护而不开自动重连，可能变成「没网了要手动点连接」。",{"title":70,"body":71},"手机和电脑分开看待设置",[72],"移动设备在 Wi-Fi 和数据之间切换的频率比电脑高得多，断网保护触发的次数自然也更多。如果在手机上觉得太频繁，可以先确认问题是不是出在网络切换本身，而不是急着把功能关掉；电脑相对固定连一个网络，触发频率低很多，平时开着基本没有感觉。",{"type":74},"downloads",{"type":14,"id":76,"html":77},"bp-limits","断网保护防不住什么",{"type":7,"html":79},"它防的是隧道断开之后的流量，不负责隧道为什么会断。如果断线是因为节点本身不稳定，断网保护只会让你更频繁地感觉到「没网」,不会让那个节点变稳定，该做的还是换一个节点，可以参考\u003Ca href=\"\u002Fblog\u002Fvpn-connected-but-no-internet\u002F\">断线排查\u003C\u002Fa>那篇的思路。",{"type":7,"html":81},"它也不管断线之前已经发出去的流量——那部分数据在隧道还活着的时候就已经上路了，安不安全取决于当时那条连接本身。如果担心的是域名解析这一层单独走漏，那是另一个问题，\u003Ca href=\"\u002Fblog\u002Fdns-leak-check-guide\u002F\">DNS 泄漏自查\u003C\u002Fa>讲的正是这一层，断网保护不覆盖这部分。",{"type":7,"html":83},"另外，断网保护管的是系统级的网络出口，如果某个 App 自己绕过系统代理设置直接连网，断网保护也拦不住那个 App 单独发出去的流量。这种情况比较少见，但确实存在，不能指望断网保护是万能的最后一道闸门。",{"type":7,"html":85},"也不要把它和「公共网络更安全」这件事混为一谈。在\u003Ca href=\"\u002Fblog\u002Fpublic-wifi-risks\u002F\">公共 Wi-Fi\u003C\u002Fa> 上，风险大多来自假热点和钓鱼登录页，断网保护对这两类问题基本不起作用——它只管隧道本身断没断，不管你连的这个网络本身是不是有问题。两件事分开评估，才不会误以为开了断网保护就等于公共网络也变安全了。",{"type":14,"id":87,"html":88},"bp-final","总结",{"type":7,"html":90},"断网保护解决的是一个很窄但很实际的问题：隧道意外断开的那几秒钟，流量该不该被放行。答案是不该，所以它选择先断网，换取那几秒不出意外。它不解决断线的根本原因，不管断线前已经发出去的数据，也管不到绕开系统代理的个别 App,更不会让不安全的公共网络本身变安全，严格意义上只管这一个空档。",{"type":7,"html":92},"值不值得为了这几秒钟忍受偶尔的不方便，取决于你在做什么。刷手机、看视频，断线几秒钟自动恢复就好；在公共网络处理转账、登录重要账号之前，提前打开会更放心，这时候多等几秒钟换来的确定性是值得的。\u003Ca href=\"\u002Ffeatures\u002F\">快橙\u003C\u002Fa>的断线保护和自动重连是配合着做的，断了尽快连回来，连不上之前也不留漏洞，具体的加密方式写在\u003Ca href=\"\u002Fsecurity\u002F\">安全说明\u003C\u002Fa>里。想先感受一下重连有多快，注册后每天都有免费时长，\u003Ca href=\"\u002Forder\u002F\">了解详情\u003C\u002Fa>。",[94,97,100,103,106],{"q":95,"a":96},"断网保护开着，为什么切换 Wi-Fi 和流量时会突然没网？","这是它在正常工作。网络接口切换的那一刻隧道会短暂断开，断网保护为了不让流量走漏，直接把整个网络先掐掉，等新隧道建好才放行。这几秒没网是设计好的行为，不是故障。",{"q":98,"a":99},"断网保护和自动重连，是不是都该开着？","建议都开。断网保护管的是断线瞬间不泄露，自动重连管的是尽快把隧道建回来，两个解决的是同一个问题的两端，只开一个体验都不完整。",{"q":101,"a":102},"为什么我这边好像没找到断网保护这个开关？","不同平台的实现和入口不太一样，有些默认开启、不单独显示开关，有些藏在高级设置里，具体位置要看当前用的客户端版本和平台。",{"q":104,"a":105},"断网保护会不会拖慢正常上网的速度？","不会。它平时什么都不做，只在隧道意外断开的那一刻介入，连接正常的时候完全感觉不到它的存在。",{"q":107,"a":108},"断线的时候，之前已经发出去的那部分数据还安全吗？","断网保护挡的是断线之后还没发出去的流量。断线前已经发出去的那部分，安不安全取决于当时那条连接本身，断网保护帮不上这个忙。",{"blocks":110,"faq":186},[111,113,115,117,119,121,123,125,127,129,135,137,139,141,143,145,147,149,151,169,170,172,174,176,178,180,182,184],{"type":7,"html":112},"A kill switch does exactly one thing: the instant the tunnel drops unexpectedly, it cuts the whole device's network access so traffic can't quietly fall back to the unencrypted path.",{"type":7,"html":114},"It exists for one very specific gap. While the connection is healthy, this feature does nothing at all — you won't notice it's there. Only in the few seconds after a tunnel drops and before a new one is up does it step in and lock the network down temporarily. Skip that step, and those few seconds look like nothing more than a hiccup, while your traffic may already have quietly switched to the unencrypted default route.",{"type":7,"html":116},"Here's exactly when it fires, what it actually protects, why it can feel annoying, and what it has no say over.",{"type":14,"id":15,"html":118},"What a kill switch actually does",{"type":7,"html":120},"A VPN tunnel isn't permanently stable — a dropped connection, switching nodes, or a device waking from sleep can all take it down in an instant. Normally the device falls back to a plain, unencrypted connection right away, and that handoff is usually so fast and quiet that most people never notice the gap in between.",{"type":7,"html":122},"A kill switch sits right in that gap. It keeps checking whether the tunnel is still alive, and the moment it isn't, it takes back network access immediately rather than letting the system decide on its own, holding it until the new tunnel is ready. During that stretch the device looks like it has no internet, but the trade is that those seconds never become the exception where something leaks.",{"type":7,"html":124},"The word &quot;kill&quot; sounds harsh, but all it cuts is the network — not the device itself, and not a form you're filling in or a file saved locally. Once the connection is back, most things just carry on; at worst, the page you were on needs a refresh.",{"type":14,"id":24,"html":126},"When it actually fires",{"type":7,"html":128},"The most common triggers:",{"type":29,"items":130},[131,132,133,134],"Switching nodes by hand, in the second or two between the old tunnel closing and the new one coming up","Wi-Fi and mobile data switching automatically as the network interface reinitializes","A computer or phone waking from sleep before the network stack is fully back","The current network itself being unstable, dropping the tunnel and forcing it to renegotiate",{"type":7,"html":136},"What these all have in common: the drop is brief and usually resolves itself within seconds, but the risk during that short window is nothing like the risk during a stable connection. Telling them apart isn't hard — if you just switched nodes yourself or just unlocked the screen, it's almost certainly one of the first two; if nothing changed and the network just vanished, the network itself is more likely unstable, and that kind of drop can keep recurring even after you change nodes.",{"type":14,"id":38,"html":138},"What it actually protects against",{"type":7,"html":140},"It protects against exactly this leak during the gap. Without a kill switch, the moment a tunnel drops, the browser and every app keep sending whatever they were sending — just over the unencrypted default connection instead. Your real IP and the domains you're visiting can be exposed for those few seconds, often without you noticing at all, because the page may still load fine; it just took a different route to get there.",{"type":7,"html":142},"A kill switch turns that gap from &quot;quietly leaks&quot; into &quot;goes offline first, comes back once it's safe.&quot; The cost is a brief inconvenience; what you get in return is that those seconds never become the exception.",{"type":14,"id":45,"html":144},"Why it can be genuinely annoying",{"type":7,"html":146},"A kill switch doesn't distinguish a sensitive connection from an ordinary one — it acts globally. So an entirely routine network switch, like walking from your home Wi-Fi into an elevator and onto mobile data, takes a half-downloaded file, a video mid-playback, and a background email sync down with it for a moment.",{"type":7,"html":148},"For anyone in a hurry, those few seconds of &quot;suddenly offline&quot; are easy to mistake for a fault, and the effect is far more noticeable for anyone constantly switching between Wi-Fi and mobile data. The extreme case is riding the subway — signal flickers in and out, the system keeps hopping between Wi-Fi, data, and nothing, and the kill switch fires right along with it, which gets old fast. That's exactly why it's usually built as something you can switch on or off yourself, not something forced on permanently.",{"type":14,"id":52,"html":150},"How to actually use it",{"type":55,"items":152},[153,157,161,165],{"title":154,"body":155},"Work out whether it's &quot;cut everything&quot; or &quot;just block new connections&quot;",[156],"Implementations differ in how strict they are: some cut everything, including connections already established; others only block new ones, leaving whatever's already transferring untouched. Both get called a kill switch, but they're not remotely the same in practice — know which one you're dealing with before deciding whether to turn it on.",{"title":158,"body":159},"Turn it on only when you need the strict version",[160],"For everyday scrolling and video, a few seconds offline that resolve on their own is fine — you don't need a kill switch running for that. Before a bank transfer or logging into an important account, turning it on first is the safer call; a few extra seconds of waiting beats even one instance of a leak.",{"title":162,"body":163},"Pair it with auto-reconnect",[164],"A kill switch stops leaks the moment the tunnel drops; auto-reconnect gets the tunnel back up as fast as possible. Run both and the experience is &quot;briefly offline, back quickly.&quot; Run the kill switch alone without auto-reconnect, and it can turn into &quot;offline until you tap reconnect yourself.&quot;",{"title":166,"body":167},"Treat phones and computers as separate cases",[168],"A mobile device switches between Wi-Fi and data far more often than a computer does, so a kill switch fires more often there too. If it feels too frequent on your phone, check first whether the cause is the network switching itself before rushing to turn the feature off; a computer usually stays on one network, so it fires rarely enough that you'll barely notice it's on.",{"type":74},{"type":14,"id":76,"html":171},"What a kill switch does not protect against",{"type":7,"html":173},"It protects traffic after the tunnel drops — it has no say in why the tunnel dropped in the first place. If the cause is an unstable node, a kill switch will just make you notice &quot;no internet&quot; more often without making that node any more stable; the actual fix is still switching nodes, and \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-connected-but-no-internet\u002F\">diagnosing a dead connection\u003C\u002Fa> covers that approach.",{"type":7,"html":175},"It also has nothing to do with traffic that already went out before the drop — that data was already on its way while the tunnel was still alive, and how safe it was depends entirely on that connection at the time. If what worries you is DNS resolution leaking on its own, that's a separate problem; \u003Ca href=\"\u002Fen\u002Fblog\u002Fdns-leak-check-guide\u002F\">checking for a DNS leak\u003C\u002Fa> covers that exact layer, which a kill switch doesn't touch.",{"type":7,"html":177},"It's also worth knowing a kill switch governs the system-level network exit — if some app bypasses the system proxy and connects directly on its own, a kill switch can't stop that app's traffic either. That's uncommon, but it happens, and it's not a reason to treat a kill switch as some final, universal safety net.",{"type":7,"html":179},"Don't confuse it with &quot;the public network itself is now safe,&quot; either. On \u003Ca href=\"\u002Fen\u002Fblog\u002Fpublic-wifi-risks\u002F\">public Wi-Fi\u003C\u002Fa>, most of the risk comes from fake hotspots and phishing login portals, and a kill switch does essentially nothing about either — it only cares whether the tunnel itself is up, not whether the network you joined has a problem of its own. Keep the two separate, or it's easy to assume turning on a kill switch makes a shady public network safe, which it doesn't.",{"type":14,"id":87,"html":181},"In summary",{"type":7,"html":183},"A kill switch solves one narrow but genuinely useful problem: whether traffic should be allowed through during the few seconds a tunnel drops unexpectedly. The answer is no, so it goes offline first to make sure those seconds never become the exception. It doesn't fix why the drop happened, doesn't cover data sent before it, doesn't reach an app that bypasses the system proxy, and doesn't make an unsafe public network safe — strictly speaking, it only ever covers this one gap.",{"type":7,"html":185},"Whether the occasional inconvenience is worth it depends on what you're doing. For scrolling and video, a few offline seconds that resolve themselves are fine; before a transfer or an important login on a public network, turning it on first is the safer trade — a few extra seconds for that certainty is worth it. \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">FastOrange\u003C\u002Fa> pairs its kill switch with auto-reconnect, so it comes back fast and never leaves a gap open in the meantime; the encryption behind it is on the \u003Ca href=\"\u002Fen\u002Fsecurity\u002F\">security page\u003C\u002Fa>. Every account gets free daily trial time after signup if you want to see how fast the reconnect really is — \u003Ca href=\"\u002Fen\u002Forder\u002F\">see the details\u003C\u002Fa>.",[187,190,193,196,199],{"q":188,"a":189},"Why does the internet cut out for a second when I switch between Wi-Fi and mobile data with the kill switch on?","That's it working as intended. The tunnel drops briefly the moment the network interface switches, and the kill switch cuts the whole network rather than let traffic leak, until the new tunnel is up. Those few offline seconds are by design, not a fault.",{"q":191,"a":192},"Should I turn on both the kill switch and auto-reconnect?","Yes, ideally both. The kill switch stops leaks at the moment of disconnection; auto-reconnect gets the tunnel back up quickly. They cover opposite ends of the same problem, and running only one leaves the experience half-finished.",{"q":194,"a":195},"I can't find a kill switch toggle anywhere. Where is it?","Implementations and menu locations vary by platform. Some turn it on by default with no visible toggle; others bury it in advanced settings. Check the exact spot for your current client version and platform.",{"q":197,"a":198},"Does a kill switch slow down a normal connection?","No. It does nothing at all while the tunnel is healthy and only steps in the moment it drops unexpectedly — you won't notice it exists while the connection is stable.",{"q":200,"a":201},"Is data sent right before a drop still safe?","A kill switch only blocks traffic that hasn't gone out yet after the drop. Whatever was already sent before the tunnel failed depends on that connection at the time — the kill switch can't do anything about it after the fact.",1794787866997]