<?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: Pix 506e - conduit command in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692119#M1035382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes indeed, but it's still recommended to have it specified there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Nov 2006 15:49:18 GMT</pubDate>
    <dc:creator>a.kiprawih</dc:creator>
    <dc:date>2006-11-21T15:49:18Z</dc:date>
    <item>
      <title>Pix 506e - conduit command</title>
      <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692115#M1035368</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the process of building a pix 515e to replace my 506e. Below is part of the current 506 configuration. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx  eq ssh any&lt;/P&gt;&lt;P&gt;conduit permit udp host xxx.xxx.xxx.xxx host xxx.xxx.xxx.xxx  eq syslog&lt;/P&gt;&lt;P&gt;conduit permit icmp any any&lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx  eq smtp any&lt;/P&gt;&lt;P&gt;conduit permit udp host xxx.xxx.xxx.xxx  eq 1812 any&lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx eq 3101 any&lt;/P&gt;&lt;P&gt;conduit deny tcp any eq 6129 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I undertsand that the conduit command is no longer available in later IOS versions (the 515e is running version 7.0{5}), can anyone advise me on what alternative commands I now need to use use?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:58:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692115#M1035368</guid>
      <dc:creator>johnnymac</dc:creator>
      <dc:date>2019-03-11T08:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 506e - conduit command</title>
      <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692116#M1035370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alternative option for Conduit is to use access-list (ACL).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conduit does not give you ability to specify where/ports you should apply the restriction, while ACL provide flexible and more options to control and where to apply the ACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conduit command goes by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conduit &lt;PERMIT&gt; &lt;PROTOCOL&gt; &lt;LOCAL internal=""&gt; eq &lt;PORT&gt; &lt;ACCESS by="" who=""&gt;&lt;/ACCESS&gt;&lt;/PORT&gt;&lt;/LOCAL&gt;&lt;/PROTOCOL&gt;&lt;/PERMIT&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACL command structure:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list &lt;ACL_NAME&gt; &lt;PERMIT&gt; &lt;PROTOCOL&gt; &lt;SOURCE ip=""&gt; &lt;DESTINATION ip=""&gt; eq &lt;PORT&gt;&lt;/PORT&gt;&lt;/DESTINATION&gt;&lt;/SOURCE&gt;&lt;/PROTOCOL&gt;&lt;/PERMIT&gt;&lt;/ACL_NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on your conduit config, it control access from outside/internet to your xxx.xxx.xxx.xxx server (I assumed this is public IP for the server).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore, the ACL version of it shoud be as follow (line by line):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Existing conduit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx eq ssh any --&amp;gt; allow any to access xxx.xxx.xxx.xxx IP. Same goes to others.&lt;/P&gt;&lt;P&gt;conduit permit udp host xxx.xxx.xxx.xxx host xxx.xxx.xxx.xxx eq syslog &lt;/P&gt;&lt;P&gt;conduit permit icmp any any &lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx eq smtp any &lt;/P&gt;&lt;P&gt;conduit permit udp host xxx.xxx.xxx.xxx eq 1812 any &lt;/P&gt;&lt;P&gt;conduit permit tcp host xxx.xxx.xxx.xxx eq 3101 any &lt;/P&gt;&lt;P&gt;conduit deny tcp any eq 6129 any &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*New ACL - apply/bind on Outside interface/port:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside permit tcp any host xxx.xxx.xxx.xxx eq ssh&lt;/P&gt;&lt;P&gt;access-list outside permit udp host xxx.xxx.xxx.xxx host xxx.xxx.xxx.xxx eq syslog &lt;/P&gt;&lt;P&gt;access-list outside permit icmp any any &lt;/P&gt;&lt;P&gt;access-list outside permit tcp host xxx.xxx.xxx.xxx eq smtp&lt;/P&gt;&lt;P&gt;access-list outside permit udp host xxx.xxx.xxx.xxx eq 1812 &lt;/P&gt;&lt;P&gt;access-list outside permit tcp host xxx.xxx.xxx.xxx eq 3101 &lt;/P&gt;&lt;P&gt;access-list outside deny tcp any any eq 6129 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure your PIX has default route to internet router, i.e:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.1  --&amp;gt; your internet router IP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Conduit/outbound notice:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_field_notice09186a00801d3621.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_field_notice09186a00801d3621.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Access-list &amp;amp; COnduit Ref:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094aad.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a0080094aad.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps. Pls rate all useful post(s).&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2006 10:31:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692116#M1035370</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-21T10:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 506e - conduit command</title>
      <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692117#M1035374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, for the new ACL entries, I recommend to use 'deny ip any any' to deny all unwanted IP (TCP/UDP).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, the last line (with deny statement) will be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside deny ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2006 10:36:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692117#M1035374</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-21T10:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 506e - conduit command</title>
      <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692118#M1035378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks thats very concise. Won't the access list have an implicit deny any any statement at the end of the access list by default?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2006 10:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692118#M1035378</guid>
      <dc:creator>johnnymac</dc:creator>
      <dc:date>2006-11-21T10:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Pix 506e - conduit command</title>
      <link>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692119#M1035382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes indeed, but it's still recommended to have it specified there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2006 15:49:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-506e-conduit-command/m-p/692119#M1035382</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-11-21T15:49:18Z</dc:date>
    </item>
  </channel>
</rss>

