Roderick_Graham
Sep 16, 2015Nimbostratus
APM Network Access Split Tunnel: Not Seeing Lease Pool IP in tcpdump
I have an APM network access split-tunnel that uses a lease pool that contains only one IP address.
The destination resource (an internal VIP) is defined in the "network access-launch applications-path\parameter" field by the domain name that resolves to the internal VIP address.
Everything appears to be working however when I run a tcpdump against the internal VIP while connecting via the external VIP configured with the access policy the IP I see connecting to the internal VIP is my LAN IP address (instead of the lease pool IP address).
Any idea(s) why I wouldn't be seeing the lease pool IP address as the source IP (instead of my usual, dhcp-assigned LAN IP address)?