Forward error correction (FEC) is a technique for controlling data transmission errors over unreliable or noisy communication channels. With FEC, the sender encodes messages with a little extra error-correcting code. FEC enables recovery of lost packets to avoid retransmission and increase throughput on lossy links. FEC is frequently used when retransmission is not possible or is costly.
In Access Policy Manager®, you can use FEC on network access tunnels. You can do this provided that you configure a network access resource for Datagram Transport Level Security (DTLS) and configure two virtual servers with the same IP address. Users connect on a TCP/HTTPS virtual server. Another virtual server handles DTLS for the network access resource.
|Network Access||Select Network Access for a webtop to which you will assign only a single network access resource.|
|Portal Access||Select Portal Access for a webtop to which you assign only portal access resources.|
|Full||Select Full for a webtop to which you assign one or more network access resources, multiple portal access resources, and multiple application access app tunnel resources, or any combination of the three types.|
|Resource Assign||Select the Resource Assign action to add a network access resource only. Resource Assign does not allow you to add a webtop or ACLs. If you want to add ACLs, a webtop, or webtop links after you add a Resource Assign action, you can add them with the individual actions ACL Assign and Webtop and Links Assign.|
|Advanced Resource Assign||Select the Advanced Resource Assign action to add network access resources, and optionally add a webtop, webtop links, and one or more ACLs.|
Network settings specify tunnel settings, session settings, and client settings.
|Network Tunnel||Enable||When you enable a network tunnel, you configure the network access tunnel to provide network access. Clear the Enable option to hide all network settings and to disable the tunnel.|
|Supported IP Version||IPV4 or IPV4&IPV6||Sets the Network Access tunnel to support either an IPv4 lease pool, or
both IPv4 and IPv6 lease pools.
Important: Network access with IPv6 alone is not supported. An IPv6 tunnel requires a simultaneous IPv4 tunnel, which is automatically established when you assign IPv4 and IPv6 lease pools, and set the version to IPv4&IPv6.
|General Settings||Basic/Advanced||Select Advanced to show settings for Proxy ARP, SNAT Pool, and Session Update.|
|IPv4 Lease Pool||List selection of existing IPv4 lease pools||Assigns internal IP addresses to remote network access clients, using configured lease pools. Select a lease pool from the drop-down list. To create a lease pool within this screen, click the + sign next to Lease Pool.|
|IPv6 Lease Pool||List selection of existing IPv6 lease pools||Assigns internal IP addresses to remote network access clients, using configured lease pools. Select a lease pool from the drop-down list. To create a lease pool within this screen, click the + sign next to Lease Pool.|
|Compression||No Compression/GZIP Compression||Select GZIP Compression to compress all traffic between the Network Access client and the Access Policy Manager®, using the GZIP deflate method.|
|Proxy ARP||Enable||Proxy ARP allows remote clients to use IP addresses from the LAN IP subnet, and no configuration changes are required on other devices such as routers, hosts, or firewalls. IP address ranges on the LAN subnet are configured in a lease pool and assigned to network access tunnel clients. When this setting is enabled, a host on the LAN that sends an ARP query for a client address gets a response from Access Policy Manager with its own MAC address. Traffic is sent to the Access Policy Manager and forwarded to clients over network access tunnels.|
|SNAT Pool||List selection of None, Auto Map, or SNAT pool name||Specifies the name of a SNAT pool used for implementing selective and
intelligent SNATs. The default is Auto Map. If you have
defined a SNAT on the system, that SNAT is available as an option on this list.
The following two options are always available.
Note: To support CIFS/SMB and VoIP protocols, select None and configure routable IP addresses in the lease pool
|Session Update Threshold||Integer (bytes per second)||Defines the average byte rate that either ingress or egress tunnel traffic must exceed, in order for the tunnel to update a session. If the average byte rate falls below the specified threshold, the system applies the inactivity timeout, which is defined in the Access Profile, to the session.|
|Session Update Window||Integer (seconds)||Defines the time value in seconds that the system uses to calculate the EMA (Exponential Moving Average) byte rate of ingress and egress tunnel traffic.|
|Client Settings||Basic/Advanced||Select Advanced to configure client proxy, DTLS, domain reconnect settings, and client certificate options.|
|Force all traffic through tunnel||Enable/disable||Specifies that all traffic (including traffic to or from the local subnet) is forced over the VPN tunnel.|
|Use split tunneling for traffic||Enable/disable||Specifies that only the traffic targeted to a specified address space is sent over the network access tunnel. With split tunneling, all other traffic bypasses the tunnel. By default, split tunneling is not enabled. When split tunneling is enabled, all traffic passing over the network access connection uses this setting.|
|IPV4 LAN Address Space||IPv4 IP address, IP address and network mask||Provides a list of addresses or address/mask pairs describing the target LAN. When using split tunneling, only the traffic to these addresses and network segments goes through the tunnel configured for Network Access. You can add multiple address spaces to the list, one at a time. For each address space, type the IP address and the network mask and click Add.|
|IPV6 LAN Address Space||IPv6 IP address, IP address and network mask||Provides a list of IPv6 addresses or address/mask pairs describing the target LAN. When using split tunneling, only the traffic to these addresses and network segments goes through the tunnel configured for Network Access. You can add multiple address spaces to the list, one at a time. For each address space, type the IP address and the network mask and click Add. This list appears only when you select IPV4&IPV6 in the Supported IP Version setting.|
|DNS Address Space||domain names, with or without wildcards||Provides a list of domain names describing the target LAN DNS addresses. This field only appears if you use split tunneling. You can add multiple address spaces to the list, one at a time. For each address space, type the domain name, in the form site.siterequest.com or *.siterequest.com, and click Add.|
|Exclude Address Space||IP address/network mask pairs||Specifies address spaces whose traffic is not forced through the tunnel. For each address space that you want to exclude, type the IP address and the network mask and click Add.|
|Allow Local Subnet||Enable/disable||Select this option to enable local subnet access and local access to any host or subnet in routes that you have specified in the client routing table. When you enable this setting, the system does not support integrated IP filtering.|
|Client Side Security > Prohibit routing table changes during Network Access connection||Enable/disable||This option closes the network access session if the client's IP routing table is modified during the session.|
|Client Side Security > Integrated IP filtering engine||Enable/disable||Select this option to protect the resource from outside traffic (traffic generated by network devices on the client's LAN), and to ensure that the resource is not leaking traffic to the client's LAN.|
|Client Side Security > Allow access to local DHCP server||Enable/disable||This option appears when the Integrated IP filtering
engine option is enabled. This option allows the client access
to connect through the IP filtering engine, to use a DHCP server local to the
client to renew the client DHCP lease locally. This option is not required or
available when IP filtering is not enabled, because clients can renew their
Important: This option does not renew the DHCP lease for the IP address assigned from the network access lease pool; this applies only to the local client IP address.
|Client Traffic Classifier||List selection||Specifies a client traffic classifier to use with this network access tunnel, for Windows clients.|
|Client Options > Client for Microsoft Networks||Enable/disable||Select this option to allow the client PC to access remote resources over a VPN connection. This option is enabled by default. This allows the VPN to work like a traditional VPN, so a user can access files and printers from the remote Microsoft network.|
|Client Options > File and printer sharing for Microsoft networks||Enable/disable||Select this option to allow remote hosts to access shared resources on the client computer over the network access connection. This allows the VPN to work in reverse, and a VPN user to share file shares and printers with remote LAN users and other VPN users.|
|Provide client certificate on Network Access connection when requested||Enable/disable||If client certificates are required to establish an SSL connection, this option must always be enabled. However, you can disable this option if the client certificates are only requested in an SSL connection. In this case, the client is configured not to send client certificates.|
|Reconnect to Domain > Synchronize with Active Directory policies on connection establishment||Enable/disable||When enabled, this option emulates the Windows logon process for a client
on an Active Directory domain. Network policies are synchronized when the
connection is established, or at logoff. The following items are synchronized:
|Reconnect to Domain > Run logoff scripts on connection termination||Enable/disable||This option appears when Synchronize with Active Directory policies on connection establishment is enabled. Enable this option if you want the system to run logoff scripts, as configured on the Active Directory domain, when the connection is stopped.|
|Client Interface Speed||Integer, bits per second||Specifies the maximum speed of the client interface connection, in bits per second.|
|Display connection tray icon||Enable/disable||When enabled, balloon notifications for the network access tray icon (for example, when a connection is made) are displayed. Disable this option to prevent balloon notifications.|
|Client Power Management||Ignore, Prevent, or Terminate||Specifies how network access handles client power management settings, for
example, when the user puts the system in standby, or closes the lid on a laptop.
|DTLS||Enable/disable||Specifies, when enabled, that the network access connection uses Datagram Transport Level Security (DTLS). DTLS uses UDP instead of TCP, to provides better throughput for high-demand applications like VoIP or streaming video, especially with lossy connections.|
|DTLS Port||Port number||Specifies the port number that the network access resource uses for secure UDP traffic with DTLS. The default is 4433.|
|Client Proxy Settings||Enable/disable||When selected, provides configuration settings for client proxy connections for this network access resource.|
|Client Proxy Uses HTTP for Proxy Autoconfig Script||Enable/disable||Some applications, like Citrix® MetaFrame, can not use the client proxy autoconfig script when the browser attempts to use the file:// prefix to locate it. Select this option to specify that the browser uses http:// to locate the proxy autoconfig file, instead of file://.|
|Client Proxy Autoconfig Script||URL||The URL for a proxy auto-configuration script, if one is used with this connection.|
|Client Proxy Address||IP address||The IP address for the client proxy server that network access clients use to connect to the Internet.|
|Client Proxy Port||Port number||The port number of the proxy server that network access clients use to connect to the Internet.|
|Bypass Proxy For Local Addresses||Enable/disable||Select this option if you want to allow local intranet addresses to bypass the proxy server.|
|Client Proxy Exclusion List||IP addresses, domain names, with wildcards||Specifies the web addresses that do not need to be accessed through your proxy server. You can use wildcards to match domain and host names, or addresses. For example, www.*.com, 128.*, 240.8, 8., mygroup.*, *.*.|