The examples, etc using the API are great. We are already trying to write our own simplified interface for end users in Delphi based on the examples provided, but it is a major pain for us to learn Delphi (java, ruby or any other programming language for that matter). Even python is tough if you want to make a GUI and are not a programmer.
Before we spend a lot of time re doing what someone else has already accomplished (TowNet, Mikrocontrol, etc), I was wondering if there is someone who already has developed an open, simple windows client, like winbox, but designed for end users so they can simply specify a few parameters without having to understand the entire RouterOS. Source code? We are looking for a complete example that could be easily tweaked.
Webbox is close to what we want, but since you cannot change it’s functionality, it is not going to do what we need.
With the introduction of LUA in v4, will we be able to port something like Gargoyle or LUCI onto RouterOS? This would be an interface that is customizable by us mere mortals (ISP guys with limited programming skills). LUA is close enough to simple scripting that we can figure it out and customize it ourselves. Of course you would need to be able to upload the LUA pages to a web server on the device in order for this to work.
Add/enable bridge or mesh interface
a. Bond interfaces into bridge or mesh
b. For bridge turn on or off RTSP
c. For mesh make portal node
Configure wireless
a. Set mode, band, frequency, SSID
b. Enable Nstreme
c. Enable WPA and set PSK
IP/Routing/NAT
a. Apply IP address and mask to interface
b. Enable NAT and set public interface
c. Set up port forwarding
d. Enable DMZ (one host for port forwarding) and set address
e. Set default gateway
f. Add/delete static routes
DHCP
a. Enable server on interface with range, default gw, and dns server
b. Enable client on interface
Administration
a. Set password
b. Set system ID
c. Set time zone and time
d. Enable and set NTP
All values would populate from the running configuration of the router. Apply would change only values that were altered. The rest of the detailed set up would be done via winbox or telnet by an administrator. If there were even more configuration available, but we had the option of editing the source to delete out the functions we don’t need for a particular type of user, it would be really cool. Maybe the ability to reset and run a script would be good. Still thinking about it.
This is the kind of application I think a lot of people want, but none of us has either the programming skill or the money to pay for development. Once an example is made, I bet you would have all sorts of variants. Your API test interface was good, but didn’t really go far enough in showing how edits would work, etc.
I’m working on an API client in C at the moment (for implementation in an openWRT metarouter). Has this been done yet? I don’t want to re-invent the wheel, especially since my C is really rusty.
