7.2.4820
Release Date: 15 October 2024
What’s New updated 31 October 2024
See the Controller Release Notes for Corrected Issues and Known Issues in this release.
Controller Version Tracks
Aviatrix Controller releases have two versioning tracks, depending on the Linux OS version supported.
Controller versions that support the newer Linux OS have software image numbers that start with a "g3-" prefix.
-
Newer Linux OS is supported on Controller software versions with the g3 image:
-
7.2.4820
-
7.1.4183, 7.1.4139, 7.1.4105, or 7.1.3958
-
-
Older Linux OS is supported on Controller software versions:
-
7.1.4101, 7.1.3956, and earlier
-
Deprecation Notices
Controller UI Deprecation
The Aviatrix Controller UI will be deprecated in 2025. We recommend using CoPilot as your Aviatrix Management UI. Please contact your Account Representative for additional information.
“Keep Alive via Firewall Lan Interface” Option is Deprecated
The “Keep Alive via Firewall Lan Interface” option will be removed from the UI and enabled by default in a future Controller release. In preparation for that change, any newly launched FireNet resources will have “Keep Alive via Firewall LAN” (Keep Alive) enabled by default. You will not be able to disable the Keep Alive option. Existing FireNet resources should have “Keep Alive via Firewall LAN” set to enabled. Upgrades will be blocked if the Keep Alive option is disabled on any FireNet resources.
CloudN Not Supported
CloudN is not supported with any Aviatrix Controller releases that are based on the newer Linux OS. CloudN has been replaced with Aviatrix Edge. You must migrate CloudN Gateways to Aviatrix Edge before upgrading to a release based on the newer Linux OS. For more information, contact your account team.
New and Enhanced Features in Release 7.2.4820
Improved Troubleshooting for Network Connectivity Issues
New notifications have been added to help identify potential causes of connection problems. The following notifications will appear in the user interface when configuring or managing gateways:
-
Alert when a Gateway configuration is out-of-date
-
Warning when Geoblocking is enabled on a Gateway
This update helps to quickly pinpoint if Geoblocking rules or stale configurations are preventing connections from establishing properly. It also eliminates the need to manually check logs or configuration status when troubleshooting unexpected connectivity issues. It is particularly useful for diagnosing problems with BGP (Border Gateway Protocol) connections.
This update does not affect HPE or Public Subnet Filter Gateway functionality.
Intra-VPC AWS Diagnostic Tool Added
Added new functionality to track Aviatrix security policy enforcement in AWS VPCs. This improves visibility and troubleshooting for AWS intra-VPC security policy enforcement and allows administrators to easily verify applied security rules.
Edge Transit Gateways
This release provides a major new capability for Aviatrix Edge Gateways. Edge Transit Gateways have been added to provide a secure, high-performance networking solution designed to simplify and accelerate hybrid and multi-cloud connectivity. Edge Transit Gateways enable seamless routing and end-to-end encryption across various cloud providers and on-premises environments, while providing centralized management and operational visibility. This feature is available at Cloud Fabric > Hybrid Cloud > Edge Gateways.
Edge Transit Gateways is a GA Feature for Aviatrix Edge Platform (AEP) and is a Preview Feature for Equinix Network Edge and Megaport Virtual Edge (MVE) in this Controller release.
Proxy Management for Aviatrix Edge Platform
Customers deploying Edge on physical appliances like Dell and HPE hardware, can now configure explicit and transparent proxies for Edge OS management connectivity outbound. The proxy support allows enterprises to leverage the proxies in their environment and Edge OS can now seamlessly call home via proxy server configuration.
You can configure proxy profiles for Edge Platform network connections from Cloud Fabric > Edge > Devices. You can create multiple proxy profiles to route traffic based on organizational requirements.
For more information, see Onboarding an Edge Device for the Aviatrix Edge Platform.
DCF Support for Disconnected VPC/VNETs with Overlapping IPs in Azure
Customers can now leverage Distributed Cloud Firewall (DCF) for Egress security in Azure across multiple disconnected VPCs with the same IP ranges.
When using SmartGroups VM, VPC, or Subnet-type selectors, Aviatrix now intelligently programs policies for the appropriate VPCs even if the CIDRs are the same. CIDR-based SmartGroups are still programmed on all VPCs/VNets that match the CIDR. Logging will show the gateways that are enforcing the policies along with the appropriate rule UUIDs. This feature is already supported in AWS in previous releases.
Enhanced Distributed Cloud Firewall (DCF) Scale
Distributed Cloud Firewall (DCF) now has support for up to 5,000 rules and higher Groups scale.
Key Highlights:
-
Support for 5,000 DCF rules
-
1,200 Groups (ThreatGroups, and SmartGroups)
-
200 System GeoGroups
-
300,000 matched CIDRs
Dynamic Security Updates on Aviatrix
This Distributed Cloud Firewall (DCF) feature enhances how GeoGroups and ThreatGroups are automatically updated with the latest security intelligence.
Key Features:
-
MaxMind Integration: GeoGroups are updated regularly with the latest geographical data from MaxMind.
-
EmergingThreats Integration: ThreatGroups are continuously refreshed with Suricata Rules and threat intelligence from EmergingThreats.
-
Automated Resource Updates:
-
Controller Sync: The Aviatrix Controller checks for updates every hour. If new data is detected (via hash changes), it pulls and stores updated resources automatically.
-
Gateway Sync: Gateways check for updates from the Controller every hour. If changes are found, the Gateway downloads and applies the new resources seamlessly.
-
Continuous Protection: Missing or modified resources are automatically downloaded and updated, ensuring policies are always based on the latest security intelligence without manual intervention.
-
GCP Underlay Support on Edge
This release now supports the option of terminating Google interconnect connection on Edge Gateways and the ability to set up BGP to Google Cloud Router.
NetFlow Sampling Rate
An option has been added to the NetFlow Agent that allows you to set the NetFlow sampling rate. Adjusting the sampling rate can reduce storage requirements and, in some cases, could provide a more accurate representation of NetFlow.
FlowIQ, CostIQ, and Anomaly Detection will factor in the sampling rate in the individual features. The sampling rate cannot be set to less than 100% for ThreatIQ and Geoblocking, if you are currently using those features.
For more information, see Configuring the Aviatrix NetFlow Agent.
FireNet and Next-Generation Firewall (NGFW) in China
This release enables you to securely expand your cloud footprint into China, using Palo Alto Firewalls in Azure China for advanced traffic filtering and security.
Key Highlights:
-
FireNet with NGFW Integration with Palo Alto Firewalls.
-
Regulatory compliance with local Chinese regulations.
-
Global expansion into China using localized versions of AWS, Azure, and Alibaba Cloud.
Preview Features in Release 7.2.4820
See the documentation for an explanation of Aviatrix Feature Modes.
Edge Transit Gateways for Equinix and Megaport
Transit Edge is a Preview Feature for Equinix NE and Megaport MVE in this controller release.
Global GCP Spoke Support for FireNet Egress
This Preview Feature enables secure and streamlined egress traffic management in Google Cloud Platform (GCP) deployments.
Key Features:
-
Global Spoke Support: Extend FireNet functionality to GCP spokes, allowing you to manage outbound egress traffic securely and efficiently across your global GCP network.
-
Centralized Traffic Filtering: Integrate with the Aviatrix FireNet architecture, centralizing security policies and egress filtering for spokes, reducing complexity, and improving visibility into egress traffic.
For more information, see Enabling and Disabling GCP Global VPC.
ThreatGroups and GeoGroups for Enhanced Security
This release introduces two powerful new Preview Features, ThreatGroups and GeoGroups, designed to strengthen your security posture through dynamic content filtering and real-time threat intelligence.
-
ThreatGroups: Leverage external dynamic content filtering to create advanced threat prevention policies based on real-time intelligence. This allows for more precise and adaptable security measures, enhancing your overall defense against emerging threats.
-
GeoGroups: Implement geolocation-based policies to block or allow traffic from specific regions, enabling more granular control over your network security.
These new features seamlessly integrate with ThreatIQ, providing you with enhanced flexibility and control to safeguard your infrastructure from location-based and evolving threats.
See the documentation About Groups.
Distributed Cloud Firewall Rule Enforcement on External Connections
This Preview Feature significantly enhances security and traffic management capabilities for hybrid cloud deployments.
Key Highlights:
-
Enforcement of Distributed Cloud Firewall (DCF) policies on Site2Cloud interfaces.
-
Specific Use Cases: Designed specifically for Partner Landing Zones, Backbone Use Cases, and CloudWAN/AVA scenarios.
-
DCF rules can be pushed to both Spoke and Transit Gateways.
Distributed Cloud Firewall (DCF) Policy Push to Public Subnet Filtering (PSF) Gateways
This release enables organizations to enhance security for their public-facing workloads by leveraging advanced traffic filtering and security features. This is a Preview Feature.
Key Highlights:
-
DCF with PSF Gateway Integration: Apply advanced security policies to secure inbound and outbound traffic in public subnets.
-
Dynamic Policy Enforcement: Utilize GeoGroups, ThreatGroups, WebGroups and SmartGroups to dynamically filter traffic based on geographic locations, known threats, and custom groupings.
Support for Additional Cloud Regions
The following CSP regions are supported as a Preview Feature in this release.
AWS
-
ca-west-1 (Canada—Calgary)
-
ap-southeast-4 (Melbourne)
-
eu-south-2 (Spain)
-
eu-central-2 (Zurich)
-
ap-south-2 (Hyderabad)
-
il-central-1 (Israel—Tel Aviv)
Azure
-
Mexico Central
-
Italy North
-
Poland Central
-
Spain Central
-
Israel Central
OCI
-
me-riyadh-1
-
us-chicago-1
-
eu-stockholm-1
-
eu-paris-1
-
eu-madrid-1
-
sa-valparaiso-1
-
sa-bogota-1
-
ap-singapore-2
-
mx-queretaro-1
-
mx-monterrey-1
Alibaba
-
acs-me-central-1 (Riyadh)
Behavior Changes in Release 7.2.4820
Limit Check for ECMP
A limit check has been added for equal-cost multi-path (ECMP) Tunnels. A maximum number of tunnels can be created between certain gateway types:
-
For older versions of Linux OS gateways: 123 tunnels
-
For newer versions of Linux OS gateways: 466 tunnels
See Controller Version Tracks for specific version numbers.
You can address this issue by doing any of the following:
-
Reduce tunnel count to stay under the limit.
-
Use larger gateway sizes supporting more tunnels.
-
Distribute connections across multiple gateways.
Keep Alive via Firewall Lan Interface Is Removed
As of 7.2.4820, the Keep Alive via Firewall Lan Interface option has been removed from the Controller UI. This action is now enabled by default and performed automatically.
Spaces Now Allowed in Object Names
You can now include spaces when naming rules, rulesets, SmartGroups, and WebGroups. Previously, names were restricted to alphanumeric characters, hyphens, and underscores. The maximum name length remains 128 characters and names must still be unique within your account.
Distributed Cloud Firewall Rule Changes
-
Previously, when the "Ensure TLS" setting on a (DCF) rule was enabled, non-encrypted HTTP traffic was incorrectly passed to the next rule instead of being dropped. This occurred even when all other rule criteria were matched. The issue specifically affected HTTP traffic on port 80.
With this release, rules with Ensure TLS enabled correctly match TLS traffic and drop non-encrypted HTTP traffic.
If you want to verify that the Ensure TLS feature is performing as you expect, you can do the following:
-
Disable the Ensure TLS option on the DCF rule.
-
Wait awhile and then check traffic logs to see If non-TLS traffic matches the rule.
-
Re-enable Ensure TLS or configure a new DCF Rule, as needed.
-
-
DCF rules were not properly applied to non-encrypted, non-web traffic (Non-TLS and Non-HTTP traffic) when processed by the High Performance Encryption (HPE) enabled gateways.
This issue was fixed to enable correct identification and Rule enforcement for all traffic types, regardless of Rule order.
Logging Terminology Consistency
Inconsistent use of "DROP" and "DENY" in traffic logs for blocked connections caused confusion when interpreting Layer 7 and Layer 4 traffic logs. "DROP" and "DENY" were used interchangeably to indicate blocked connections. With this release, all Logs will be updated to consistently use "DENY" for all blocked traffic.