-
Release Notes
- July 8, 2024
- May 22, 2024
- April 17, 2024
- March 20, 2024
- February 22, 2024
- January 18, 2024
- 2023 Releases
- 2022 Releases
-
2021 Releases
- December 20, 2021
- December 1, 2021
- November 22, 2021
- November 4, 2021
- October 26, 2021
- September 30, 2021
- September 22, 2021
- September 2, 2021
- August 16, 2021
- August 2, 2021
- July 19, 2021
- July 1, 2021
- June 17, 2021
- June 1, 2021
- April 30, 2021
- April 8, 2021
- March 25, 2021
- March 15, 2021
- February 25, 2021
- February 8, 2021
- January 28, 2021
- January 21, 2021
- January 13, 2021
- 2020 Releases
- Getting Started
- Ports
- Cross Connects
- Point-to-Point
- Virtual Circuits
- Cloud Connections
- Cloud Router
- Marketplace & IX
- Administration
- Billing
- Troubleshooting & FAQ
- Technical Reference
- Partners Portal
- API & Automation
August 2, 2021 Release Notes
New features
IPSec VPN connections for PacketFabric Cloud Router
You can now add an IPSec VPN connection to a PacketFabric Cloud Router. This will allow you to connect branch locations, on-premises users, and remote data centers to the PacketFabric Cloud Router quickly and easily.
For more information, see Site-to-Site VPN for Cloud Router.
Changes and enhancements
User groups
Users can now only be in one permissions group at a time. This is to support future development for group customizations.
When creating a new user, or when editing the groups for an exisiting user, you can no longer select multiple permission groups.
Existing users who are in multiple groups will not be removed from any groups; however the same rules apply in that they are restricted to the permissions at the lowest group level.
Bug fixes
- A number of small API bugs were fixed with regards to the scheduled ports functionality (introduced in the July 19 release).
- Incorrect prefixes were allowed when editing BGP session details for Cloud Router.
- Users were able to set a 10 Gbps capacity for IBM connections, when 5 Gbps is the maximum allowed.
- Cloud Router configurations were incorrectly restricting
/31
broadcast addresses. - Disabling a provisioning port would result in a
500
error. Now a proper, descriptive error is returned instead.
Knowledge base
New pages
Updated on 19 Sep 2022