<?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 Old school command line vs. ASDM GUI in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/old-school-command-line-vs-asdm-gui/m-p/828933#M958188</link>
    <description>&lt;P&gt;I have a VPN tunnel that functions correctly, however, the technical person on the remote end is more comfortable using ASDM.  Local device is a PIX 535 w/ver 7.2(2). The remote side is an ASA 5520 w/ver 7.2(1). When the remote side is setup via GUI things do not work. After resetting remote side up using object groups and command line we can get source/destination/service port connectivity. The remote Team wants to do "VPN filters" Is this different from an ACL with source/destination/service? If so can u provide urls for review?&lt;/P&gt;</description>
    <pubDate>Wed, 13 Mar 2019 00:53:35 GMT</pubDate>
    <dc:creator>reramirez</dc:creator>
    <dc:date>2019-03-13T00:53:35Z</dc:date>
    <item>
      <title>Old school command line vs. ASDM GUI</title>
      <link>https://community.cisco.com/t5/network-security/old-school-command-line-vs-asdm-gui/m-p/828933#M958188</link>
      <description>&lt;P&gt;I have a VPN tunnel that functions correctly, however, the technical person on the remote end is more comfortable using ASDM.  Local device is a PIX 535 w/ver 7.2(2). The remote side is an ASA 5520 w/ver 7.2(1). When the remote side is setup via GUI things do not work. After resetting remote side up using object groups and command line we can get source/destination/service port connectivity. The remote Team wants to do "VPN filters" Is this different from an ACL with source/destination/service? If so can u provide urls for review?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:53:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/old-school-command-line-vs-asdm-gui/m-p/828933#M958188</guid>
      <dc:creator>reramirez</dc:creator>
      <dc:date>2019-03-13T00:53:35Z</dc:date>
    </item>
    <item>
      <title>Re: Old school command line vs. ASDM GUI</title>
      <link>https://community.cisco.com/t5/network-security/old-school-command-line-vs-asdm-gui/m-p/828934#M958189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rene&lt;/P&gt;&lt;P&gt;  Following also applies to L2L VPN tunnels. But instead modifying defaultl2l group-policy, ask them to create a new group policy and set the tunnel use this policy&lt;/P&gt;&lt;P&gt;  tunnel-group xxx general-attrib&lt;/P&gt;&lt;P&gt;  default-group-policy createdgrouppolicy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a0080641a52.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a0080641a52.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 00:07:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/old-school-command-line-vs-asdm-gui/m-p/828934#M958189</guid>
      <dc:creator>Alan Huseyin Kayahan</dc:creator>
      <dc:date>2007-12-21T00:07:06Z</dc:date>
    </item>
  </channel>
</rss>

