Changelog 4.10 beta1


  • While adding DHCP lease for particular MAC address the system checks if the MAC address has assigned any IP address dynamically. If yes, dynamic record is removed at first. In the past dynamic record was not removed but it caused (in the case of assigned IP address from dynamic pool) that IP address was assigned after timeout of previous assigned IP address.


  • Customized RADIUS to better identify disconnected clients. In some previous cases (e.g. link failure) RADIUS was not able to detect these disconnected clients properly and after re-connection clients still looked like disconnected.
  • While adding DHCP lease for particular MAC address the system checks if the MAC address has assigned any IP address dynamically. If yes, dynamic record is removed at first. In the past dynamic record was not removed but it caused (in the case of assigned IP address from dynamic pool) that IP address was assigned after timeout of previous assigned IP address.

Changelog 4.10 beta2


  • Added support of UBNT Edge Router.
  • Added support of Cambium ePMP 1000.
  • Content filtering option has been also customized, so it is now possible to select "Router type" from pop-up menu and choose type "Ubiquiti Edge Router" or "Cambium".
  • When access details are filled in the system will start to retrieve interface list from routers (approx. in 5 minutes) and also will start to draw transfer graphs, signal graphs of connected clients (if available) and CPU graph.


  • In the tab "Settings / IP Pools" there is a new tab "NAT Pools".
  • There is possible to define public IP addresses used for NAT of clients.
  • While adding NAT pool there it is possible to define range of IP addresses (network number / mask) and also router which is that range defined on.
  • While adding Internet service in a client card there is now possible to defined IP address (on which NAT is provided) from pre-defined range. System provides NAT on particular router automatically (if enabled) for private IP address of the client.
  • To enable applying of NAT address on router, it is necessary to set up key "mikrotik_nat_for_end_user" to value "1" in the tab "Settings / Syst. settings / Mikrotik". In other case (value "0") NAT will not be applied to Mikrotik.
  • If enabled, every client will have applied another rules "dstnat" and "srcnat".
    • /ip firewall nat add action=netmap chain=ispadmin_first_dstnat comment=ispadmin_NAT_1.2.3.4_10.10.0.100 dst-address= to-addresses=
    • /ip firewall nat add action=netmap chain=ispadmin_last_srcnat comment=ispadmin_NAT_10.10.0.100_1.2.3.4 to-addresses= src-address=


Changelog 4.12 beta1


  • In a situation where the router Mikrotik is only an AP without any routed network and clients, and also has QOS set on his parent router. It starts to write the clients, that are assigned to this access point, to the Access-List(included AP-TX-LIMIT, CLIENT-TX-LIMIT according to the settings for internet services).The Routers have to be listed as active and their API, MAC filter, wi-fi Mac has to be enabled.

Changelog 4.13 beta1


  • New rewritten router list.
  • In the router list. a new filter State was added, which has the option to filter Monitored routers and Routers with a restart configuration.
  • In the router list under the filters, the buttons + and - are located. With the help of these buttons, it is possible to hide or show all parent routers. In the hidden state, a list view with the most important information is displayed. At the beginning of every row, a button + for the option to collapse is displayed. This option to expand or collapse is saved to each administrator account, so after the next login it displays the last set state. The same principal of expanding and collapsing is also used on Network interface, Device attached to device, Switches, Headends and Routers.
  • With the new rewritten router list, also the permissions for the routers have changed (tab Settings Administrators). The option to set the permissions to MasterAdmin and MainAdmin for the routers was removed. Now they have no effect on the router list. Everything is set for each administrator separately, this can be set on any given account.
    • Allow routers: routers ON/OFF
    • Adding routers
    • Editing routers
    • Deleting routers
    • Manage devices
    • Manage headends
    • Router restart
    • Update router configuration
    • Router backup
    • Photogallery management
    • Emergency mode

Changelog 4.14 beta1

  • Improved client portal for better usability - font style, column width, padding between virtual interfaces.
  • In the tab RoutersAll, new filter options, DFS supported and DFS enabled, for the State filter were added.
  • Now in the tab RoutersAll, WiFi clients on Access points are also displayed.
  • Now on the header of a router: in the tab Extra, the number of photos assigned to that a specific router is displayed.
  • The icon for displaying ping graphs on routers was added back to the frequently used icons.

Changelog 4.15 beta1

  • The tab with the list of switches was moved into the main tab Hardware.
  • Now it is possible to add a switch if it has no parent router.
  • For each switch (without a parent router) it is now possible to choose a locality. Switches with a set locality can then be assigned to an specific POP.
  • Now it is possible to assign a internet service to a switch (port of an switch) which aren't connected to any routers.

Changelog 4.15 beta1

  • New code list for POPs added, in the tab Settings Code lists POPs.
  • New tab Hardware Overview added. In it, it is possible to display the structure of the network. With all network elements (routers, switches, devices, passives element).
  • When first loading the page, it displays a list of localities with their name and online/offline state of all devices on a given locality.
  • Locality Overview: here it displays a list of localities of the tab Settings Code lists Locations. On each locality the name and the number of online/offline connections on a locality is specified. Located on the top right corner are icons with the options (add passive elements, legend). Every single locality and passive element is able to be connected in such a way that they correspond with the actual network. The connecting of an element is done by clicking and dragging into the yellow boxes of each element. After a link has been created it is possible to click on the link to display a menu with the options (add a note, remove connection).
    • POP Overview: POP Overview, passive elements and uplinks can be displayed by clicking on a locality. An Uplink is a connection between a locality or a POPs intended for a specific devices. On the right menu it is possible to display routers and switches which are on a locality and is possible to add them to a POP. The assigning is done by dragging the device icon on to a specific POP.
    • POP Details: By clicking on a POP it displays a list of devices that are assigned to the POP (routers, switches, passive elements and uplinks). Here it is also possible to make the same changes as on the POP site.
  • Every change of dragging and connecting is automatically saved.

Changelog 4.23 beta1


  • When adding a new router IP address entered is being checked against the database immediately. If already in use in the system a warning message will be displayed with router name which is used with the IP address. You will be able to save the form anyway.


Changelog 4.23 beta2


  • Arris modems are supported now: Allowed IP addresses of clients and devices are added to the configuration file of a modem using a new variable USER_ARRIS_IPS
  • The IP addresses listed will be able to access the internet. All other traffic will be disallowed. An object called docsDevFilterIp is used.

Changelog 4.24 beta1


  • There is a new subtab in the Hardware tab - Settings. In the future, it will aggregate all the global settings related to hardware matters. At this point, three tabs can be found here: Device type, End devices and Antennas.


Changelog 4.24 beta3


  • In Hardware Routers, descriptions of individual interfaces are available for graphs of a particular router.

  • Ramdisk and scripts used for data retrieval and graph creation have been optimized.

  • The Hardware Routers Radius Account stat. page has been rewritten.


Changelog 4.26 beta1


  • The following pages have been rewritten: Hardware Routers Router status BW test and Hardware Routers Router status Wifi scan.
  • You may now filter routers by POPs in Hardware Routers All.

Changelog 4.26 beta5


  • Hardware Routers: The current frequency, not the set frequency, is displayed for MikroTik routers with DFS activated.
  • An extra contact bug in the router configuration has been fixed. This bug could cause problems with the sending of Nagios notifications.
  • Router backup notifications have been implemented. If a problem occurs during the backup process, an email will be sent to the administrator.


Changelog 4.26 beta6


  • Modifications have been made to the way router backups work. Monthly backups are now created as well. The number of backups setting remains the same, but the backup procedure differs. If 10 router backups are to be made, 5 daily and 5 monthly backups will be created. That is, half the backups will be daily backups and the other will be monthly backups. If the value entered is an odd number, the number of daily backups will be greater than the number of monthly backups. The total disk space occupied will remain the same. 


Changelog 4.27 beta1


  • Redundant router - If you are in the process of adding/editing a router, you can now choose a new option Mikrotik - redundant in the Router type drop-down menu and then select a particular Master router. The rules applied to the redundant router will be the same as those applied to the selected Master router. Thus, there will always be a backup router with up-to-date configuration that can be used when it is necessary.


Changelog 4.27 beta2


  • Hardware Routers: Modifications have been made to the way switches and devices connected to routers are deleted. In some cases (if there were other devices dependent on the device to be deleted), a problem could arise that would lead to the deletion of all Nagios dependencies. The Status Map was affected as a result. This version fixes the problem. We recommend that you update your ISPadmin. If you use only stable versions, please update to the latest stable version (4.26 Stable).


Changelog 4.28 beta3


  • The structure of firewall rules in the NAT section has been optimized. This modification resolves a problem that could, in some specific cases, result in NAT 1:1 not working. It also resolves a problem with the redirection of incoming Internet traffic to the info page in the case of suspended services. For example, even though a client's Internet service was suspended, they could still access their CCTV and generate traffic.
  • It is now possible to disable backups in the configurations of individual routers.


Changelog 4.30 beta1


  • Hardware Routers All --> Network interface --> WiFi scan: The scan tool has been rewritten.
  • Hardware Routers Router status WiFi scan: The scan tool has been rewritten.
  • Hardware Routers All --> Device connected to router: If the installation address is not filled out, the Show on map button is disabled.
  • A duplicate IP address check has been introduced for active routers and switches. If you need to add a device with a duplicate IP address, the device status must be set to inactive.


Changelog 4.31 beta1


  • The Hardware Routers All > Test connection page has been rewritten.
  • The Hardware CMTS Detail > Ping page has been rewritten.
  • The Hardware Routers Router status WIFi Links page has been rewritten.
  • MikroTik - Settings - /radius: The src-address parameter is now automatically sent to the relevant MikroTik device. It works only via API.
  • Net::SSH::Perl upgraded to 2.14


Changelog 4.32 beta1


  • Hardware Routers All: New button added - Update selected routers
  • Radius data synchronization script rewritten
  • Bug fix - BW test start time


Tips on how to use this documentation



Searching required information is possible either via structured menu which is divided into sections, or via full-text search of the entire contents of this on-line documentation.

This aid will make it possible for you to find out where exactly you are at the moment.

If, for example, the following appears beneath the main menu - ISPadmin Wiki / ENG / Client management / Menu - CLIENTS / Clients / Message Board / Groups - it means that you are:


  • in the Wiki documentation of the ISPadmin system
  • in its English localization
  • in the Client management section
  • in the Clients tab
  • in the Message board subtab
  • in the Groups sub-subtab


It contains newly added functionalities and modifications of the system which are displayed by versions and issue date. Changelog articles are also displayed in individual sections / pages of the documentation which relate to new functionality or modification. 

Basic orientation

You will find a welcoming menu with basic instruction on trying / implementing / using below. 


Frequently asked questions along with most important procedures and settings are listed in FAQ section. 


Items which refer to real system menu are highlighted in corresponding colour, including their graphical background. Eg. Invoicing Settings Templates Reminders. This is also a working reference to an article. 


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