Athena SWG (Secure Web Gateway)

Athena SWG (formerly Internet Access Gateway) ensures visibility and control across the network, detecting risks like unauthorized access, non-compliant activities, and data leaks to manage endpoints.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
13.0.120
{{sendMatomoQuery("Athena SWG (Secure Web Gateway)","Local Subnets")}}

Local Subnets

{{ $t('productDocDetail.updateTime') }}: 2025-12-29

List the intranet subnets of a hardware device so that VPN users can access the intranet subnets of the HQ. For example, if the HQ has to subnets (192.200.100.x and 192.200.200.x), you can set the local subnet list to enable interconnection among mobile users, branch users, and HQ intranet users. The configuration procedure is as follows:

  1. Configure the subnets that require interconnection on the Local Subnet List page. See the following figure.

Click Add and add an IP Address and Netmask.

IP Address and Netmask must be set to the network ID and subnet mask of a network segment other than the directly connected network segment of the LAN/DMZ port of the IAG at the local end.

  1. Set reachable routes for the subnets in the Static Routes window. (For details, choose System > Network > Routing.

The local subnet list acts as a statemen[LCH269][270]t. The network segments defined in the list are regarded by Sangfor 's VPN device and software client as VPN network segments. This is because all the packets intended for the network segments are encapsulated in the VPN channels for transmission when the packets reach the VPN device or software client. Therefore, if subnet segments are added to the list, static routes are required to access the subnets.