×

Warning

JUser: :_load: Unable to load user with ID: 43

JUser: :_load: Unable to load user with ID: 40

Groups

 

On this page, you can define in detail the rights of individual groups that will be used for the management of technicians’ access to routers. Then you assign individual users (technicians) to the groups you have created. You may create as many groups with various rights as possible.

 

A new group can be added by clicking on . On the page that appears, enter the name of a given group and set the individual rights the way you want. You can also modify the settings in the overview of existing groups. There is a list of rights for each group along with information about how you have configured them (icon check ok / icon check ko). You can change the configuration by clicking on individual icons. 

 

You can set the following rights:

 

local A given group of technicians is / is not allowed to log in through a local console.
telnet A given group of technicians is / is not allowed to log in through telnet.
ssh A given group of technicians is / is not allowed to log in through SSH.
ftp A given group of technicians is / is not allowed to log in through FTP. Such technicians can read, write and delete.
reboot A given group of technicians is / is not allowed to reboot a router.
read A given group of technicians is only allowed to read. No configuration changes are possible.
write A given group of technicians is / is not allowed to modify configurations (with the exception of user management - setting up further user accounts for access to routers). If you want to allow this group to read as well, you have to modify the read item accordingly.
policy A given group of technicians is / is not allowed to set up further administrator accounts for access to routers.
test A given group of technicians is / is not allowed to carry out the following tests: ping, traceroute, bandwidth-test, wireless scan, sniffer a snooper.
web A given group of technicians is / is not allowed to log in through the web interface.
winbox A given group of technicians is / is not allowed to log in through WinBox.
password A given group of technicians is / is not allowed to change passwords to individual user accounts.
sensitive A given group of technicians is / is not allowed to see sensitive data, such as passwords, wireless keys etc.
api A given group of technicians is / is not allowed to log in through API.
sniff A given group of technicians is / is not allowed to use a sniffer utility.

 

You can edit a particular group by clicking on icon edit.

You can delete a particular group by clicking on icon check ko grey.

 

System back-ups

ISPadmin has an automatic data back-up functionality. It is possible to store...

MySQL database

Restart of MySQL service /etc/init.d/mysqld restart Recovery of database...

ISPadmin update

Switch to new system version using the following command from command line (logi...

Postfix mail server

By default, the SMTP server is configured in the way that it is only possible...

System Variables

System variables are used for replacing items such as client's name, address,...

System migration

The information contained in this manual pertains to the migration of ISPadmin ...

Emails cannot be sent because of their size

Check and modify the settings of the following parameters: upload_max_f...

Ramdisk and RRD backup-data restoration

More on RAM disk here (index.php?option=com_content view=article id=508:4-11-bet...

HTTPS Certificates

These are instructions on how to create and set up trustworthy certificates (h...

Crashed table repair

these instructions (index.php?option=com_content view=article id=1284:system-bac...

Moving graphs to RAMDISK

The main usage load for disks, on which the system is installed on, is the gener...

Forgotten root password

You can try two ways: First procedure 1. Insert installation DVD of ISPa...

Text editors

Nano text editor is always used in this documentation. If you don’t...

Linux update

For reasons of compatibility and availability of future versions of ISPadmin,...

ISPadmin serving as SMTP server

By default, the SMTP server is configured in the way that it is only possible to...

Cache-only DNS server

Caching-only is ready after installation of ISPadmin. It is sufficient to use IP...

Technical support status cannot be verified

If technical support cannot be verified, most likely it is due to DNS malfunc...

Administration of running processes

We recommend using htop program for easier monitoring of running process inst...

Timezone settings

"Europe/Prague” timezone is set by default. To change it, do the following:...

IPv6

ISPadmin does not currently support IPv6, it only supports IPv4. It is, of cours...

Configuration / update of IP Address

A) Temporary setting of IP address (until next Linux restart).Just add the fo...

High CPU load of ISPadmin server

Run htop command from the Linux console to determine the problems. With this ...

ISPadmin operation behind NAT

If you have your ISPadmin located on private network and wish to access it from ...

Manual update

If the Error 404: Not Found message appears during an update, it will be necessa...

Inner/outer address on ISPadmin server

The system is typically connected to the network by one network card only. Both ...

Running service check

If you need to find out if a certain process is running use the following comman...

Error "Allowed memory size of ... bytes exhausted ..."

Fatal error: Allowed memory size of ... bytes exhausted (tried to allocate ... b...

What is the directory structure in /usr/local/script/ispadmin/rrd_data?

headend ipaccount modem routers snmp switches user_devices wifi

«
»

CONTACT

NET service solution, s.r.o.
Žerotínova 3056/81a
787 01 Šumperk
Czech Republic