I have the following setup working - and it’s great!
ISP1 gateway - 10.0.0.1, ISP2 gateway - 10.0.1.1
ISP1 --> 10.0.0.2 \
prio 1 | --> Mikrotik (192.168.0.0/24) NATTED
| (192.168.0.9 is a WEB SERVER - use dst-nat
ISP2 --> 10.0.1.2 / forward port 80 to 192.168.0.9)
prio 2
All internal LAN machines work AOk! ISP1 is always used unless service goes down and ISP2 then kicks in. This is the way I want it.
The web server domain points to 10.0.0.1 (for example sake) so when they type that in anywhere in the world it goes to the mikrotik and it port forwards the port 80 request to 192.168.0.9 perfectly.
Now the problem is if I have a machine on the public IP block from ISP2 say 10.0.1.3 and I try to goto http://10.0.0.1 it does NOT forward to 192.168.0.9. Normally the traffic SHOULD route out through ISP2 through the internet and then back through ISP1 to get to the web server however for some reason it is short circuited (though no static routing has been declared!!).
If I am at 10.0.1.3 and ping 10.0.0.1 it shows up in 2ms.. I want that ping to go out to the internet through the ISP2 gateway 10.0.1.1 and then back through ISP1 to 10.0.0.1. Anyone have any ideas why my 10.0.1.1 gateway tells 10.0.1.3 that 10.0.0.1 is right next door and to not go out onto the net?? confusing.. there are no special routing tables that I’ve created to make that short circuit so I don’t know where it’s coming from.
Hopefully that made some sense!
cheers
Paul