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
Route-staleness monitor (routes_linux.go): subscribe to netlink route changes
and re-sync the tableID exemption copies (v4 and v6) with the live host
default(s) on DHCP renew / Wi-Fi<->Ethernet roam / new RA. Debounced (500ms)
reconcile diffs by route key; it never touches the TUN default or the IPv6
unreachable fence, so there is no leak window even mid-uplink-change. The
monitor re-subscribes with backoff on a mid-session netlink socket death, using
a per-subscription cancel channel so a dead socket + its watcher goroutine are
released immediately rather than leaked. RouteState gains a mutex + monitor
lifecycle; teardown stops the monitor first. Adds vpn_hostnet integration tests
(v4 + v6 reconcile) with goleak checks.
Drop the conf lock on the inbound hot path: writeInboundBatch takes *VpnPeer and
reads vp.weAllowUsingAsExitNode (atomic, synced by RefreshPeersList) instead of a
per-batch conf.GetPeer RLock + peer.ID.String() alloc. Forward-without-permission
is still dropped before the TUN write.
Gateway connectivity event: new awlevent.VPNGatewayConnectivityChanged, emitted
from Tunnel on gateway-peer connect/disconnect with edge dedup and an initial
state on enable. awl-tray shows a desktop notification on up/down.
Refuse removing a peer that is the active VPN gateway (409) instead of
black-holing all non-local traffic; the user must disable the gateway first.
Copy file name to clipboardExpand all lines: README.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -259,8 +259,6 @@ On macOS and Windows awl currently refuses to start with VPN gateway enabled.
259
259
> -**Dual-stack (IPv4 + IPv6):** everything automatically uses IPv4 through the tunnel.
260
260
> -**IPv6-only network:** you'll have no internet connectivity until you turn the gateway off.
261
261
262
-
> **Linux: host network changes mid-session aren't tracked.** If the host switches network (new Wi-Fi, Ethernet or cellular connection) while the gateway is on, restart awl. This will be fixed in a future release.
263
-
264
262
### Serve as an exit node
265
263
266
264
This lets your other devices route their internet traffic out through this one. It is **off by default** — see [Why serving as an exit node is opt-in](#why-serving-as-an-exit-node-is-opt-in) below. Two things need to be set: turn the gateway service on, then allow each specific device to use it. Serving as an exit node is Linux-only (see the status table above).
0 commit comments