 |
ImportantIPv6 is not supported in
Routing Mode.
|
The following table explains which features and capabilities provide IPv6
support in Bridge Mode and Software Switch deployments. In addition to the support
specified
in the table, Cloud Edge can forward traffic over IPv6
through the Cloud Edge gateway, including to an IPv6
router, which can provide access to the Internet.
Cloud Edge IPv6 Support in Bridge Mode and Software Switch Deployments
|
Feature
|
Category |
Support for IPv6
|
Not Supported for IPv6
|
|
Dashboard
|
 |
||
|
Cloud Edge supports displaying
IPv6 addresses in the dashboard.
|
|||
|
Gateway— Registration
|
|
||
|
Cloud Edge uses IPv4 to connect
to Cloud Edge Cloud Console.
|
|||
|
Gateways — Network
|
Interfaces
|
|
|
|
Administrative access
|
|
||
|
DHCP
|
|
||
|
Dynamic DNS
|
|
||
|
Routing table
|
|
||
|
Static Routes
|
|
||
|
NAT
|
|
||
|
Cloud Edge gateways do not support
IPv6 for network configurations (any mode). However, Cloud Edge can forward requests such as DNS for
IPv6 and DHCPv6 through to end points.
|
|||
|
Gateways — Bandwidth control
|
|
||
|
Gateways — VPN
|
User VPN
|
|
|
|
Site–to–Site VPN
|
|
||
|
Gateways — End User Management — General settings
|
|
||
|
Functionality dependent on user accounts is not supported for
IPv6.
|
|||
|
Gateways — Updates
|
|
||
|
Cloud Edge uses IPv4 to connect to
ActiveUpdate.
|
|||
|
Gateways — Network Access Control
|
|
||
|
Cloud Edge does not support
network access control for IPv6 endpoints, even if the endpoint is dual-stack with
both an IPv4 and IPv6 address.
|
|||
|
Policies — Policies
|
Source IP
|
|
|
|
Source FQDN
|
|
||
|
Users / User Groups
|
|
||
|
Destination IP
|
|
||
|
Destination FQDN
|
|
||
|
Traffic — Applications and URL categories
|
|
||
|
Policies based on users or user groups are not supported for IPv6.
That policy will not be applied to IPv6 traffic.
|
|||
|
Policies — Objects
|
IP Address/FQDN
|
|
|
|
MAC Addresses
|
|
||
|
Services
|
|
||
|
Applications and application groups
|
|
||
|
URL categories
|
|
||
|
Cloud Edge supports ICMPv6.
|
|||
|
Policies — Approved Blocked List
|
IPv6 addresses
|
|
|
|
FQDNs
|
|
||
|
URLs
|
|
||
|
Policies — Security Profiles
|
IPS
|
|
|
|
Anti-Malware
|
|
||
|
Email Security — Local Scan
|
|
||
|
Email Security — Cloud Scan
|
|
||
|
Anti-DOS
|
|
||
|
HTTPS
|
|
||
|
Web Reputation
|
|
||
|
Endpoint Identification
|
|
||
|
Both email local scan and cloud scan do not support IPv6. IPv6 email
traffic will pass through the Cloud Edge
gateway without scanning.
HTTPS IPv6 traffic will pass through the Cloud Edge gateway without scanning.
Cloud Edge does not trigger
Endpoint Identification for IPv6 traffic. If Captive Portal is enabled, the
Captive Portal window will not open; IPv6 traffic will pass through the Cloud Edge gateway.
|
|||
|
Policies — Web Reputation Service
|
|
||
|
Policies — User Notifications
|
|
||
|
Cloud Edge supports displaying
user notifications to IPv6 clients.
|
|||
|
Analysis & Reports — Reports
|
|
||
|
Cloud Edge supports displaying
IPv6 addresses in reports.
|
|||
|
Analysis & Reports — Log Analysis
|
Application bandwidth
|
|
|
|
Policy Enforcement
|
|
||
|
Internet Access
|
|
||
|
Internet Security
|
|
||
|
Cloud Edge supports displaying
IPv6 addresses in the logs.
|
|||
|
Administration — Users & Accounts
|
|
||
|
Functionality dependent on user accounts is not supported for
IPv6.
|
|||
|
Administration — User Authentication
|
|
||
|
Functionality dependent on user accounts is not supported for
IPv6.
|
|||
|
Administration — Audit Log
|
|
||
|
Administration — Administrator Alerts
|
Gateway status change
|
|
|
|
Mail security status change
|
|
||
|
C&C Callbacks
|
|
||
|
Administration — Scheduled Updates
|
|
||
|
Cloud Edge uses IPv4 to connect
to ActiveUpdate.
|
|||
|
Administration — Maintenance
|
|
||
|
Cloud Edge uses IPv4 to connect
to external servers.
|
|||
|
Administration — Certificate Management
|
|
||