| Xsight Network Monitor |
You will probably want to restrict access to Xsight.
You can do this through your web server security mechanisms (eg username/password). Xsight organises data into sites. Each site has its own directory under www in the Xsight root directory. You can create individual site access policies, eg using Apache .htaccess files.In addition, Xsight allows you to restrict who can make changes to your configuration: if a file called ACL is present in the control/site directory, it is assumed to contain a list of IP addresses (one per line) of those workstations which are allowed write access to the site. Simple wildcards such as 192.168.1.* are allowed. If ACL doesn't exist, everyone who can access the web pages will be able make changes. If ACL exists and is empty, *no-one* will be able to make changes. Remember to allow access from localhost if you are making changes on the same computer as xsight is running on. An ACL file can be created in the control/.xsight directory to control who can create and modify sites.
When a new site is created, the file ACL (if it exists) is copied from the xsight directory, and the contents of the Default directory are copied to the new site's www directory, so you could set up a default access policy for new sites eg by creating a default .htaccess file and a default ACL file.
| v5.8 Copyright © 2004-2008 | IPv1 Networks Ltd |