.. up to the main site

Icon  Name                                       Last modified      Size  Description
[PARENTDIR] Parent Directory - directory (probably) [TXT] Router Automatic Deletions.nfo 2013-12-16 22:09 2.1K plain text info [   ] RouterAutomaticDeletions.tar.gz 2013-03-10 05:38 520 GZIP compressed archive [   ] RouterRebooterShellScript.tar.gz 2013-03-10 05:38 459 GZIP compressed archive [TXT] brad.sh 2013-03-10 05:38 2.4K unix shell script [DIR] deprecated/ 2013-12-24 05:32 - directory (probably) [TXT] rad.sh 2013-03-10 05:38 1.4K unix shell script [TXT] rr.sh 2013-03-10 05:38 572 unix shell script [TXT] zipb-off.sh 2013-03-10 05:38 687 unix shell script [TXT] zipb-on.sh 2013-03-10 05:38 796 unix shell script

The BT Voyager 205 page is HERE

info:

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, instead..

The *nix versions (something.sh) are generally renamed to something and placed inside /usr/local/bin or somewhere else in your path, so you can simply type rad from your shell/ssh session/whatever.

note: 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 afterwards!

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.