Pangolin, the open-source tunneled reverse proxy and zero-trust networking platform built around WireGuard, has released version 1.24, with the headline addition of Exit Nodes.
Until now, Pangolin operated as a split-tunnel solution, meaning only traffic to Pangolin-protected resources passed through the tunnel, while regular internet traffic used the device’s normal connection.
With Pangolin 1.24, users can create a private resource as an Exit Node and associate it with one or more sites. Once a client selects it, all internet traffic routes through that site using the default IPv4 and IPv6 routes, giving Pangolin full-tunnel VPN functionality when needed.
When multiple sites attach to an Exit Node, Pangolin automatically chooses between them based on latency, throughput, and availability. Exit Nodes support TCP, UDP, and ICMP traffic and are available on Windows, macOS, iOS, Android, and the Pangolin CLI.
Another notable addition, especially for Linux users, is Subnet Router support. A Linux machine running the Pangolin client can now advertise an entire subnet, letting devices on that network access Pangolin resources without installing the client on each device.
Moreover, on macOS and iOS, the apps use Apple’s Network Extension API to bring up the tunnel automatically when a suitable network connection is available. Users can configure automatic connection separately for Ethernet, Wi-Fi, and, on iOS, cellular connections. Wi-Fi rules can be limited to selected networks or exclude specific SSIDs.
macOS additionally gains a Start at Login option. Windows receives similar behavior through Start at Login and Connect at Start settings, while Android users can rely on the platform’s Always-on VPN functionality.
The Windows and macOS clients have also received interface work. Windows 0.15 introduces redesigned preferences and system tray interfaces intended to more closely match the macOS client.
On macOS, the menu bar interface no longer closes when users connect, switch accounts, change organizations, or select another Exit Node, making multiple consecutive changes easier. Plus, connection details are more accessible, including information about connected sites and whether a connection is direct or relayed.
Finally, the preferences Status page across supported platforms now provides a formatted view of site information previously mainly exposed through JSON output.
For more details, see the announcement.
