Our router has 2 WAN interfaces with 2 IPs, but clients always connecting use one. As far as I understand, in the Pritunl server settings (set by the public address in either the top right settings or in the host settings for enterprise subscriptions) specify only one.
By default public address is blank to automatically detect the servers public address.
How can it be possible to use the 2nd WAN interface? Only by additionally installing a second Pritunl or setting up a software like Traefik or similar behind the router?
Because we want so that some clients connect via WAN1, the rest of the clients via WAN2. At this time it’s not convenient to edit user profile configs manually…
The server isn’t designed to support that, if it’s an enterprise subscription a blank host can be created by temporarily removing /var/lib/pritunl/pritunl.uuid and running sudo systemctl restart pritunl. This will create a second host, the public address of that host can be set to the second IP address. Then both hosts can be attached to the server. Even though the second host is offline the client will still attempt both IP addresses in a random order. This would not result in additional billing for the offline host.
Please clarify, finally must be exists only one file pritunl.uuid (new created automatically)? Pritunl client can’t connect although 2nd host added successfully and we set up 2nd IP explicitly as Public address. Now in pritunl client log:
2024-11-06 17:37:49 TCP/UDP: Preserving recently used remote address: [AF_INET]IP_WAN1:port
2024-11-06 17:37:49 UDPv4 link local: (not bound)
2024-11-06 17:37:49 UDPv4 link remote: [AF_INET]IP_WAN1:port
2024-11-06 17:37:53 Server poll timeout, restarting
2024-11-06 17:37:53 SIGUSR1[soft,server_poll] received, process restarting
type or paste code here
The uuid should be restored to the original value after the second host is created. If the host isn’t able to connect to the IP address then it is an issue with that network configuration. Check the remote values in the profile paths listed in the client debugging documentation.