jerome_itable Lv2Posted 17 Jan 2024 08:09
  
Understanding the Problem:

    Missing Zone Assignment: SSLVPN interface lacks a zone, preventing SNAT from working for WAN access.
    Desired Outcome: Enable SSLVPN clients to access the cloud server through the WAN.

Solutions:

1. Assign SSLVPN Interface to a Zone (Ideal Approach):

    Check NGAF Documentation: Consult NGAF documentation for specific instructions on adding the SSLVPN interface to a suitable zone.
    Choose Appropriate Zone: Select a zone that allows traffic to the WAN (e.g., "Trusted" or "Untrusted").
    Configure SNAT: Apply SNAT rules to translate SSLVPN client IPs to the WAN IP when accessing the cloud server.

2. Alternate Solutions if Zone Assignment Isn't Supported:

    Policy-Based Routing: Create policies to route traffic from the SSLVPN interface to the WAN without relying on zones.
    Static Routes: Add static routes to direct traffic from the SSLVPN subnet to the WAN gateway.
    VPN-Based Solutions: Consider establishing a VPN tunnel specifically for SSLVPN clients to access the cloud server, bypassing zone limitations.

Additional Considerations:

    Firewall Rules: Ensure firewall rules allow traffic from the SSLVPN interface to the cloud server's IP and ports.
    NAT Configuration: Double-check NAT rules for correct translation of SSLVPN client IPs to the WAN IP.
    Routing: Verify routing tables for proper routing between the SSLVPN interface, WAN interface, and cloud server.
    Security Policies: Review any security policies that might restrict access from the SSLVPN interface to the WAN.

I Can Help:

Change

Moderator on This Board

0
2
4

Started Topics

Followers

Follow

67
14
3

Started Topics

Followers

Follow

3
0
2

Started Topics

Followers

Follow

1
131
3

Started Topics

Followers

Follow

Board Leaders