Summary
Learn about the limitations of IPv6 in Worry-Free Business Security (WFBS).
Details
The following table lists the limitations when the Security Server only has an IPv6 address:
| Item | Limitation |
|---|---|
|
Agent management
| A pure IPv6 server cannot:
|
| Updates and centralized management | A pure IPv6 server cannot update from pure IPv4 update sources, such as:
|
| Product registration, activation, and renewal | A pure IPv6 server cannot connect to the Trend Micro Online Registration Server to register the product, obtain the license, and activate/renew the license. |
| Proxy connection | A pure IPv6 server cannot connect through a pure IPv4 proxy server. |
| Plug-in solutions | A pure IPv6 server will have Plug-in Manager but will not be able to deploy any of the plug-in solutions to:
|
Most of these limitations can be overcome by setting up a dual-stack proxy server that can convert between IPv4 and IPv6 addresses (such as DeleGate). Position the proxy server between the Security Server and the entities to which it connects or the entities that it serves.
The following table lists the limitations when agents (Security Agents or Messaging Security Agents) only have an IPv6 address:
| Item | Limitation |
|---|---|
| Parent Security Server | Pure IPv6 agents cannot be managed by a pure IPv4 Security Server. |
| Updates | A pure IPv6 agent cannot update from pure IPv4 update sources, such as:
|
| Scan queries and Smart Feedback | A pure IPv6 Security Agent cannot send queries to Trend Micro Smart Protection Network and cannot use Smart Feedback. |
| Plug-in solutions | Pure IPv6 agents cannot install plug-in solutions because none of the plug-in solutions support IPv6. |
| Proxy connection | A pure IPv6 agent cannot connect through a pure IPv4 proxy server. |
Most of these limitations can be overcome by setting up a dual-stack proxy server that can convert between IPv4 and IPv6 addresses (such as DeleGate). Position the proxy server between the agents and the entities to which they connect.
