How can we help?
-
zWAN
-
-
-
-
-
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
-
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
- Articles coming soon
-
-
-
- Articles coming soon
-
- IPsec Tunnel not Establishing
- SSL-VPN Tunnel not Establishing
- Mobile Network Issues
- Management Tunnel does not Establish
- DNS not Resolving from Local Network Appliance
- DNS Resolution Issues in Tunnel Configuration
- DHCP Server not Leasing IP to LAN PC
- Debugging EC Events - Unknown Status Issue
- Trusted-MAC Geofencing Issues
- DNS Issues from DC LAN PC
- Troubleshooting LAN Connectivity to Internet via WAN, Remote Branch LAN, or Local Branch LAN
- NetBalancer gateways displaying Faulty/Inactive
- Packet Drop Issues
-
-
zTC
-
- Articles coming soon
-
StorTrends
-
zAccess
-
zGuardian
You are here:
Print
Gateways
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
Quick Overview
Gateways in zAccess define the logical routing points through which endpoint traffic is processed and directed. Each gateway is typically tied to one or more Subnet Groups, allowing application requests from endpoint devices to be securely routed through the proper network path. Gateways serve as policy enforcement points, traffic routers, and optional breakout nodes.
How to Use This Feature in the UI
- Navigate to Network Configuration > Gateways in the zAccess UI.
- Click ADD GATEWAY.
- Provide a Gateway Name (e.g., “Atlanta Gateway” or “Remote Office Router”).
- Optionally, enter metadata such as:
- WAN/LAN IPs
- Device Type or Model
- Gateway Group (if applicable)
- Select one or more Subnet Groups to associate with this gateway.
- Click Save to finalize the configuration.
Concepts & Use Cases
- Traffic Routing: Gateways determine how application traffic from endpoints is routed across internal or external networks.
- Policy Enforcement Points: All policies, once applied via rulesets, are enforced at the gateway level.
- Geographic Optimization: Deploy gateways near end users to reduce latency and optimize application performance.
- Breakout Control: Use specific gateways to allow or restrict internet or SaaS breakout traffic.
- High Availability: Use multiple gateways in a group to provide redundancy for critical access zones.
Troubleshooting & FAQs
- Why is a gateway not routing traffic as expected?
Check that the gateway is online and correctly associated with the relevant subnet and policy configuration. Also confirm the endpoint is in the expected IP range. - Can multiple gateways share the same subnet?
Yes, but care must be taken to avoid routing conflicts. This setup is useful in load-balanced or HA configurations. - How do I know if a gateway is being used?
View Endpoint Sessions to see the assigned gateway per session or check Event Logs for connection routing activity. - Can I update a gateway without reassigning all subnet groups?
Yes. You can edit gateway details directly and modify subnet assignments as needed without deleting existing relationships.
Was this article helpful?
0 out Of 5 Stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |
5
Table of Contents