Name Last modified Size Description
Parent Directory - directory (probably)
Router Automatic Deletions.nfo 26-Oct-2007 03:59 2.1K plain text info
RouterAutomaticDeletions.tar.gz 26-Oct-2007 04:00 520 GZIP compressed archive
RouterRebooterShellScript.tar.gz 26-Oct-2007 04:00 459 GZIP compressed archive
brad.sh 26-Oct-2007 04:00 2.4K unix shell script
deprecated/ 13-Nov-2007 04:09 - directory (probably)
rad.sh 26-Oct-2007 04:00 1.4K unix shell script
rr.sh 26-Oct-2007 04:00 572 unix shell script
zipb-off.sh 26-Oct-2007 04:00 687 unix shell script
zipb-on.sh 26-Oct-2007 04:00 796 unix shell script
A few shell useful scripts for unix (*nix/Linux/OS X/BSD/Solaris/etc)
Those nasty in-built firewall rules can be removed with a single shell command (rad), amongst other things. now that we've nailed automatic telnet into the router, there's no end of things we could do, it's all
scriptable! If you have a new (or reset) router, check out "brad", with is "Big Router Automatic Deletions".
If you run Windows, Check out ARSE
The *nix versions (
) are generally renamed to
and placed inside
or somewhere else in your path, so you can simply type rad from your shell/ssh session/whatever.
: you can run shell scripts directly on the router itself. basically just create a plain text file (with a .sh extension) that is a series of commands like in all the router pages here at corz.org, then upload it via FTP, and run it from the telnet command line..
apply fname script.sh
you have to upload it into the root (not /home) folder, or else specify the full location on the command line (I presume)
If you're comfortable with the command line, and FTP, then it's a handy, quick way to get a series of commands into your router.
remember to commit
If you're brave, you can simply recreate your commitedcfg.cfg file and upload it, over-writing the original. At the exact moment the upload completes, your router will reboot. It will probably look like the ftp transaction failed at the end, it didn't, your router is rebooting. You can do this in the web interface, too. If you start with an exported config, life is easier.
Of course you will have thoroughly tested all the rules in this replacement commitedcfg.cfg before you upload it in place! Having said that, the viking chipset seems quite forgiving of most errors.