Hi Team,
I’ve encountered several projects where it would be beneficial if Peplink units allowed for WAN selection when creating InTouch sessions with the routers. Currently, my workaround involves creating an OpenVPN profile and selecting the WAN for the VPN connection.
Hey Fletcher,
Have you considered doing it using outbound policies?
This could be configured via IC2, but I see your suggestion would be more of an “on demand” sort of level rather than permanently set?
I think there could be merit for this, even for IC2 remote access in case of a bad WAN connection. Maybe even allow connection using a 2nd, 3rd or 4th Priority WAN interface.
This could also allow us access in case a device used a WAN without Health Check but still remains online, but a 2nd priority WAN does go online.
@Giedrius @AgentAdam Thoughts?
Would be interesting to hear more about the use case.
I am not sure an outbound police would necessarily achieve all thats needed here.
It would be very nice a clean to choose a WAN port to be used when setting up and editing IT in IC2
In addition to this.
We could really use a gui for wan ordering in ic2 , even if it doesn’t let us “accidently” disable them, just changing the order.
We have resorted to using bulk-config with a changed wan order, but it’s not the same.
Absolutely love this idea Jonathan - heck, even have a default time-out in case of disconnection.
Auto-fallback after 60-120 seconds if not working or not going online.
Hi Adam,
A client of mine has an office in co-working facility. This co-working facility manages the WAN and firewall to this office and subnets out to the different businesses within the facility.
The objective is to RDP into local machines behind the co-working facilities firewall for remote users. The co-working IT manager are reluctant to open port 3389 for RDP which I can understand from a security perspective and VPN packets are drop from NAT on the firewall and port forwarding or NAT-T is not allowed. However, if we added a cellular WAN to the Peplink router and select the RDP InTouch session are created over the Cellular WAN rather than the WAN supply from the co-working facility this will give us a bit of more control. We are currently using both OpenVPN and Fast Reverse Proxying to build a solution.