@steve-burk I like Steve's suggestion for your own problem as it will absolutely work, but in the hope of making things needlessly complex, this is what I'd do:
Create a shell script that is comprised of the commands you need to provision the route.
In your installation script (you have one, don't you? ;^), check rc.local for a reference to the script. Insert a call to rc.local if it's not in there.
Also in your install script, copy the route provisioning script to somewhere sensible, such as /usr/bin/. This directory is in the path and need not be "spelled out" in rc.local.
Perhaps you could write a script that takes routes as a command line parameter. As such you could easily call the command multiple times from rc.local to configure multiple routes or perhaps better yet, pass along not a route but a config file path that contains the routes you desire. If the latter, you just mod the route config file and reboot - voila!
If you're dabbling, this suggestion is overkill. If you're trending toward production, this is a bit more important and ought to be considered. Your mileage may vary.
If your issue has been resolved, please edit your topic and add "resolved" to the title and add the "resolved" tag (at the bottom of the edit window) so that other users may easily find the information in the future. Plus you're helping make the community better! :)
Essentially a Linux environment is required, but of more importance are the dependencies. These are mostly Python packages. We’ve tested Snoopy on Kali 1.x, and Ubuntu 12.04 LTS. We managed to get it working on Maemo (N900) too. We’re investigating getting it running on OpenWRT/ddWRT. Please let us know if you have success.