Hello Tomas,
we appreciate your inquiry.
This is indeed a tricky situation: Kindly understand that there isn't a way for PRTG to "choose" it's gateway, the same also applies when issuing a normal ping from command-line. The default gateway will be used.
The recommended solution is indeed to create two distinct devices within PRTG with different addresses (You can name the devices "MyDevice via ISP A" and "MyDevice via ISP B" to make it easier to understand.)
Regardless of that, the actually Policy Based Routing (or NATting) has to be performed by your Router/Firewall.
There is one workaround I can think of which would be using an Port Sensor within PRTG instead, then create your PBR to point two distinct ports to the same port on the remove device using each available gateway. That way you can keep a single device within PRTG and have one sensor for each gateway.
SourceIP | SourcePort | DestinationIP | DestinationPort | Gateway |
LocalIP | 8001 | RemoteIP | 80 | Gateway A |
LocalIP | 8002 | RemoteIP | 80 | Gateway B |
If you don't care about using custom Sensors, you could also create an EXE/Script Advanced Sensor to ping both devices (using powershell test-connection or similar) and supply both destination IP's as parameter within the script instead of using the device's address. This solution requires coding and is less performatic than the port sensors solution, but should also work.
Kindly note that we can't provided detailed assistance regarding the configuration of router router/firewall/device.
Best Regards,
Add comment