[GH-ISSUE #2317] MacOs client stopped to work with latest Cloudflare WARP client (2026.1.150.0) #1024

New issue

Open

opened 2026-10-13 20:33:02 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 20:33:02 +00:00

Owner

Originally created by @Noksa on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2317

Describe the bug
Once we upgraded WARP to its current latest release (2026.1.150.0) it seems like when we enable AmneziaVPN before WARP, WARP can't connect anymore.

At the same time, if we use AmneziaWG application, it works as expected - WARP connects and works.

To Reproduce
Steps to reproduce the behavior:

Enable AmneziaVPN tunnel
Try to enable WARP tunnel

Expected behavior
It works as before with previous WARP releases.

But currently we get such errors in WARP logs:

Bound edge socket to interface if_index=14 _destination=162.159.193.3:4500
Happy eyeballs to 162.159.193.3:4500 failed: Connect(Os { code: 51, kind: NetworkUnreachable, message: “Network is unreachable” })

Looks like warp tries to bind on en0 instead of utun4 which is actually interface used by AmneziaVPN

Difference between resolvers configs:
AmneziaVPN modifies the resolver 1 which is still bound to en0:

DNS configuration (for scoped queries)

resolver #1
  search domain[0] : lan
  nameserver[0] : 10.101.0.1
  nameserver[1] : 8.8.8.8
  if_index : 14 (en0)
  flags    : Scoped, Request A records
  reach    : 0x00000000 (Not Reachable)

AmneziaWG creates the second which is bound to utun4:

DNS configuration (for scoped queries)

resolver #1
  nameserver[0] : 192.168.10.1
  if_index : 14 (en0)
  flags    : Scoped, Request A records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

resolver #2
  nameserver[0] : 10.101.0.1
  nameserver[1] : 8.8.8.8
  if_index : 22 (utun4)
  flags    : Scoped, Request A records
  reach    : 0x00000002 (Reachable)

So, when we use AmneziaWG app - WARP binds to utun4 interface instead of en0 and works as expected, logs with working behavior:

2026-03-06T09:54:03.349Z DEBUG main_loop:connect_single_protocol{protocol="wireguard"}:happy_eyeballs_with_retry{protocol="wireguard" pq=true}: warp_connection::socket_configurator: Bound edge socket to interface if_index=22 _destination=162.159.193.3:500
2026-03-06T09:54:03.349Z DEBUG main_loop:connect_single_protocol{protocol="wireguard"}:happy_eyeballs_with_retry{protocol="wireguard" pq=true}: warp_edge::happy_eyeballs: Start racer 10.100.4.163:63249 ---> 162.159.193.3:500

Looks like when we enable VPN via AmneziaVPN app, it doesn't support new WARP app releases anymore.

Tested on AmneziaVPN 4.8.12.9 with both awg 1.0 and awg 2.0 protocols.

Originally created by @Noksa on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2317 **Describe the bug** Once we upgraded `WARP` to its current latest release **(2026.1.150.0)** it seems like when we enable `AmneziaVPN` before `WARP`, `WARP` can't connect anymore. At the same time, if we use `AmneziaWG` application, it works as expected - `WARP` connects and works. **To Reproduce** Steps to reproduce the behavior: 1. Enable `AmneziaVPN` tunnel 2. Try to enable `WARP` tunnel **Expected behavior** It works as before with previous `WARP` releases. But currently we get such errors in WARP logs: ```shell Bound edge socket to interface if_index=14 _destination=162.159.193.3:4500 Happy eyeballs to 162.159.193.3:4500 failed: Connect(Os { code: 51, kind: NetworkUnreachable, message: “Network is unreachable” }) ``` Looks like warp tries to bind on **en0** instead of **utun4** which is actually interface used by `AmneziaVPN` Difference between resolvers configs: **AmneziaVPN** modifies the resolver 1 which is still bound to **en0**: ```shell DNS configuration (for scoped queries) resolver #1 search domain[0] : lan nameserver[0] : 10.101.0.1 nameserver[1] : 8.8.8.8 if_index : 14 (en0) flags : Scoped, Request A records reach : 0x00000000 (Not Reachable) ``` **AmneziaWG** creates the second which is bound to **utun4**: ```shell DNS configuration (for scoped queries) resolver #1 nameserver[0] : 192.168.10.1 if_index : 14 (en0) flags : Scoped, Request A records reach : 0x00020002 (Reachable,Directly Reachable Address) resolver #2 nameserver[0] : 10.101.0.1 nameserver[1] : 8.8.8.8 if_index : 22 (utun4) flags : Scoped, Request A records reach : 0x00000002 (Reachable) ``` So, when we use `AmneziaWG` app - `WARP` binds to `utun4` interface instead of `en0` and works as expected, logs with working behavior: ```shell 2026-03-06T09:54:03.349Z DEBUG main_loop:connect_single_protocol{protocol="wireguard"}:happy_eyeballs_with_retry{protocol="wireguard" pq=true}: warp_connection::socket_configurator: Bound edge socket to interface if_index=22 _destination=162.159.193.3:500 2026-03-06T09:54:03.349Z DEBUG main_loop:connect_single_protocol{protocol="wireguard"}:happy_eyeballs_with_retry{protocol="wireguard" pq=true}: warp_edge::happy_eyeballs: Start racer 10.100.4.163:63249 ---> 162.159.193.3:500 ``` Looks like when we enable VPN via `AmneziaVPN` app, it doesn't support new `WARP` app releases anymore. Tested on `AmneziaVPN 4.8.12.9` with both awg 1.0 and awg 2.0 protocols.

bsakaguchi referenced this issue

2026-10-13 21:19:42 +00:00

[PR #1024] [MERGED] Android qt 6.7 #2208