An alternate route is already configured, but an authorized user should not need router-panel access for every enable/disable request. MikroTik PBR Client sends the request from Windows with one button; prepared router rules perform the actual change. This article covers version 1.0.2, trigger-IP settings and the distinction between a submitted request and the real routing result.

بنر MikroTik PBR Client با دکمه روشن و خاموش و آدرس‌های کنترل مسیر
A simple interface for sending route control requests to MikroTik

Introduction and use cases

PBR stands for Policy-Based Routing. The router selects a route according to configured rules. This application only sends a specific request to the router; MikroTik decides which route to use and applies the policy.

Use this application when an alternate route is already configured and authorized users need to request it. Its on/off button replaces manual Ping commands. Connection speed and security still depend on network design, route health and router policy.

Router prerequisites

Before running the application, the administrator must configure trigger handling and the corresponding route changes on MikroTik. Installing the Windows application does not create those rules or configure router routes. Sending requests does not require a RouterOS username or password.

Coordinate trigger addresses and policy handling with the network administrator before use. The client must reach the destinations expected by the router rules, which need to be configured for your topology. Without those rules, pressing the button cannot change routing.

How the application works

The application sends an ICMP echo, or ping, to a trigger destination so router rules can recognize the request. Defaults are 10.10.10.10 for enable and 11.11.11.11 for disable. These are trigger addresses, not VPN-server addresses, and the administrator must control their use in the network.

The application does not create a VPN or tunnel. It does not read router state at startup and initially displays an unknown status. The initial display therefore cannot confirm whether the route is enabled. The interface reports request status; verify the actual routing result separately.

Do not translate a ping result into routing state. A reply proves only that the trigger answered, not that routing changed or Internet access works; timeout does not necessarily mean the request missed the router. The administrator needs to define an independent result check so users can verify policy application after submitting a request.

Installation and everyday use

  1. Run the supplied installer on 64-bit Windows. This installs only the client application; coordinate router prerequisites and trigger addresses with the network administrator before sending the first request.
  2. Open the installed application and remember that the initial route status is unknown.
  3. Use the main button to request the prepared alternative route and check the request status.
  4. Send the off request to disable the route. Use Send disconnect when you need to repeat the disconnect request.

The application does not send continuous Ping requests. Closing its window does not automatically send a disable request. Send the off request before leaving and verify the result using the method approved by your administrator.

Changing trigger IP addresses

Change trigger addresses in the installed settings file without editing code or rebuilding the application. Obtain the correct addresses from your administrator first. Changing only the Windows settings without coordinating router rules will not send the request to the intended destination.

  1. Open PBR Client Settings from the Start menu.
  2. Edit EnableTriggerIp and DisableTriggerIp.
  3. Save the file, close the application, and start it again.
  4. Update the router trigger rules to match the new addresses.

Installed settings file path:

CODE
%LOCALAPPDATA%\Programs\MikroTikPBRClient\appsettings.json

The example below shows only the two trigger address keys. Edit those values in the existing file and preserve all other settings. Do not replace the whole file with this example.

CODE
{
  "EnableTriggerIp": "10.10.10.10",
  "DisableTriggerIp": "11.11.11.11"
}

After saving, check both IP values and JSON structure; missing punctuation can prevent configuration loading. Fully close and reopen the application so it reads the new file. An existing window does not establish that updated values are in use; verify the request outcome separately through the router or the agreed test.

Release notes and trigger addresses

The portable application has been run and confirmed on Windows. Before distributing MSI version 1.0.2, test installation, repair and removal on your own test device; those installer paths remain untested.

Control trigger addresses through network design and router rules. In particular, 11.11.11.11 is a public address: do not use it as an ordinary Internet destination without the required router configuration. Coordinate new addresses with the administrator so trigger requests are not confused with normal traffic.

Security Considerations

Production safety

  • Do not expose management interfaces or databases to the public Internet.
  • Store passwords, tokens, and private keys outside the article and source repository.
  • Patch dependencies, restrict administrative access, and retain audit logs.

Troubleshooting

SymptomCause / CheckResolution
Service does not startCheck service status, logs, ports, permissions, and configuration syntax.Fix the reported dependency or syntax error, then restart and verify health checks.
Clients cannot connectValidate DNS, routing, firewall policy, TLS, and listening address from both endpoints.Allow only the required source and destination, reload safely, and retest with a controlled client.
Change caused an outageCompare the change with the last known-good version and inspect audit and application logs.Rollback the smallest possible change, restore service, then document the root cause and prevention.

Best Practices

  • Version-control configuration and review changes.
  • Use least privilege and explicit allow-lists.
  • Automate repeatable checks and monitor the expected state.
  • Test upgrades and restores before production rollout.

Conclusion

A reliable implementation of MikroTik PBR Client is more than a successful first run. Keep the configuration documented, observable, recoverable, and aligned with the team's change-management process.

Frequently asked questions

Is this application a VPN?

No. It only sends Ping requests to trigger addresses. Tunnels, routes, and policies must already be configured in the network.

Does a Ping reply prove the route changed?

No. It only confirms a reply from the trigger destination. Verify routing and Internet access separately. A timeout does not rule out the request reaching the router.

Do I need to rebuild the application to change IP addresses?

No. Change the two trigger values in the settings file, preserve the other settings, and restart the application. Coordinate the router addresses too.

Does closing the window disable the route?

No. Exiting does not send an off request. Use the relevant control and Send disconnect to send or repeat the disable request.

Official References

Download the 64-bit Windows installer, version 1.0.2

Download version 1.0.2

The download is a 64-bit Windows MSI installer with the required .NET files included. Check version and system architecture before installing, and test compatibility on the Windows release intended for rollout.

Version: 1.0.2 · Architecture: x64 · File format: MSI

Share

Meet AJInfrastructure & DevOps
Loading…