Please add a routing-table for dhcp-client, so that default-route would go to defined routing-table instead of default “main”. Something like that should also be available for pppoe-client, pptp-client, etc.
Right now it can be achieved using scheduler but it’s not a very clean way…
I wonder if we can script our way around these limitations with a while cycle that checks nonstop - a script running nonstop…
Sure you can. That’s not a very clean way of doing things, though. You’re constantly using some (little, but some) resources checking the conditions of the while loop and running whatever if statement you have in it checking if DHCP conditions changed.
Felix
1-3% cpu is worth it
A cleaner way would certainly be preferable.
On a sidenote, if anyone tries an infinite loop, make sure you add a delay.
:local a 1; :while ( a = 1 ) do={ :local ip [/ip add get 1]; :if ($ip = "127.0.0.1") do={ :local b 1; } else={ :local c 1 } }
pegs at 100%. Adding a 1 sec delay brings that down to 1% on an RB1000.
Felix
For now I’ve following code:
:if ([:len [ip dhcp-client get backbone.local gateway]]!=0) do={ :if ([:len [/ ip route find routing-mark=local]]=0) do={ / ip route remove [find routing-mark=local]; / ip route add gateway=[/ ip dhcp-client get backbone.local gateway] routing-mark=local check-gateway=ping; }; } else={ / ip route { remove [find routing-mark=local] }; }
That script is run by scheduler every 10s. One can ask why I don’t check “gateway”? Because there is a bug with routing-test that returns: “192.168.20.1 reachable backbone.local” instead of “192.168.20.1”. For now it works, but it would be better to have a native property…