Astrowarp wan pinning

It would be good if wan pinning could be added based on destination address or port/protocol so that astrowarp tunnels it to the exit node but doesn’t try to bond/balance it (so just tunnel it via wireguard or some other protocol)

This would allow you to do things like keep the same exit node IP as your bonded traffic but avoid some of the latency/jitter issues that may result from bonding 2 different connection types.

For instance say you have a slow DSL line and a fast 5G connection it might be advantageous to bond TCP traffic so a game download is fast but pin UDP traffic to the DSL for its more consistent latency during gameplay

The reason the UDP traffic would still need to use the exit node is so it has the same source IPs as the TCP traffic (the game login traffic will likely be TCP based)

1 Like

You mean allow users to define their own traffic policies?

Yes, the default should be to let the system handle it, but occasionally you may want to override this for whatever reason.

It's less of an issue if the WAN's are balanced in their capability, but once cellular/wi-fi.etc gets involved that's going to be less and less likely.

1 Like