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 -- work: dga@lcs.mit.edu me: dga@pobox.com MIT Laboratory for Computer Science http://www.angio.net/
On Thu, 2002-07-18 at 14:00, Scott Granados wrote:
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?
The RANCID package includes a decedent of the Digex looking glass code. http://www.shrubbery.net/rancid/ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Yet another one.. this one has support for multiple routers ... free under GNU general public license Sush ftp://ftp.enterzone.net/looking-glass/CURRENT/ ----- Original Message ----- From: "Scott Granados" <scott@graphidelix.net> To: <nanog@merit.edu> Sent: Thursday, July 18, 2002 3:00 PM Subject: looking glass
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
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/%7Erouterproxy/abilene/ Source code for the I2 Proxy is available from http://tseg.uits.indiana.edu/dist Pete. On Thu, 18 Jul 2002, Scott Granados wrote:
Date: Thu, 18 Jul 2002 12:00:38 -0700 (PDT) From: Scott Granados <scott@graphidelix.net> To: nanog@merit.edu Subject: looking glass
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
participants (5)
-
David G. Andersen -
Larry Rosenman -
Pete Kruckenberg -
Scott Granados -
Sush Bhattarai