[{"data":1,"prerenderedAt":213},["ShallowReactive",2],{"blog:switch-between-wifi-and-data":3},{"zh-CN":4,"en":114},{"blocks":5,"faq":98},[6,9,11,13,17,19,21,23,25,28,47,50,68,70,73,82,85,87,89,91,94,96],{"type":7,"html":8},"p","出门下楼的那几步，手机从家里的 Wi-Fi 跳到移动数据，正在加载的页面卡住，视频缓冲圈转了两圈——这是手机 VPN 用户最容易遇到的一种「断线」，但严格说它不是故障，是网络接口换了一个，隧道必须重新搭一次。",{"type":7,"html":10},"这件事没法做到完全无感，因为 Wi-Fi 和移动数据在手机里是两块完全不同的硬件，各有各的地址。隧道是搭在某一个接口上的，接口消失了，隧道自然要重新建立，这中间的几秒钟就是你感觉到的「断线」。",{"type":7,"html":12},"好消息是这几秒钟可以被压缩得很短，坏消息是不可能压缩到零——如果有工具告诉你能做到完全无缝切换，那多半是把「很快恢复」包装成了「没有中断」。这篇讲清楚切换时到底发生了什么，怎么把恢复时间缩到最短，以及哪些卡顿其实跟这次切换没关系。",{"type":14,"id":15,"html":16},"h2","bp-why","切换的瞬间到底发生了什么",{"type":7,"html":18},"手机同时具备 Wi-Fi 和移动数据两套网络硬件，但系统通常只会让其中一个真正在用。从 Wi-Fi 走到移动数据，等于原来那条路径上的地址整个消失，新地址还没分配好，中间有一个短暂的空白期。",{"type":7,"html":20},"隧道正好搭在这条路径上，路径没了，隧道也就跟着断了，必须在新的接口上重新握手建立一次，这个过程和你刚开机连接时做的事情本质上是一样的，只是发生得更突然。这个重建过程本身很快，但如果客户端没有及时发现接口已经换了，或者要等你手动点一下才肯重连，这段空白期就会被拖长，变成你能明显感觉到的卡顿。",{"type":7,"html":22},"同城市内 Wi-Fi 跳 Wi-Fi（比如从家里的路由器切到楼下商场的）通常更顺滑，因为两边好歹都是同一类接口，系统内部处理得比较熟练。Wi-Fi 换成移动数据是换了整个不同的硬件模块，这一步天生比同类切换要慢一点，\u003Cstrong>指望它和同类切换一样顺滑并不现实\u003C\u002Fstrong>，知道这一点，遇到几秒延迟就不会觉得是工具出了问题。",{"type":7,"html":24},"把这种等待放进日常习惯里看会更容易接受：接口消失到隧道重新连上，正常情况下只需要很短的一段时间就能完成，往往你还没点开下一个页面它就已经恢复了。明显超出这种感觉、等了很久还没反应，才值得怀疑是别的原因，而不是这次切换本身。",{"type":14,"id":26,"html":27},"bp-prepare","让切换更顺滑的准备",{"type":29,"items":30},"steps",[31,35,39,43],{"title":32,"body":33},"打开自动重连",[34],"先确认客户端设置里的自动重连是开着的。没开的话，每一次网络切换都要自己手动点一下连接，体验上会觉得断线特别频繁，其实只是少了这一个开关，不是网络本身有多不稳定。多数主流工具默认就带这个能力，具体能不能覆盖你的场景，可以看一下\u003Ca href=\"\u002Ffeatures\u002F\">功能介绍\u003C\u002Fa>。",{"title":36,"body":37},"固定一个常用节点",[38],"测试切换效果的时候，节点和网络接口最好不要同时变。如果两个变量一起动，出问题了很难判断到底是接口切换的锅，还是刚好那个节点本身不稳定，先固定节点，只让网络接口变化。",{"title":40,"body":41},"留意省电设置有没有把它冻结",[42],"手机的省电策略会把长时间在后台的 App 直接冻结甚至杀掉，而不是让它保持连接状态。切回来发现「断线」，很多时候不是网络的问题，是这个 App 在后台被系统结束了，需要重新打开而不是重新连接。",{"title":44,"body":45},"如果开了分应用规则，留意它要不要重新检查",[46],"如果你还给某些 App 单独设过直连规则，网络接口换了一次以后，这条规则不一定会跟着失效，但值得顺手确认一下。\u003Ca href=\"\u002Fblog\u002Fvpn-split-tunneling-guide\u002F\">分应用代理怎么用\u003C\u002Fa>里讲了怎么验证这类规则是否还生效。",{"type":14,"id":48,"html":49},"bp-steps","实际切换时的操作顺序",{"type":29,"items":51},[52,56,60,64],{"title":53,"body":54},"第一步：切换前看一眼当前状态",[55],"确认现在确实是连接状态（图标是绿的），这样切换以后如果出问题，你能判断是切换本身导致的，还是切换之前就已经不正常。",{"title":57,"body":58},"第二步：切到新网络后先等几秒",[59],"给客户端几秒钟去发现接口变了、重新建立隧道，不要切完立刻打开一个大文件或者视频。太快操作只会看到一次原本几秒内就会自己消失的失败。",{"title":61,"body":62},"第三步：超过十几秒还没恢复，手动重连一次",[63],"等待不是没有上限的。明显超过正常范围还没恢复，直接手动断开再连接，比继续等它自己恢复更快，也更省心。",{"title":65,"body":66},"第四步：确认新连接和切换前是同一个节点",[67],"重连以后看一眼当前节点，和切换前是不是同一个地区。如果自动切换成了别的地区，一些依赖「登录环境一致」的 App 会把这当成一次新的登录环境，弹出额外验证。",{"type":69},"downloads",{"type":14,"id":71,"html":72},"bp-pitfalls","常见的几个坑",{"type":74,"items":75},"list",[76,77,78,79,80,81],"切换瞬间正好在下载大文件或者进行语音、视频通话，重连以后进度清零或者通话中断，这是隧道真的重建了一次，不是下载或者通话本身出了问题","Wi-Fi 没有关，移动数据又开着，系统在两者之间反复跳，客户端跟着反复重连，感觉比单纯断一次还乱","App 被系统直接杀掉而不是冻结，回来发现连接正常，但 App 本身要重新打开","自动重连开着，但节点选的是「自动最优」，每次重连都换一个地区，账号类 App 会觉得登录环境一直在变","长时间没有网络信号（比如进电梯、进地库），回来以后还在等重连，其实是先要等手机本身重新搜到信号，隧道要等信号恢复以后才能开始重建","手动切换过一次数据网络的运营商制式（比如从 4G 降到 3G），接口本身没变，但底层链路质量变了，表现上和真正的接口切换很像",{"type":14,"id":83,"html":84},"bp-network","什么时候这不是手机 VPN 能解决的",{"type":7,"html":86},"有些环境本身就会造成频繁的网络切换或者信号中断，跟用什么手机 VPN 没什么关系：地铁和电梯这类信号弱覆盖的空间，移动中不断换基站的车辆，还有单纯是运营商在某个区域覆盖不好。",{"type":7,"html":88},"判断方法很简单：换成完全不用任何工具的状态，纯粹测试手机本身的网络连接是不是也一样断断续续。如果是，说明问题出在信号覆盖，而不是任何客户端的重连逻辑，这时候换工具不会有帮助。如果只有手机 VPN 在的时候才断，那才值得去看客户端本身的设置。",{"type":7,"html":90},"公共交通、电梯、地下车库这几个场景值得单独记住，因为它们出现的频率足够高。一旦确认过一次问题出在信号本身，以后再遇到同样的场景就不用重新判断，等信号恢复就好，不用怀疑是设置出了问题。想更系统地排查连接本身的问题，\u003Ca href=\"\u002Fblog\u002Fvpn-keeps-disconnecting\u002F\">VPN 老是自动断开怎么办\u003C\u002Fa>专门讲了断线的排查顺序。",{"type":14,"id":92,"html":93},"bp-final","总结",{"type":7,"html":95},"Wi-Fi 和移动数据之间的切换没法做到零延迟，因为两个接口是完全不同的硬件，隧道必须重新搭一次，这一点不会因为换了哪个品牌的工具而改变。能做的是把这个过程缩到最短：打开自动重连、测试时固定节点、留意省电设置有没有把 App 冻结，切换以后给它几秒钟再操作，而不是立刻判定是出了故障。",{"type":7,"html":97},"如果你发现移动数据能用、Wi-Fi 反而不行（或者反过来），这通常不是切换过程本身的问题，而是另一层原因，\u003Ca href=\"\u002Fblog\u002Fvpn-not-working-on-mobile-data\u002F\">移动数据能用、Wi-Fi 不行怎么办\u003C\u002Fa>专门讲了这种情况。日常想少折腾这些细节，\u003Ca href=\"\u002Forder\u002F\">快橙\u003C\u002Fa>默认自动重连、一键换节点，注册后每天有免费试用时长，先拿它测一次自己最常切换的那条路径。",[99,102,105,108,111],{"q":100,"a":101},"为什么在家换 Wi-Fi 不断，出门换数据就断？","在家换的多是同一类接口之间的切换，系统内部处理得比较平滑。Wi-Fi 换成移动数据是换了一整个不同的网络硬件，隧道必须整个重建，这一步天生没法做到完全无感。",{"q":103,"a":104},"自动重连打开以后，是不是就完全不会断了？","会明显缩短断开的时间，但接口切换那一两秒的空隙还是存在。自动重连解决的是「要不要我自己动手点连接」，不是让切换本身消失。",{"q":106,"a":107},"切换以后要等多久才算正常？","多数情况几秒内会自己恢复。超过十几秒没反应，与其等，不如直接手动断开重连一次，比等它自己好更快。",{"q":109,"a":110},"地铁上信号一直断断续续，是不是该换个工具？","先别急着换。信号本身在弱覆盖区间反复丢失和恢复，跟用什么工具关系不大，换工具通常解决不了基站覆盖的问题。",{"q":112,"a":113},"快橙在切换网络时是怎么处理的？","快橙断开以后会自动重连，换节点也是一步到位，不需要每次手动重新连接。日常切换网络时能省掉大部分手动操作，参考\u003Ca href=\"\u002Ffeatures\u002F\">功能介绍\u003C\u002Fa>。",{"blocks":115,"faq":197},[116,118,120,122,124,126,128,130,132,134,152,154,172,173,175,183,185,187,189,191,193,195],{"type":7,"html":117},"Walking down the stairs and out the door, the phone hops from home Wi-Fi to mobile data, the page that was loading freezes, the video buffering wheel spins twice — this is the failure mode mobile VPN users run into most often, and strictly speaking it is not a fault. The network interface itself changed, and the tunnel has to be rebuilt.",{"type":7,"html":119},"There is no way to make this fully invisible, because Wi-Fi and mobile data are two entirely different pieces of hardware inside the phone, each with its own address. The tunnel sits on top of one specific interface; once that interface disappears, the tunnel has nothing left to sit on and has to be re-established, and that handful of seconds is what you feel as a &quot;drop.&quot;",{"type":7,"html":121},"The good news is that handful of seconds can be compressed a long way. The bad news is it cannot be compressed to zero — if a tool claims a fully seamless handoff, it is probably dressing up &quot;recovers fast&quot; as &quot;never interrupted.&quot; This piece explains what actually happens during the switch, how to shrink the recovery time as far as it goes, and which stalls have nothing to do with this handoff at all.",{"type":14,"id":15,"html":123},"What actually happens the instant you switch",{"type":7,"html":125},"A phone carries two separate pieces of network hardware, Wi-Fi and mobile data, but the system generally only keeps one of them truly active. Moving from Wi-Fi to mobile data means the address on the old path disappears entirely, the new address is not assigned yet, and there is a short blank gap in between.",{"type":7,"html":127},"The tunnel happens to sit exactly on that path. Once the path is gone, the tunnel goes with it and has to shake hands again on the new interface — mechanically the same thing that happens when you first connect, just triggered more abruptly. That rebuild itself is quick, but if the client is slow to notice the interface changed, or insists on waiting for you to tap reconnect yourself, that blank gap stretches out into the stall you actually notice.",{"type":7,"html":129},"Wi-Fi to Wi-Fi within the same building (say, from your home router to the mall downstairs) is usually smoother, because both ends are at least the same class of interface and the system has practiced handling that case. Wi-Fi to mobile data swaps an entire different hardware module, and that step is inherently slower than a same-type switch — \u003Cstrong>expecting it to feel as smooth as a same-type switch is not realistic\u003C\u002Fstrong>, and knowing that in advance keeps a few seconds of delay from looking like the tool failing.",{"type":7,"html":131},"Put the wait in everyday terms: under normal conditions, the time from the old interface vanishing to the tunnel reconnecting is short enough that you often will not even have opened the next page before it recovers. If it is clearly taking far longer than that with nothing happening, that is when it is worth suspecting something else, rather than the handoff itself.",{"type":14,"id":26,"html":133},"Getting ready for a smoother handoff",{"type":29,"items":135},[136,140,144,148],{"title":137,"body":138},"Turn on auto-reconnect",[139],"Check first that auto-reconnect is actually enabled in the client's settings. Without it, every single network change requires a manual tap to reconnect, which makes drops feel far more frequent than they really are — that is simply a switch left off, not the network being unreliable. Most mainstream tools ship this by default; whether it covers your case is worth checking under \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">what the app does\u003C\u002Fa>.",{"title":141,"body":142},"Pin down one node you use regularly",[143],"While testing how the handoff behaves, try not to change the node and the network interface at the same time. Move both at once and, if something goes wrong, you cannot tell whether the interface switch or an unstable node caused it. Keep the node fixed and let only the interface change.",{"title":145,"body":146},"Check whether battery settings are freezing it",[147],"A phone's power-saving policy can freeze or outright kill an app that has sat in the background a while, rather than letting it hold its connection open. Coming back to what looks like a &quot;drop&quot; is often not a network problem at all — the app was ended by the system and needs reopening, not reconnecting.",{"title":149,"body":150},"If you have a split-tunneling rule, check it survived",[151],"If you have set up a direct-connection rule for certain apps, an interface change will not necessarily break it, but it is worth a quick check regardless. \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-split-tunneling-guide\u002F\">How to use split tunneling\u003C\u002Fa> covers how to confirm a rule like that is still active.",{"type":14,"id":48,"html":153},"The order of operations when you actually switch",{"type":29,"items":155},[156,160,164,168],{"title":157,"body":158},"Step one: glance at the current state before you switch",[159],"Confirm you are actually connected right now (a green icon) so that if something looks wrong after the switch, you can tell whether the switch caused it or it was already off before.",{"title":161,"body":162},"Step two: after landing on the new network, give it a few seconds",[163],"Let the client notice the interface changed and rebuild the tunnel before you open a large file or a video. Acting too fast just shows you a failure that would have cleared itself within a few seconds anyway.",{"title":165,"body":166},"Step three: reconnect manually if it clearly has not recovered",[167],"Waiting does not have to be open-ended. Once it is clearly well past the normal range with no recovery, disconnecting and reconnecting by hand beats continuing to wait, and it is less stressful too.",{"title":169,"body":170},"Step four: confirm the new connection landed on the same node",[171],"After reconnecting, check the current node against the one from before the switch. If it silently switched to a different region, apps that expect a consistent login environment may treat that as a fresh session and throw an extra verification prompt.",{"type":69},{"type":14,"id":71,"html":174},"A few common traps",{"type":74,"items":176},[177,178,179,180,181,182],"A large download, or a voice or video call, happens to be running right at the switch, and the progress resets or the call drops afterward — the tunnel genuinely rebuilt itself, the download or call was not at fault","Wi-Fi was never turned off and mobile data is also on, so the system keeps hopping between the two and the client keeps reconnecting, which feels messier than a single clean drop","The app was killed outright by the system rather than frozen; the connection itself is fine on return, but the app still needs a fresh launch","Auto-reconnect is on, but the node is set to &quot;auto-best,&quot; so every reconnect lands in a different region and account-bound apps read that as a constantly shifting login environment","A long stretch with no signal at all (an elevator, an underground garage) leaves you waiting on a reconnect that cannot start until the phone itself finds signal again","A manual switch between carrier generations (say, dropping from 4G to 3G) leaves the interface itself unchanged, but the underlying link quality shifts enough to look just like a real interface switch",{"type":14,"id":83,"html":184},"When this is not something any tool can fix",{"type":7,"html":186},"Some environments cause frequent handoffs or signal loss on their own, regardless of which mobile VPN is running: subways and elevators with weak coverage, a moving vehicle constantly changing cell towers, or a carrier simply having poor coverage in a given area.",{"type":7,"html":188},"The test is simple: turn everything off and check whether the phone's raw connection is just as choppy on its own. If it is, the cause is signal coverage, not any client's reconnect logic, and switching tools will not help. If the drops only happen while the mobile VPN is active, that is when the client's own settings are worth a look.",{"type":7,"html":190},"Public transit, elevators and underground garages are worth remembering specifically, since they come up often enough. Once you have confirmed the cause is signal a single time, the next time you hit the same spot you do not need to re-diagnose it — just wait for signal to return. For a more systematic way to work through drops in general, \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-keeps-disconnecting\u002F\">what to do when a VPN keeps disconnecting\u003C\u002Fa> covers that on its own.",{"type":14,"id":92,"html":192},"In summary",{"type":7,"html":194},"Switching between Wi-Fi and mobile data cannot reach zero delay, because the two interfaces are genuinely different hardware and the tunnel has to be rebuilt — that does not change no matter whose client you run. What you can do is shrink the process: turn on auto-reconnect, keep the node fixed while testing, check whether battery settings are freezing the app, and give it a few seconds after switching before deciding something is actually broken.",{"type":7,"html":196},"If you find mobile data works while Wi-Fi does not (or the other way round), that is usually a different layer of the problem rather than the handoff itself, and \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-not-working-on-mobile-data\u002F\">mobile data works but Wi-Fi does not\u003C\u002Fa> covers that case specifically. To spend less time on this day to day, \u003Ca href=\"\u002Fen\u002Forder\u002F\">FastOrange\u003C\u002Fa> reconnects automatically and switches node in one tap by default — every registered account gets free trial time daily, so test it on the route you switch most often first.",[198,201,204,207,210],{"q":199,"a":200},"Why does switching Wi-Fi networks at home not drop the connection, but switching to mobile data does?","Switching within the same interface type is usually handled smoothly by the system internally. Wi-Fi to mobile data swaps the entire hardware module, and the tunnel has no choice but to rebuild completely — that step was never going to be seamless.",{"q":202,"a":203},"If I turn on auto-reconnect, does it stop dropping altogether?","It cuts the downtime a lot, but the second or so it takes the interface itself to switch is still there. Auto-reconnect answers 'do I have to tap connect myself,' not 'does the handoff disappear.'",{"q":205,"a":206},"How long should I wait before assuming something is wrong?","Most cases recover within a few seconds on their own. If it has clearly been much longer than that with nothing happening, disconnecting and reconnecting manually beats waiting it out.",{"q":208,"a":209},"The subway keeps cutting in and out — should I switch tools?","Not yet. Signal dropping and returning repeatedly in a weak-coverage stretch has little to do with which tool you run, and switching tools will not fix cell tower coverage.",{"q":211,"a":212},"What does FastOrange do when the network changes?","FastOrange reconnects automatically once a link drops, and changing node is a single tap too, so most of the manual work goes away on its own. See \u003Ca href=\"\u002Fen\u002Ffeatures\u002F\">what the app does\u003C\u002Fa>.",1794787838649]