I created some config - test it !

Code: Select all

/ip dhcp-client
add add-default-route=no dhcp-options=hostname,clientid disabled=no interface=ether1 use-peer-dns=no use-peer-ntp=no
add add-default-route=no dhcp-options=hostname,clientid disabled=no interface=ether11 use-peer-dns=no use-peer-ntp=no
/ip address
add address=192.168.0.1/24 interface=bridge1 network=192.168.0.0
add address=10.0.0.1/24 interface=bridge1 network=10.0.0.0
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
add action=masquerade chain=srcnat out-interface=ether11
/interface list add name=LANs
/interface list member 
add interface=bridge1 list=LANs
add interface=bridge2 list=LANs 
/ip firewall mangle
add action=mark-connection chain=prerouting connection-state=new in-interface=ether1 new-connection-mark=ether1_conn
add action=mark-connection chain=prerouting connection-state=new in-interface=ether11 new-connection-mark=ether11_conn
add action=mark-routing chain=output connection-mark=ether1_conn new-routing-mark=ISP1
add action=mark-routing chain=output connection-mark=ether11_conn new-routing-mark=ISP2
add action=mark-connection chain=prerouting connection-state=new dst-address-type=!local in-interface-list=LANs new-connection-mark=ether1_conn per-connection-classifier=both-ports:2/0
add action=mark-connection chain=prerouting connection-state=new dst-address-type=!local in-interface-list=LANs new-connection-mark=ether11_conn per-connection-classifier=both-ports:2/1
add action=mark-routing chain=prerouting connection-mark=ether1_conn in-interface-list=LANs new-routing-mark=ISP1
add action=mark-routing chain=prerouting connection-mark=ether11_conn in-interface-list=LANs new-routing-mark=ISP2
/ip route
add dst-address=1.1.1.1 gateway=192.168.100.1 scope=10 comment=WAN-ISP1
add dst-address=8.8.8.8 gateway=192.168.200.1 scope=10 comment=WAN-ISP2
add distance=1 gateway=1.1.1.1 routing-mark=ISP1 check-gateway=ping
add distance=2 gateway=8.8.8.8 routing-mark=ISP1 check-gateway=ping
add distance=1 gateway=8.8.8.8 routing-mark=ISP2 check-gateway=ping
add distance=2 gateway=1.1.1.1 routing-mark=ISP2 check-gateway=ping
/system script
add dont-require-permissions=no name=CheckGW owner=ico policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=":\
    global newgw1 [/ip dhcp-client get [find interface=\"ether1\" ] gateway ]\
    \r\
    \n:global activegw1 [/ip route get [/ip route find comment=\"WAN-ISP1\"] g\
    ateway ]\r\
    \n:if (\$newgw1 != \$activegw1) do={\r\
    \n/ip route set [find comment=\"Ether1-ISP1\"] gateway=\$newgw1\r\
    \n}\r\
    \n:global newgw2 [/ip dhcp-client get [find interface=\"ether11\" ] gatewa\
    y ]\r\
    \n:global activegw2 [/ip route get [/ip route find comment=\"WAN-ISP2\"] g\
    ateway ]\r\
    \n:if (\$newgw2 != \$activegw2) do={\r\
    \n/ip route set [find comment=\"Ether2-Wan\"] gateway=\$newgw2\r\
    \n}"
/system scheduler
add interval=10s name=schedule_GWcheck on-event=\
    "/system script run number=CheckGW" policy=\
    ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-date=sep/06/2019 start-time=06:00:00

This is not full config, but you can add or change what you need !

add dst-address=1.1.1.1 gateway=192.168.100.1 scope=10 comment=WAN-ISP1
add dst-address=8.8.8.8 gateway=192.168.200.1 scope=10 comment=WAN-ISP2

To be honest, I was just saying that if you find some nice dual-WAN config you like, and it's made with static addresses, it's not a deal breaker, because you can use lease scripts to change config dynamically. Otherwise I don't enjoy multi-WAN configs very much and I tend to stay away. I also don't like RouterOS scripting, but in my defense, it didn't like me first.

Anyway, there are different ways how to do this. You can either do what example script does and add or remove items. Or you can create static config and only mark selected items with unique comments, and then use scripts to update them (change addresses, enable or disable them). If you do that, you can get away with much simpler scripts like this (from top of my head, not tested):

Code: Select all

:if ($bound=1) do={
  /ip route set [/ip route find where comment="WAN1 route"] gateway=$"gateway-address" disabled=no
} else={
  /ip route set [/ip route find where comment="WAN1 route"] disabled=yes
}

It can really help with debugging, which is the thing I hate most. I guess I'm spoiled, but any normal code will throw syntax or runtime errors and tells user where it happened. RouterOS scripting tends to just silently fail, so the shorter script is, the easier it's to work with it, at least for me.

With that cleared up, you can check the last link I posted, it describes more reliable way how to test working connections. And try to experiment a little.

@anav: It's not that easy. RouterOS is like LEGO, you get the basic parts and it's up to you what you build. There can be some automated shortcuts, but there's only limited amount of configs that could be supported in this way. And if you would need to combine them with anything extra, it could be a problem. I'm not saying that it's impossible, maybe some nice and compatible improvements can be done, but we definitely don't want another Quick Set that works fine by itself, but doesn't play well with the rest, do we?

Yes for all questions !

This is an important topic and one that is not properly documented or easy to do. In my estimation the router OS should already be designed to deal with dynamic ISPs and not force us knowledge peons to attempt to write scripts. In other words, I should be able to check a box that says dynamic IP (YES).
The result would be.....
- upon loss of connectivity (as evident in routing rules)
- reboot ISP, when connected grab new gateway IP
- replace IP ROUTE RULE old gateway IP with new gateway IP.
DONE.

This is what I have to do manually now and its a pain.

To be clear I have no idea what thost scripts are doing, how to program them and WTF (w=why) are we marking anything?
I simply want the new gateway IP to be inserted into the route rule(s).

This is an important topic and one that is not properly documented or easy to do. In my estimation the router OS should already be designed to deal with dynamic ISPs and not force us knowledge peons to attempt to write scripts. In other words, I should be able to check a box that says dynamic IP (YES).
The result would be.....
- upon loss of connectivity (as evident in routing rules)
- reboot ISP, when connected grab new gateway IP
- replace IP ROUTE RULE old gateway IP with new gateway IP.
DONE.

This is what I have to do manually now and its a pain.

To be clear I have no idea what thost scripts are doing, how to program them and WTF (w=why) are we marking anything?
I simply want the new gateway IP to be inserted into the route rule(s).

To be honest, I was just saying that if you find some nice dual-WAN config you like, and it's made with static addresses, it's not a deal breaker, because you can use lease scripts to change config dynamically. Otherwise I don't enjoy multi-WAN configs very much and I tend to stay away. I also don't like RouterOS scripting, but in my defense, it didn't like me first.

Anyway, there are different ways how to do this. You can either do what example script does and add or remove items. Or you can create static config and only mark selected items with unique comments, and then use scripts to update them (change addresses, enable or disable them). If you do that, you can get away with much simpler scripts like this (from top of my head, not tested):

Code: Select all

:if ($bound=1) do={
  /ip route set [/ip route find where comment="WAN1 route"] gateway=$"gateway-address" disabled=no
} else={
  /ip route set [/ip route find where comment="WAN1 route"] disabled=yes
}

It can really help with debugging, which is the thing I hate most. I guess I'm spoiled, but any normal code will throw syntax or runtime errors and tells user where it happened. RouterOS scripting tends to just silently fail, so the shorter script is, the easier it's to work with it, at least for me.

With that cleared up, you can check the last link I posted, it describes more reliable way how to test working connections. And try to experiment a little.

@anav: It's not that easy. RouterOS is like LEGO, you get the basic parts and it's up to you what you build. There can be some automated shortcuts, but there's only limited amount of configs that could be supported in this way. And if you would need to combine them with anything extra, it could be a problem. I'm not saying that it's impossible, maybe some nice and compatible improvements can be done, but we definitely don't want another Quick Set that works fine by itself, but doesn't play well with the rest, do we?

:if ($bound=1) do={
   /ip route set [/ip route find where comment="WAN1 route"] gateway=$"gateway-address" disabled=no
   /ip firewall address-list set [/ip firewall address-list find where comment="WAN1 list"] address=$"gateway-address" disabled=no
} else={
  /ip route set [/ip route find where comment="WAN1 route"] disabled=yes
}