What are people using for looking glass software. Is it just some simple
perl code which grabs data from the router or is it more complex than
that?
Thanks
Scott
On Thu, Jul 18, 2002 at 12:00:38PM -0700, Scott Granados mooed:
What are people using for looking glass software. Is it just some simple
perl code which grabs data from the router or is it more complex than
that?
It's just perl. I have a copy of it at
http://www.angio.net/rep/lg.tar.gz
if you want it.
-Dave
The RANCID package includes a decedent of the Digex looking glass code.
Yet another one.. this one has support for multiple routers ... free under
GNU general public license
Sush
We have heavily modified a version of the MRLG
( ftp://ftp.enterzone.net/looking-glass/ ) to provide
controlled router access to a specific (mostly internal)
audience.
We have found that allowing people who normally have no
router access, to have read-only access to some normally
enable-only commands through a Web interface has been
invaluable in delegating diagnostics and "peer review".
The major benefit of a Web-based interface is that we can
control the commands, input parameters, output display, and
usability much better than with a command line interface.
For example, we allow "show config", but we cover up any
security-sensitive information (passwords, SNMP strings,
TACACS keys, server IP addresses, etc) in the command
output. The control is very flexible, allowing certain users
to see only certain things, or be able to execute commands
that other users can't, for example. We can embed HTML links
in the output to related resources (Web-based help, graphs,
related commands, etc). Everything is encrypted via SSH/SSL,
and can be tracked for audit and security purposes.
To see something similar to what we have done (and where we
got the idea from), see the Internet2 Abilene Core Node
Router Proxy at http://loadrunner.uits.iu.edu/~routerproxy/abilene/
Source code for the I2 Proxy is available from
http://tseg.uits.indiana.edu/dist
Pete.