You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,7 @@
32
32
-[Terminal-based client](#terminal-based-client)
33
33
-[Common examples](#common-examples)
34
34
-[Upgrading](#upgrading)
35
+
-[Platform notes & known limitations](#platform-notes--known-limitations)
35
36
-[Contributing](#contributing)
36
37
-[License](#license)
37
38
@@ -196,8 +197,6 @@ Open the web UI at http://admin.awl (or the Android app). On the Status / Overvi
196
197
197
198
To try the public tester: enter `12D3KooWJMUjt9b5T1umzgzjLv5yG2ViuuF4qjmN65tsRXZGS1p8` as peer id, name it `awl-tester`, save. After a few seconds it will appear in your peer list. Open http://awl-tester.awl/ — you should see a network speed-test page.
198
199
199
-
> `.awl` DNS is not yet available on Android ([#17](https://github.com/anywherelan/awl/issues/17)); on Android you access peers by IP.
200
-
201
200
When someone invites you, a notification will appear; accept or block in the admin UI.
202
201
203
202
### Server
@@ -496,6 +495,24 @@ systemctl restart awl
496
495
497
496
As an alternative on desktop or server: download the new build from the [releases page](https://github.com/anywherelan/awl/releases) and replace the files manually.
498
497
498
+
## Platform notes & known limitations
499
+
500
+
### `.awl` name resolution
501
+
502
+
`.awl` names resolve on every platform, but the mechanism differs:
503
+
504
+
-**Desktop (Linux / Windows / macOS):** awl runs a local resolver and registers it with the OS. Where the OS supports split-DNS only the `.awl` zone is captured; the rest of your DNS is left untouched, so LAN names keep working.
505
+
-**Android:** the app resolves `.awl` inside the tunnel — `.awl` is answered locally, everything else is forwarded to the configured upstream resolver (`1.1.1.1` by default, `dns.upstreamDNSAddress` in the config). This has a few consequences:
506
+
-**Private DNS in strict mode** (a hostname set under Android's *Private DNS* setting) bypasses the VPN's DNS entirely, so `.awl` names won't resolve. The default *Automatic* mode works fine.
507
+
- While DNS is enabled, all queries go to the configured upstream instead of your network's own resolver, so LAN-only names handed out by your router (e.g. `printer.lan`) won't resolve.
508
+
-`admin.awl` is not reachable on Android — use the app's own UI instead.
509
+
-`dns.disableDNS: true` in the config turns awl's DNS handling off entirely: `.awl` stops resolving and queries go straight to the system resolver again.
510
+
511
+
### Other limitations
512
+
513
+
-**IPv6 inside the tunnel is not supported** — IPv6 packets are dropped, only IPv4 is carried.
514
+
-**Serving as a VPN gateway / exit node** is not available on every platform — see the [support table](#vpn-gateway-full-tunnel-exit-node).
515
+
499
516
# Contributing
500
517
501
518
Contributions to this repository are very welcome.
0 commit comments