<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic  Hi,Can you try with an in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550970#M206584</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can you try with an extended acl, like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list acl_splitvpn extended permit ip external_ip 255.255.255.255 any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pedro Lereno&lt;/P&gt;</description>
    <pubDate>Fri, 10 Oct 2014 16:24:20 GMT</pubDate>
    <dc:creator>Pedro Lereno</dc:creator>
    <dc:date>2014-10-10T16:24:20Z</dc:date>
    <item>
      <title>Client VPN access to Public IP</title>
      <link>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550967#M206581</link>
      <description>&lt;P&gt;Hi, the&amp;nbsp;requirement here is to provide access to a website hosted behind a PIX 515e (version 7 software) via a Cisco VPN client. The client will need to access the website via the "external" IP address of the site,&amp;nbsp;rather than the internal. We currently have Client VPN configurations in place to allow access to servers via the internal IP address, but not via the external( public) address.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help with the above would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:50:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550967#M206581</guid>
      <dc:creator>WelcomEIB</dc:creator>
      <dc:date>2019-03-12T04:50:23Z</dc:date>
    </item>
    <item>
      <title>Hi,From your explanation it</title>
      <link>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550968#M206582</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;From your explanation it seems that you have a "nat exempt" rule to your vpn clients, so they access the servers via the internal IP and not the public ("natted") one.&lt;/P&gt;&lt;P&gt;A possible solution:&lt;/P&gt;&lt;P&gt;1. Disable nat exempt rule and all vpn clients must access to the public ip of the server.&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;2. Create a new address-pool, associate to a vpngroup, and not exempt nat. Example:&lt;/P&gt;&lt;P&gt;ip local pool OUT_IP 192.168.130.1-192.168.130.255&lt;/P&gt;&lt;P&gt;vpngroup PUBLICIPACCESS address-pool OUT_IP&lt;/P&gt;&lt;P&gt;vpngroup&amp;nbsp;PUBLICIPACCESS&amp;nbsp; password&amp;nbsp; xxxxxxxxxx&lt;/P&gt;&lt;P&gt;access-list outside_access_in permit ip 192.168.130.0 255.255.255.0 any&lt;/P&gt;&lt;P&gt;access-list outside_cryptomap_dyn_20 permit ip any 192.168.130.0 255.255.255.0&lt;BR /&gt;crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20&lt;BR /&gt;crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-SHA&lt;BR /&gt;crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map&lt;/P&gt;&lt;P&gt;(attention to the the name and order of the acls and crypto maps)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this could help you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pedro Lereno&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2014 13:25:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550968#M206582</guid>
      <dc:creator>Pedro Lereno</dc:creator>
      <dc:date>2014-09-30T13:25:13Z</dc:date>
    </item>
    <item>
      <title>Hi, Thanks for your feedback</title>
      <link>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550969#M206583</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your feedback on this. The VPN configuration is in place and working as per your suggestion.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only item that isn't working well as the split tunnelling. So without split tunnelling the external IP address is accessible, however this will route ALL client traffic through the VPN tunnel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The split tunnelling config is as follows:&lt;/P&gt;&lt;P&gt;access-list acl_splitvpn standard&amp;nbsp;permit ip external_ip 255.255.255.255&lt;/P&gt;&lt;P&gt;group-policy gp_name attributes&lt;BR /&gt;&amp;nbsp; split-tunnel-policy tunnelspecified&lt;BR /&gt;&amp;nbsp; split-tunnel-network-list value acl_splitvpn&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any further assistance would be appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2014 11:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550969#M206583</guid>
      <dc:creator>WelcomEIB</dc:creator>
      <dc:date>2014-10-08T11:24:07Z</dc:date>
    </item>
    <item>
      <title> Hi,Can you try with an</title>
      <link>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550970#M206584</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can you try with an extended acl, like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list acl_splitvpn extended permit ip external_ip 255.255.255.255 any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pedro Lereno&lt;/P&gt;</description>
      <pubDate>Fri, 10 Oct 2014 16:24:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/client-vpn-access-to-public-ip/m-p/2550970#M206584</guid>
      <dc:creator>Pedro Lereno</dc:creator>
      <dc:date>2014-10-10T16:24:20Z</dc:date>
    </item>
  </channel>
</rss>

