Well to be honest … it’s complicated. The script can do it, (extended LTELIMITER script) but the statement is currently disabled. For the SXT with both SIM’s there is only that remote connection available, and all management is done remotely.. I do not want to fail-over to the other SIM when that network is not operational. The over-quota in this case still gives reduced speed, so there is still connection. The script warns instead for over-quota. (the actual swap statement is commented out in the LTELIMITER script for selecting the SIM and APN). I want to indicate what I prefer, but the script must be smart enough to switch back if that gives no connection. So switching SIM cards today is still by manually triggering the switch-script. (Script is needed as both SIM card and APN must be changed to reconnect.).
In the previous example the SXT’s are load balanced. So there it is different. The LTE is set down at the quota limit, and the balancer ignores that line. The LTE reopens when the quota is reset at the end of the metered period. (The LTELIMITER script) If all 3 are over quota they should reopen, just to have connection. But I have a satellite connection as fallback for the balancer.
The hEX with DUDE are local to those remote networks. (The hEX also make the SSTP tunnels as client to an internet reachable Mikrotik SSTP server (as TURN server for management nodes with DUDE client and WinBOX))