![]() > 12:07:26.735453: Network change detected with unsatisfied route and interface order > Here are some logs from the moment of this event: > If NETunnelProviderProtocol is configured with includeAllNetworks=true (Kill Switch), when network change is detected the device connectivity goes offline instead of routing VPN tunnel traffic through a new network. I had a patch somewhere here but haven’t spent much time testing it: Have you tried on the most recent beta? I think it works over there, but requires some tweaks to the network monitor code in WireGuard. 8:19 ` Jeroen Massar 1 sibling, 2 replies 10+ messages in threadįrom: Andrej Mihajlov 8:08 UTC ( / raw) 10:55 Changing network fails with includeAllNetworks (Kill Switch) Juraj 8:08 ` Andrej Mihajlov * Re: Changing network fails with includeAllNetworks (Kill Switch) WireGuardKit: 79aeb0be0d0aa3f6c8bd24309aaa8dcf03216fb4Ĭan someone confirm this issue or point to a possible workaround? 12:07:26.751550: peer(eN1f…Oymc) - Routine: sequential receiver - stopped ![]() 12:07:26.735453: Network change detected with unsatisfied route and interface order Here are some logs from the moment of this event: If NETunnelProviderProtocol is configured with includeAllNetworks=true (Kill Switch), when network change is detected the device connectivity goes offline instead of routing VPN tunnel traffic through a new network. 8:19 ` Jeroen Massar 0 siblings, 2 replies 10+ messages in thread Changing network fails with includeAllNetworks (Kill Switch) All of help / color / mirror / Atom feed * Changing network fails with includeAllNetworks (Kill Switch) 10:55 Juraj Hilje
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |