I see your on vers6 software however I will provide the current ver7 format because that will work on both and when you transition to vers 7.5 stable for example... it should be seamless as far as routing goes...............
In general you really need to simplify all parts of your config.
For example your interface lists, forget discover and mactel, they are very old in approach (same with any discussion of slave and local, not used anymore) and simply use WAN, LAN, and Management.
All smart devices get their IP address on the Managmenet LAN or vlan, and the admin is normally connected on this network.
IF you have a trusted subnet, then put this single subnet on the management interface list.
In any case...........
Its very hard to discern what you are doing and what the routing tables should look like.
It is also unclear why you are mangling ISP1 and ISP 2 traffic at this point. Mangling is normally not required for simple failover!!!
Will assume that ether1 is the Primary WAN and ether3? is the secondary failover WAN..
(1) Remove the first line here in yellow because the pppoe settings are all done under that menu and not this menu!!
/ip dhcp-client
add add-default-route=no comment="default configuration" disabled=no interface=ether1-gateway
add default-route-distance=5 interface=ether3-slave-local
(2) It is not clear to me what the first two routes are, but will assume they have nothing to do with the two ISP connections and can be ignored. ????
/ip route
add distance=4 gateway=**** routing-mark=Out_Ether4
add distance=3 gateway=****
(3) Since you have the default routes selected for both pppoe and whatever is on ether3, its hard to provide advice as they are not normally visible on a config, but I will play as if we were doing it manually and then you can adjust accordingly.
/ip route
add check-gateway=ping comment=Primary ISP distance=1 dst-address=0.0.0.0/0 gateway=Primary-gatewayIP (table=main)
add comment=SecondaryISP distance=2 dst-address=0.0.0.0/0 gateway=Secondary-gatewayIP (table=main)
In this setup all traffic will go to ISP1 and if its not available will switch to ISP2 and when ISP1 comes back on line will revert back to ISP2.
NOT
a) dst: 0.0.0.0 gateway: ISP1 IP Address and check gateway: ping
b) dst: 0.0.0.0 gateway: ISP2 IP Address and check gateway: ping
3) dst: 0.0.0.0 gateway: ISP1 & ISP2 IP Address and check gateway: ping
You only need to check ping on the primary and why do you have the third entry (note that on all three the distances are missing).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
What other requirements do you have that are not clearly stated regarding what ISP users should be going out on???
Hi,
Thank you for your effort, I appreciate it!
Btw, for your additional information, here's our network diagram image below.
ITA Router - this is a isp company to provide connection to our stores. (No internet, just a local connection or VPN)
PBX - Connected to Office in other Country (but not included in the image; because its only connected to switch)
Red drawing - I will put the connection in eth5 to obtain a internet from the other office via Access Point.
Any question, please let me know.
Thanks