This release adds a bunch of new features and tidies up a number of bugs / regressions in the v5 release train. All IX's running < v5.3.0 are advised to upgrade.
Summary:
git --no-pager diff --shortstat --no-merges v5.2.0 v5.3.0
277 files changed, 28450 insertions(+), 15504 deletions(-)
Upgrade Instructions
Please follow the official upgrade documentation without skipping any steps. Then read through the release notes below for any additional tasks.
Other Post-Upgrade Tasks
-
Some very old databases may have a bad default value in some columns. Please run the following SQL manually:
UPDATE `cust` SET `dateleave` = NULL where CAST(dateleave AS CHAR(10)) = '0000-00-00'
-
See the SQL query in Patch Panel History Improvements below.
-
Country and city details per IX-F Export Improvements below.
2FA and User Session Management
Two factor authentication (2fa) strengthens access security by requiring two methods (also referred to as factors) to verify your identity. Two factor authentication protects against phishing, social engineering and password brute force attacks and secures your logins from attackers exploiting weak or stolen credentials.
IXP Manager now supports a Google Authenticator compatible 2fa system.
In addition to this, we have implemented user session management which allows a user to be logged in and remembered from multiple browsers / devices and to manage those sessions from within IXP Manager.
See details here: https://docs.ixpmanager.org/usage/authentication/
IX-F Export Improvements
IXP Manager sets the switch location on IX-F Member Exports to the global city and country as defined in the IXP Manager configuration file.
We have added fields to the infrastructure (for your IX's country) and facilities (for city and country) to provide more precise information in the export.
After you upgrade IXP Manager, please edit your infrastructure(s) and set the new country field and then edit your facilities and set their city and country in the new fields provided. Once set, the IX-F Export will use these instead.
Patch Panel History Improvements
We chose not to link historical patch panel ports to customers via the customer database ID to avoid foreign key issues when customers are deleted. This meant it is difficult to show a specific customer's historical patch panel ports. This was fixed in v5.3 and admin users can now also see historical patch panel ports assigned to customers in the overview page for convenience.
To populate the customer history for your current database, please run the following after you upgrade:
UPDATE patch_panel_port_history ppph
SET ppph.cust_id = (
SELECT c.id FROM cust c WHERE c.name = ppph.customer
)You just need to do this once.
Small Features & Improvements
- Looking Glass: navigation between looking glass instances improved (b488a66)
- Looking Glass: only translate communities for route servers / collectors. Our communities only exist within our BGP daemons and any member using the same community tag would have a different intention / meaning.
- Patch Panels: hide LoA options for non-customer ports (342b7ec)
- PHP 7.4: IXP Manager is tested (and developed) on PHP 7.4 without issue (2178455)
- Provisioner API: IP addresses are now included in the layer2interfaces (ab7f682)
- VLAN Interface: ARPA hostname can be made optional by setting the configuration option:
IXP_FE_VLANINTERFACES_HOSTNAME_REQUIRED=false.
Bug Fixes
- Issue deleting a customer #568
- Wrong login history displayed for user #594
- Peering matrix displaying two rows rather than one (1eaf792)
- Resold member details show billing information when it shouldn't (c32e4e0)
- Switch configuration results in HTTP 500 error #602
- last logins -> login history -> view -> generates 404 (fa09668)
- Patch panel port list page - server 500 error (2aa8934)
Other Acknowledgements
We had a second level student on work experience who found a bunch of cosmetic issues and these were fixed in 1d5e700 - thanks Adam!