I would imagine so, its more than likely the same as when the device is acting as a dhcp-rely across a tunnel. The request is sourced from the outside.
try add a rule to your crypto access-list that specifies the outside interface IP address to the tftp server IP address using tftp and the...
sorry..
access-list policy_nat permit ip host <ipaddress1> any
access-list policy_nat permit ip host <ipaddress2> any
access-list policy_nat permit ip host <ipaddress3> any
access-list policy_nat permit permit ip host <ipaddress1> any
access-list policy_nat permit permit ip host <ipaddress2> any
access-list policy_nat permit permit ip host <ipaddress3> any
global (outside) 15 <publicIP>
nat (inside) 15 access-list policy_nat
That seems a little weird.. Are you 100% there is nothing on the host blocking ICMP?
If you plug another host into different switchport on the ASA are you able to ping between the two hosts?
If you want internet access via a split-tunnel change your ACL to the following.
access-list seamarmexico_splitTunnelAcl standard 192.168.2.0 255.255.255.0
The public is x.x.162.232 and the private is 10.3.0.232?
i.e http://x.x.162.232 -> http://10.3.0.232
If so your config is fine, try a "clear xlate"
Confused why you mention 1.1.1.10 and 10.2.0.10 in your first post?
Your address-pool on the tunnel-group is missing
tunnel-group seamarmexico general-attributes
address-pool poolclients
Rather change your VPN address pool to a pool off your local subnet remembering to change your split-tunnel too.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.