CloudFlare Warp - первый среди всех

uwu · October 17, 2025, 6:47pm

del

No_nameuser · October 18, 2025, 10:39am

Есть ли инструкция как настроить Zero trust в виде обычного Wireguard?
Всё что находил в поиске не давал токен получить для wgcf

Dikoz · October 18, 2025, 11:57am

Можно, и потом даже можно его через авг использовать, что куда лучше чем трогать их официальный клиент и их “разделяемые туннели” GitHub - rany2/warp.sh: WARP wireguard config generator in POSIX Shell

No_nameuser · October 18, 2025, 1:21pm

Вроде получилось но, у него разве не должен быть внутренний ip отличный от 172.16.0.2/32?
В отличии от обычного warp

Hrenowatice · October 18, 2025, 2:21pm

Любопытно, спасибо. То есть принудительная ротация ключей — миф?
А то официальный клиент действительно неприятно наводит свои порядки в nftables вплоть до «случайного» запрета SSH. Форум официалов завален этим вопросом.

alk2ntc · October 18, 2025, 3:30pm

В документации usque тоже есть раздел, посвященный работе с Zero Trust, но usque через WG не соединяет.

ZT назначает клиентам внутренние адреса из диапазона 100.96.x.x

Я с разделяемыми туннелями особых бед не испытываю, единственная странность - не всегда с первого раза запрос идет напрямую, не через CF, хотя и должен. “Лечится” либо запросом traceroute (после этого начинает идти как надо) , либо отключением и подключением заново.

SeamniZ · October 18, 2025, 5:46pm

А можно подробнее, я сам конфиг сгенерил, но про -T не понял, на странице где авторизую тиму в зиро траст ввожу код из мыла, потом делаю там же console.log(document.querySelector(“meta[http-equiv=‘refresh’]”).content.split(“=”)[2]) , вбиваю в консоль на гите вывод и пишет ошибку, , что там должно быть на выходе? Или как правильно сделать зеро траст конфиг чтоб его через роутер запустить?

zxcn · October 20, 2025, 6:41pm

Возможно ли поднять warp такой схемой? Интернет через мобильный телефон → пк (Windows)→ vless → warp в режиме tun(его же подключение через socks5 или как-то иначе)

0ka · October 20, 2025, 7:34pm

Цепочкой в throne

SilentWarrior · October 20, 2025, 7:58pm

Хотел поделиться наблюдением:
В системе прописан днс от клаудов, раньше пинг до него (до любого из двух днс) был наименьшим среди всех - 16-20мс. С недавних пор (4-5 дней) пинг стал выше 60 (65-70 обычно). Сперва подумал, что запрет что-то делает, отключил, но результат не поменялся. ЧТо-то провайдер мУтит…
а вот впн подключаю и пинг до клаудов становится 35-40.

zxcn · October 20, 2025, 8:03pm

Из коробки без настройки режима tun не работает

magikgate · October 20, 2025, 8:09pm

А на деле сервера перегружены и сами клауды постоянно чет мутят.

Там ремонт, тут ремонт, там обслуживание и т д.

uwu · October 20, 2025, 8:13pm

на билайне bgp маршруты гуляют по всем серверам cf
минимальный пинг будет, если маршрут идет к мск серверу

zxcn · October 20, 2025, 9:26pm

всё таки заработало, но warp пока не алё в России, возможно получается что круг зацикливается когда создаётся ещё tun

0ka · October 20, 2025, 9:27pm

я вообще не понял ваши оба поста

zxcn · October 20, 2025, 10:44pm

Не получается с помощью throne завести warp. Пробовал как соединение в виде usb модема и через пробрасывания порта через adb

Спойлер

2025-10-20T21:59:36.666Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 6718c11d-2b27-4131-84b9-c0d1c8d28110; GetAccount
2025-10-20T21:59:36.666Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 6718c11d-2b27-4131-84b9-c0d1c8d28110; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T21:59:36.667Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: ba9ea9d9-cd2f-4107-bac6-abfdda154b39; GetOrganization
2025-10-20T21:59:36.667Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: ba9ea9d9-cd2f-4107-bac6-abfdda154b39;
2025-10-20T21:59:36.667Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: b06e1a44-1e80-448d-9695-ebf034f28357; GetSecondsUntilLocalNetworkAccessEnd
2025-10-20T21:59:36.667Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: b06e1a44-1e80-448d-9695-ebf034f28357; Uint: 0
2025-10-20T21:59:36.668Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: c0d4031c-2fb6-45ed-a672-b518f4e7c377; GetAppSettings
2025-10-20T21:59:36.668Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: f06ee769-05db-4ece-8ac3-a57982801810; GetAppSettings
2025-10-20T21:59:36.669Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 4822f117-b0a2-463c-8e46-5d32993e179d; GetAccount
2025-10-20T21:59:36.669Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 4822f117-b0a2-463c-8e46-5d32993e179d; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T21:59:36.670Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: b56c2df7-587c-45bf-bfdb-faf2de7cd003; GetAppSettings
2025-10-20T21:59:40.161Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Os { code: 11001, kind: Uncategorized, message: “Этот хост неизвестен.” }))
2025-10-20T22:00:01.373Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:00:01.373Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53
new_info=

2025-10-20T22:00:01.373Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Reconnecting on network change
2025-10-20T22:00:01.373Z INFO firewall::engine: Firewall stopped
2025-10-20T22:00:01.373Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Determining disconnected reason from connectivity state net_info=
power_state=None disconnect_reason=None
2025-10-20T22:00:01.373Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“status_change”
2025-10-20T22:00:01.373Z INFO main_loop: warp::warp_service: WARP status: Unable(NoNetwork)
2025-10-20T22:00:01.373Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Unable(NoNetwork)
2025-10-20T22:00:01.373Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Unable(NoNetwork)
2025-10-20T22:00:01.384Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: f8edd3d4-3ad9-4d4a-acf4-74e913b0bfc9; GetAppSettings
2025-10-20T22:00:01.384Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 18f3fe13-649f-4fd3-a022-0c4bbe8fcf5c; GetAppSettings
2025-10-20T22:00:01.385Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: dcddf710-29f4-4421-8619-b3b44fce753d; GetAccount
2025-10-20T22:00:01.385Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: dcddf710-29f4-4421-8619-b3b44fce753d; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T22:00:01.388Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: e912131e-57ee-45e4-b005-71cb4aae0e73; GetAppSettings
2025-10-20T22:00:01.456Z DEBUG actor_connectivity::connectivity: Routes changed:
Deleted; Interface: 58; Destination: 172.19.0.1/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 172.19.0.255/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 172.19.0.0/24; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 255.255.255.255/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 0.0.0.0/2; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 64.0.0.0/3; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 96.0.0.0/4; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 112.0.0.0/5; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 120.0.0.0/6; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 124.0.0.0/7; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 126.0.0.0/8; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 128.0.0.0/1; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 224.0.0.0/4; Next hop: 0.0.0.0;
2025-10-20T22:00:21.153Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 255.255.255.255/32; Next hop: 0.0.0.0;
2025-10-20T22:00:21.160Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 224.0.0.0/4; Next hop: 0.0.0.0;
2025-10-20T22:00:21.225Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 172.19.0.255/32; Next hop: 0.0.0.0;
2025-10-20T22:00:21.229Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 172.19.0.0/24; Next hop: 0.0.0.0;
Added; Interface: 58; Destination: 172.19.0.1/32; Next hop: 0.0.0.0;
2025-10-20T22:00:21.312Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:00:21.312Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=
new_info=DNS servers:, 172.19.0.2:53

2025-10-20T22:00:21.325Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 0.0.0.0/2; Next hop: 172.19.0.2;
2025-10-20T22:00:21.330Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:00:21.330Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=DNS servers:, 172.19.0.2:53
new_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53

2025-10-20T22:00:21.330Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Reconnecting on network change
2025-10-20T22:00:21.330Z INFO firewall::engine: Firewall stopped
2025-10-20T22:00:21.330Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53
power_state=None disconnect_reason=None
2025-10-20T22:00:21.330Z WARN main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Disconnecting, but reason is unknown
2025-10-20T22:00:21.331Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“status_change”
2025-10-20T22:00:21.331Z INFO main_loop: warp::warp_service: WARP status: Disconnected(Manual)
2025-10-20T22:00:21.331Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Disconnected(Manual)
2025-10-20T22:00:21.331Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Disconnected(Manual)
2025-10-20T22:00:21.334Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 342dc895-9669-4310-a9c9-f5489d4077a7; GetAppSettings
2025-10-20T22:00:21.334Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 28ddeaf5-c7c9-41a6-8d7f-864a991e4d1b; GetAppSettings
2025-10-20T22:00:21.335Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 5aef9f93-059b-4637-81a4-ad8d5839489d; GetAccount
2025-10-20T22:00:21.335Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 5aef9f93-059b-4637-81a4-ad8d5839489d; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T22:00:21.335Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 64.0.0.0/3; Next hop: 172.19.0.2;
2025-10-20T22:00:21.339Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 68d4a674-d3a1-4c6a-b996-7fd40195447b; GetAppSettings
2025-10-20T22:00:21.340Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 96.0.0.0/4; Next hop: 172.19.0.2;
2025-10-20T22:00:21.345Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 112.0.0.0/5; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 120.0.0.0/6; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 124.0.0.0/7; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 126.0.0.0/8; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 128.0.0.0/1; Next hop: 172.19.0.2;
2025-10-20T22:00:26.680Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:00:41.957Z DEBUG warp_api_client::client: Method: POST, Path: v0/1c1927ac-de29-41ca-a13c-062cb1d5d00b/observe_events, StructuredLogsEndpoint { device_id: “1c1927ac-de29-41ca-a13c-062cb1d5d00b”, logs: Array [Object {“event”: String(“UserToggledV0”), “toggle”: String(“off”), “warp_colo”: String(“none”), “warp_metal”: String(“none”), “version”: Number(0), “client_sample_rate”: Number(1), “app_version”: String(“2025.1.861.0”), “os”: String(“Windows”), “os_version”: String(“10.0.17763”), “timestamp”: Number(1760997576660385), “session_id”: String(“228bb29d-8cab-4399-9560-ef5a8c4eb282”)}] }
2025-10-20T22:00:42.996Z ERROR warp_api_client::client: Failed API Request endpoint=StructuredLogsEndpoint { device_id: “1c1927ac-de29-41ca-a13c-062cb1d5d00b”, logs: Array [Object {“event”: String(“UserToggledV0”), “toggle”: String(“off”), “warp_colo”: String(“none”), “warp_metal”: String(“none”), “version”: Number(0), “client_sample_rate”: Number(1), “app_version”: String(“2025.1.861.0”), “os”: String(“Windows”), “os_version”: String(“10.0.17763”), “timestamp”: Number(1760997576660385), “session_id”: String(“228bb29d-8cab-4399-9560-ef5a8c4eb282”)}] } err=ApiFailure(404, ApiErrors { errors: [ApiError { code: 10001, message: “Not Found”, other: {} }], other: {“success”: Bool(false)} })
2025-10-20T22:01:25.293Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:01:25.293Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53
new_info=

2025-10-20T22:01:25.293Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Reconnecting on network change
2025-10-20T22:01:25.293Z INFO firewall::engine: Firewall stopped
2025-10-20T22:01:25.293Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Determining disconnected reason from connectivity state net_info=
power_state=None disconnect_reason=None
2025-10-20T22:01:25.293Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“status_change”
2025-10-20T22:01:25.293Z INFO main_loop: warp::warp_service: WARP status: Unable(NoNetwork)
2025-10-20T22:01:25.293Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Unable(NoNetwork)
2025-10-20T22:01:25.293Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Unable(NoNetwork)
2025-10-20T22:01:25.300Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: a1cb5c24-b4ff-4ef3-813b-c54cdff657cb; GetAppSettings
2025-10-20T22:01:25.315Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: a2b5fac3-8407-4bf2-9a51-28964b608752; GetAppSettings
2025-10-20T22:01:25.315Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: eaea9289-73d1-4538-b352-96d90a135972; GetAccount
2025-10-20T22:01:25.316Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: eaea9289-73d1-4538-b352-96d90a135972; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T22:01:25.319Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: b71ae813-587e-4963-bad5-d9e5a4600bcf; GetAppSettings
2025-10-20T22:01:25.381Z DEBUG actor_connectivity::connectivity: Routes changed:
Deleted; Interface: 58; Destination: 172.19.0.1/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 172.19.0.255/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 172.19.0.0/24; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 255.255.255.255/32; Next hop: 0.0.0.0;
Deleted; Interface: 58; Destination: 0.0.0.0/2; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 64.0.0.0/3; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 96.0.0.0/4; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 112.0.0.0/5; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 120.0.0.0/6; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 124.0.0.0/7; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 126.0.0.0/8; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 128.0.0.0/1; Next hop: 172.19.0.2;
Deleted; Interface: 58; Destination: 224.0.0.0/4; Next hop: 0.0.0.0;
2025-10-20T22:01:27.150Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:01:44.359Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 255.255.255.255/32; Next hop: 0.0.0.0;
2025-10-20T22:01:44.367Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 224.0.0.0/4; Next hop: 0.0.0.0;
2025-10-20T22:01:44.425Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 172.19.0.255/32; Next hop: 0.0.0.0;
2025-10-20T22:01:44.446Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 172.19.0.0/24; Next hop: 0.0.0.0;
Added; Interface: 58; Destination: 172.19.0.1/32; Next hop: 0.0.0.0;
2025-10-20T22:01:44.513Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:01:44.513Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=
new_info=DNS servers:, 172.19.0.2:53

2025-10-20T22:01:44.529Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 0.0.0.0/2; Next hop: 172.19.0.2;
2025-10-20T22:01:44.533Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“main_loop_compat_rx”
2025-10-20T22:01:44.534Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service::actor_compat: Handling network status change old_info=DNS servers:, 172.19.0.2:53
new_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53

2025-10-20T22:01:44.534Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Reconnecting on network change
2025-10-20T22:01:44.534Z INFO firewall::engine: Firewall stopped
2025-10-20T22:01:44.534Z DEBUG main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Determining disconnected reason from connectivity state net_info=IPv4: [throne-tun; 172.19.0.1; Other; Interface GUID: Guid { guid: 4D1F5918-B803-12D4-F5F6-C1B87E0D628D }; Interface Index: 58; Gateway: None], DNS servers:, 172.19.0.2:53
power_state=None disconnect_reason=None
2025-10-20T22:01:44.534Z WARN main_loop:handle_update{update=NetworkInfoChanged}: warp::warp_service: Disconnecting, but reason is unknown
2025-10-20T22:01:44.534Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“status_change”
2025-10-20T22:01:44.534Z INFO main_loop: warp::warp_service: WARP status: Disconnected(Manual)
2025-10-20T22:01:44.534Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Disconnected(Manual)
2025-10-20T22:01:44.534Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Disconnected(Manual)
2025-10-20T22:01:44.537Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 01cd09c9-f29c-45f4-8ca8-0efec2f8f03b; GetAppSettings
2025-10-20T22:01:44.537Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 7fc95f19-5be6-421d-8bb8-20ca8b5556de; GetAppSettings
2025-10-20T22:01:44.538Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: a498281c-df80-4ba1-833e-e04381f34f14; GetAccount
2025-10-20T22:01:44.538Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: a498281c-df80-4ba1-833e-e04381f34f14; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T22:01:44.540Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 0d24d7d6-5d15-4b5e-9baa-61143adf522b; GetAppSettings
2025-10-20T22:01:44.541Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 64.0.0.0/3; Next hop: 172.19.0.2;
2025-10-20T22:01:44.545Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 96.0.0.0/4; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 112.0.0.0/5; Next hop: 172.19.0.2;
2025-10-20T22:01:44.549Z DEBUG actor_connectivity::connectivity: Routes changed:
Added; Interface: 58; Destination: 120.0.0.0/6; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 124.0.0.0/7; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 126.0.0.0/8; Next hop: 172.19.0.2;
Added; Interface: 58; Destination: 128.0.0.0/1; Next hop: 172.19.0.2;
2025-10-20T22:02:28.431Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:03:27.632Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:04:27.293Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:05:27.410Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:06:27.160Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:07:28.228Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:08:27.594Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:09:27.185Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:09:32.694Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: a2e0e793-806e-4c2d-bbb2-3db2483d3eb5; GetDaemonStatus
2025-10-20T22:09:32.694Z DEBUG main_loop: warp::warp_service::ipc_handlers: Sending IPC status update: Disconnected(Manual)
2025-10-20T22:09:32.694Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc Broadcast ResponseStatus: Disconnected(Manual)
2025-10-20T22:09:32.694Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: a2e0e793-806e-4c2d-bbb2-3db2483d3eb5; Success
2025-10-20T22:09:32.697Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: c6fe4184-1440-4ef3-800f-35259ac2d722; GetAppSettings
2025-10-20T22:09:32.697Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: d6127b6a-9470-4595-885d-8d2461083f93; GetAccount
2025-10-20T22:09:32.698Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: d6127b6a-9470-4595-885d-8d2461083f93; Registration: ID: 1c1927ac-de29-41ca-a13c-062cb1d5d00b; Public Key: 3059301306072a8648ce3d020106082a8648ce3d03010703420004872c9ad8cf1d942de6fc6759027d203ef0b64c97edc1087db7bf7f6dac849d34ffa4df20a4c3314047ee3106dc74c699fd5153b24a0281772391b05afcf3f034; Managed: false; Account: Free { id: AccountId(4b5faaad-f64a-4906-847a-a3cf74f4428c), license: “Vdu532q6-L6jF59z1-80WzSK95” };Alternate networks: None
2025-10-20T22:09:32.698Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: fffd3d17-58f0-4e73-adf9-b59b88c656ad; GetAppSettings
2025-10-20T22:09:32.702Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 56ed690c-29ad-4fc3-b24c-4fa9fda0708c; GetAppSettings
2025-10-20T22:09:34.516Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 4c57e36b-9ace-4651-a8b4-39217efc72aa; GetAppSettings
2025-10-20T22:09:34.537Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 609a2bc9-5559-497f-8c35-d99f7eb5ae8b; GetSupportUrl
2025-10-20T22:09:34.537Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 609a2bc9-5559-497f-8c35-d99f7eb5ae8b;
2025-10-20T22:09:36.083Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc request: 3248b22c-bf8c-41be-900f-ce7df31a819a; SetAlwaysOn(false)
2025-10-20T22:09:36.083Z INFO main_loop: structlog: event=“UserToggledV0” toggle=“off” warp_colo=“none” warp_metal=“none”
2025-10-20T22:09:36.083Z DEBUG run: warp_settings::manager: LayerManager update: UserOverrides()
2025-10-20T22:09:36.083Z DEBUG run: warp_settings::manager: UserOverrides updated: UserOverrides { version: Some(Current), always_on: Some(false), operation_mode: Some(Warp), disable_for_wifi: None, disable_for_ethernet: None, disable_for_networks: None, families: Some(Off), dns_log_until: FutureSystemTime(None), gateway_id: None, onboarding: None, organization: None, split_config: None, fallback_domains: None, proxy_port: None, disable_connectivity_checks: None, override_api_endpoint: None, override_doh_endpoint: None, override_warp_endpoint: None, override_tunnel_mtu: None, qlog_log_until: FutureSystemTime(None) }
2025-10-20T22:09:36.084Z DEBUG main_loop: warp::warp_service::ipc_handlers: Ipc response: 3248b22c-bf8c-41be-900f-ce7df31a819a; Success
2025-10-20T22:09:36.561Z INFO warp::warp_service::ipc_loop: IPC connection ended
2025-10-20T22:10:27.614Z WARN cf_ntp_client: Failed to synchronize time with NTP server err=Synchronization(IOError(Custom { kind: TimedOut, error: “Timeout while waiting for server reply” }))
2025-10-20T22:10:32.876Z INFO warp_svc::windows: Stopping warp service control_event=Stop
2025-10-20T22:10:32.876Z INFO main_loop: warp::warp_service::shutdown: Service shutting down
2025-10-20T22:10:32.876Z DEBUG main_loop: warp::warp_service: Entering main loop arm arm=“shutdown”
2025-10-20T22:10:32.876Z WARN watchdog: warp::watchdog: Watchdog reports that daemon has disconnected watchdog_name=“main loop”
2025-10-20T22:10:32.877Z INFO warp::warp_service: Dropping WarpService
2025-10-20T22:10:32.877Z INFO warp_svc::windows: Warp service stopped
2025-10-20T22:10:32.879Z DEBUG network_info::win::change_notifier: Shutting down HkeyHandle driver
2025-10-20T22:10:32.879Z DEBUG network_info::win::change_notifier: Shutting down HkeyHandle driver

0ka · October 20, 2025, 10:52pm

В логе явно не трон а что-то другое. Я предлагал вам:

Конфиг влесс в трон
Конфиг варп в трон
Цепочка варп через влесс в трон ()
И затем tun mode

Телефон подключается через режим юсб модем или точка доступа

Вообще варп через влесс это не очень эффективно, лучше через ss или hysteria

zxcn · October 21, 2025, 12:24am

Скрин

По идеи почти достиг своих целей, заработала cs 1.6 теперь надо игру Planetside 2 завести через варп

А можно по подробнее как варп через влесс и в троне?

Sudo · October 21, 2025, 6:21am

Вы могли намного проще пропустить игру через прокси. Если вы именно этого добиваетесь. Есть Netch и Proxifyre где можно сделать трон> socks5 на 127.0.0.1 > Netch > ваша игра. К сожалению знаю один баг или проблему, не знаю с чем связана, пинг скачет например в недавнем времени пробовал таким образом пустить battlefield 6, вроде бы я где-то слышал что это из-за взаимодействия netch с виндой

zxcn · October 21, 2025, 5:55pm

cs 1.6 нужен udp, с proxifier не прокатывает, у меня пока надежда вся на Throne