I have configured the router for dual WAN PCC. It works fine. But since I have done this, redirecting to a suspension page of our CRM on port 81 does not work anymore.
It used to work fine when there was only one WAN connected to the router.

- clients are in 192.168.0.0/22
- my CRM also belongs to this subnet. It is on 192.168.0.1. The server is on port 3 of the router. The LAN is Bridged port 3 to port 9.


When a client is redirected to 192.168.0.1:81 by rules in the router, the client browser does not react anymore.
The response is apparently not routed by the router and the client rejects it.

How can I 'force' the communication from any LAN IP with 192.168.0.1 to go through the router on port 3?
Is there a mangle rule that will do so?

Or do I simply take port 3 out of the LAN bridge and add an address 192.168.0.1/24 on that port 3? That is the only IP address that is connected to port 3.
But I don't know if I can do that if I already have an address in the address list (for port 4 to 9) 192.168.0.0/22. All clients are connected to those ports.
Wouldn't this configuration conflict and look for all clients in 192.168.0.1/24 on port 3?

Or is it really that simple that I click 'Auto Isolate' on port 3 in the bridge? Is that what 'Auto Isolate' does?

Auto-Isolate is specifically for Spanning Tree, so this would not do you anything at all.

You could write a mangle rule specifically targeting a dst address from a src address and route it in another routing table. Even including the specific port if needed, so that only traffic sourced from 192.168.0.1 destined for an IP on TCP port 81, routes to a specific interface separated from the main routing table.