I would like to see a whole swag of new features that would help manage RouterOS devices.. by the thousand. I want to be able to manage Mikrotik HomeAPs from the cloud, regardless of what firewalls, NATed routers etc might be in between.
- HTTP POST support for sending usage summaries etc to cloud service. HTTP is good, as it will be open through most firewalls. I can use HTTP GET, but as all the parameters are part of the URL, its easy for some foreign agent to attempt to pollute the data.
- RouterOS as a uPnP client. The PHP API is good, but doesn’t help if the RouterOS device to work behind a NATed router. Allow RouterOS device to work behind a NATed router by pushing port forwarding rules to the NATed router.
- Mikrotik “PUSH” protocol. Maybe something similar to the Apple Push Protocol that leave a (client initiated) TCP session open, to get notifications/commands back to a firewalled/NATed RouterOS device, without the need to do periodic Polling (Pull) by the RouterOS device.
- Easy reporting of user authentication and LAN DHCP lease information over SSL. I can collect and send this using syslog, but its not secure.
- Parsing and secure passing of RouterOS WebProxy data to the cloud. Again syslog is possible, but data volume is huge and syslog is insecure. I just want to summaries of Date/Time, LocalIP, Username (matched via DHCP lease to IP), URL, byte count, of the HTTP Request Responses.
- Ability to have multiple devices associated with one Hotspot user, some using username for authentication, some using MAC, but all accounting against one usage limit and time limit.
- TR-069 - may be a solution for updating some router configs remotely, but probably not a “Cure all”.