RELEASE DATE: November 8, 2018
- According to an official MikroTik announcement (https://wiki.mikrotik.com/wiki/Manual:API), newer versions of ROS (> 6.43) will utilize a new API login method. The key difference lies in the use of a password in plain text. For security reasons, it is necessary to use exclusively communication via API-SSL.
- This version of ISPadmin includes new automatic tools and libraries that attempt to switch all the active MikroTik routers with ROS >= 6.43 to API-SSL. If communication via API-SSL works all right, the system starts using API-SSL. If communication via API-SSL does not work, the system continues using the old API login method. It will use it only as long as the method is supported by MikroTik. Afterwards, API will stop working. The system attempts to switch routers to the new API login method every single hour via API or SSH.
- MikroTik routers with ROS < 6.43 can be switched to API-SSL manually through the router settings (new item: Use API-SSL). After this change, it is necessary to check whether communication with a given router works as it should (Test connection to router).
Hardware / Routers / Router status / Routers
- New tables added: Firmware versions and Other services. The latter shows the status of services that are currently vulnerable to malicious activities (socks, web proxy, packet sniffer).
- In the Update status column (formerly: Version status), you can find a history of the last 5 executed commands related to a given scheduled action. You can check the history for potential errors.
- New option added to the list of actions: Change service configuration. With the help of this feature, you can activate/deactivate services on selected routers, allow access only from certain IP addresses or change port. This way, you can improve network security.
Hardware / Routers / Router status / Dashboard
- New table added: Hardware versions (overview of MikroTik router types used)
- New column added to the Basic services table: Ispadmin (number + type of communication used by ISPadmin)
- Modification: 1 reminder = 1 invoice. It is thus possible to use even those system variables that must always be associated with one specific invoice. It is possible to enter a minimum debt amount per invoice for a reminder to be generated.
- Modification: It is possible to generate multi-page reminders.
- New: Overview of reminders to be generated: The overview appears when you click on the number given in the Number of reminders section.
- Bug fix: The number given in the Number of reminders section was not always correct.
Other changes and bug fixes
- Modification: Filter Details / Renewal - NO in Clients / Internet
- Modification: Edit invoicing period
- Modification: Allowed pages edited → Master reset performed on all the relevant routers
- Bug fix: Invoicing / Overviews / Invoicing / By period / Overview of invoices: Ordering in CSV exports
- Bug fix: Filter Tariff - Not set in Clients / Internet
- Bug fix: PDF files attached to emails from Scheduling
- Bug fix: Address given in a text (SMS) message that is sent to an assigned technician from Scheduling
- Bug fix: Switch from a redundant router to a normal one
- Bug fix: GDPR consent in the Client portal
- Bug fix: Send settings via e-mail in the Client card
- Bug fix: Handling of DOCX files in Settings / Contracts / My templates
Did this article help you?