No warp. might be my setup!

[JustWilder]

Hey! I wish you could shed some light on a little issue i have.

So Im connected to cloudflares VPN using Wireguard on openwrt and im using 1.1.1.1 as DNS. I do get my internet traffic thru this connection but i get no warp and checking it on https://1.1.1.1/help it says

Connected to 1.1.1.1 | Yes
Using DNS over HTTPS (DoH) | Yes
Using DNS over TLS (DoT) | No
Using DNS over WARP | No
AS Name | Cloudflare
AS Number | 13335
Cloudflare Data Center | HKG

But if I use other DNS addresses like 8.8.8.8 i get this instead

Connected to 1.1.1.1 | No
Using DNS over HTTPS (DoH) | No
Using DNS over TLS (DoT) | No
Using DNS over WARP | Yes
AS Name | Goolge
AS Number | 15169
Cloudflare Data Center | HKG

Any idea whats going on here?

[LuuOW]

Hey everyone, for all of those who's having trouble, i've found a solution, just change the endpoint in the conf file like this:

[Interface]
PrivateKey = your_private_key
Address = 172.16.0.2/32
Address = fd01:5ca1:ab1e:85e0:b48d:db14:f528:3a81/128
DNS = 1.1.1.1
MTU = 1280
[Peer]
PublicKey = your_public_key
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = engage.cloudflareclient.com:2408 <=============== THIS IS WHAT YOU HAVE TO CHANGE

just from "engage.cloudflareclient.com" DO NOT change the port, to other dns client, i've been using duckdns
So now, my client looks like this:

[Interface]
PrivateKey = your_private_key
Address = 172.16.0.2/32
Address = fd01:5ca1:ab1e:85e0:b48d:db14:f528:3a81/128
DNS = 1.1.1.1
MTU = 1280
[Peer]
PublicKey = your_public_key
AllowedIPs = 0.0.0.0/0
AllowedIPs = ::/0
Endpoint = place_your_dns_here:2408 <====== this is what it changes, not the port, again

These are the ips of engage.cloudflareclient.com, so your dns must refer to this ips:

Lookup IPv4 Address: 162.159.192.1
Lookup IPv6 Address: 2606:4700:d0::a29f:c001

I hope you can solve your problems.

[RaXorX]

Hello, I just tried this too. Changing the dns address does change the DNS over HTTPS to WARP.
At first when I didn't know about that link, I thought it was connecting to warp and was looking for a way to change it to DoH. However, after testing it out I saw that I have DoH too. @LuuOW it is already set to engage.cloudflareclient.com:2408 so that answer does not solve anything. Also, don't think the 8.8.8.8 DNS OP was talking about goes over there. It goes over under [Interface] DNS = place_your_dns_here

[ViRb3]

Duplicate of #85, please continue conversation there.

[ViRb3]

Upon close look, this issue seems to be unrelated. What exactly is the problem here? If your IP address changes, you are definitely connected to Cloudflare WARP, no matter what any check tells you. Note that unlike the official WARP client, which is a custom VPN with extra DNS features, wgcf generates a standard profile for WireGuard, which only supports standard DNS and not DNS over HTTPS, TLS, or WARP, so this setting will always be "No". If your IP changes, then wgcf works as expected. Making the DNS work like the official client is out of scope for this project.

[docsapro]

Hi,
could it be related to https://community.cloudflare.com/t/1-1-1-1-dns-not-responding-inside-warp-from-china/339464/4 ?