<?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 Re: ASA VPN user communication problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308608#M825411</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This will allow vpn clients (10.144.x.x) to access the dmz as required. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list no_nat0&lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.191.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.190.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow vpn clients (10.144.x.x0 to access the internet via hairpin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;nat (outside) 1 10.144.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And this may allow your vpn clients to communicate with each other...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (outside) 0 access-list nat0outside&lt;/P&gt;&lt;P&gt;access-list nat0outside extended permit ip 10.144.0.0 255.255.0.0 10.144.0.0 255.255.0.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Oct 2009 13:59:17 GMT</pubDate>
    <dc:creator>acomiskey</dc:creator>
    <dc:date>2009-10-09T13:59:17Z</dc:date>
    <item>
      <title>ASA VPN user communication problem</title>
      <link>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308607#M825406</link>
      <description>&lt;P&gt;We use ASA 5520's for firewalling and VPN.  When users are connected to VPN they are unable to communicate with each other.  If i remove the nat associated with the outside interface all works well and they are able to communicate.  Only problem is that they can no longer hairpin and use the ASA for internet access.  I tried to apply and ACL to the nat but denies aren't allowed.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA# sh run nat&lt;/P&gt;&lt;P&gt;nat (outside) 1 10.144.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list no_nat0&lt;/P&gt;&lt;P&gt;nat (dmz) 1 172.16.0.0 255.240.0.0&lt;/P&gt;&lt;P&gt;nat (dmz) 1 10.0.0.0 255.0.0.0&lt;/P&gt;&lt;P&gt;ASA# sh run global&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip 10.144.191.0 255.255.255.0 any log &lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip 10.144.190.0 255.255.255.0 any log &lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.190.0 255.255.255.0 log &lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.191.0 255.255.255.0 l&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated.  Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308607#M825406</guid>
      <dc:creator>Darren Sasso</dc:creator>
      <dc:date>2019-03-13T00:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: ASA VPN user communication problem</title>
      <link>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308608#M825411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This will allow vpn clients (10.144.x.x) to access the dmz as required. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (dmz) 0 access-list no_nat0&lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.191.0 255.255.255.0&lt;/P&gt;&lt;P&gt;access-list no_nat0 extended permit ip any 10.144.190.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow vpn clients (10.144.x.x0 to access the internet via hairpin.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;nat (outside) 1 10.144.0.0 255.255.0.0&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And this may allow your vpn clients to communicate with each other...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (outside) 0 access-list nat0outside&lt;/P&gt;&lt;P&gt;access-list nat0outside extended permit ip 10.144.0.0 255.255.0.0 10.144.0.0 255.255.0.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Oct 2009 13:59:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308608#M825411</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2009-10-09T13:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: ASA VPN user communication problem</title>
      <link>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308609#M825417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok great i'll give that a try.  Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Oct 2009 14:10:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-vpn-user-communication-problem/m-p/1308609#M825417</guid>
      <dc:creator>Darren Sasso</dc:creator>
      <dc:date>2009-10-09T14:10:49Z</dc:date>
    </item>
  </channel>
</rss>

