<?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: Controlling VPN client access on pix in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376753#M1059644</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i will try to make some acls matchingthe intersting traffic on the inside interface , the sysopt command only overwrites the acl on the outside interface &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Jan 2005 23:55:16 GMT</pubDate>
    <dc:creator>carlogon</dc:creator>
    <dc:date>2005-01-18T23:55:16Z</dc:date>
    <item>
      <title>Controlling VPN client access on pix</title>
      <link>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376751#M1059639</link>
      <description>&lt;P&gt;Does anyone have any idea on controlling VPN client access once they get connected thru VPN (PIX).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried using access-list but it does not filter out correct as defined by ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:44:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376751#M1059639</guid>
      <dc:creator>jeffrey.chong</dc:creator>
      <dc:date>2020-02-21T07:44:57Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling VPN client access on pix</title>
      <link>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376752#M1059641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The sysopt permit Ipsec will overide the acls on the interfaces for your vpn traffic.  You will need to take the sysopt out.  Then on the outside interface build your ACL to allow isakmp and ESP/AH traffic.  Once you do that you can now limit your traffic per ACL on the outside or inside interface.  That it is up to you and your security policy.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Nov 2004 15:48:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376752#M1059641</guid>
      <dc:creator>jay_colby</dc:creator>
      <dc:date>2004-11-16T15:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Controlling VPN client access on pix</title>
      <link>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376753#M1059644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i will try to make some acls matchingthe intersting traffic on the inside interface , the sysopt command only overwrites the acl on the outside interface &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Jan 2005 23:55:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/controlling-vpn-client-access-on-pix/m-p/376753#M1059644</guid>
      <dc:creator>carlogon</dc:creator>
      <dc:date>2005-01-18T23:55:16Z</dc:date>
    </item>
  </channel>
</rss>

