#Set pulse secure client mtu windows

By default the setting is always false, and therefore the TCP MSS options are always considered for MTU by default. Note: This вЂњignore-tcp-mssвЂќ setting is applicable for the virtual adapter MTU calculation only for IPv4. The advanced configuration setting 'ignore-tcp-mss' is Layer3 Adapter configuration setting and this will be consumed by the Pulse client as part of the IpsecConfig.

Enter the following XML input in 'Advanced Client Configuration for Pulse Client'.

The following figure shows the configuration page for Pulse Connect Secure.

Select System > Configuration > Advanced Client Configuration to display the configuration page.

If the administrator configures the Pulse Connect Secure sever with the following XML input in 'Advanced Client Configuration for Pulse Client' option, it will ignore TCP MSS options while calculating the virtual adapter MTU on client side. Here, customer wants to ignore the TCP MSS options while calculating the Virtual Adapter MTU calculation. In this scenario, the TCP MSS value on the Pulse client will default to a minimum value of 536, and as a result the client side MTU calculation will result in a minimum MTU value of 576.

MIN (Physical Adapter MTU, MTU from PCS, TCP MSS value + 40)ДЇollowing is a scenario where Firewall on the data path is stripping the TCP MSS options being advertised by the SA/PCS to the Pulse client.

#Set pulse secure client mtu windows

Enter the following XML input in 'Advanced Client Configuration for Pulse Client'. If the Pulse Secure Client from the Windows Store is installed on a device, the Pulse Secure Client provided by us might not. Figure shows the configuration page for Pulse Connect Secure.

prior to v5.2R2, the virtual adapter MTU was calculated based on the physical adapter MTU (of the host machine) and the MTU sent by the PCS.Д«asically, the formula used to calculate the virtual adapter MTU is: Select System > Configuration > Advanced Client Configuration to display the configuration page. In the earlier Pulse client releases, i.e. From 9.0R3 release onwards, this feature will minimize the number of changes going into the PCS admin console to fulfill the requirement of a specific customer. Pulse clients supporting these custom settings will consume them when connecting to this PCS, and the same would be applied on the client machines. Admin can set these custom settings in the form of XML input through the Advanced Client Configuration UI feature. This topic describes the XML advanced client configuration that can be used by the PCS administrator to configure the custom settings, which are meant to solve a specific customer scenario without changing the PCS admin console. You are here: Advanced Client Configuration Feature