<?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: Block traffic while allowing Passive FTP in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378808#M6587</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.  That's the last piece of the puzzle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Dec 2004 23:05:56 GMT</pubDate>
    <dc:creator>mromer</dc:creator>
    <dc:date>2004-12-13T23:05:56Z</dc:date>
    <item>
      <title>Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378805#M6584</link>
      <description>&lt;P&gt;We've got two subnets sitting behind a redundant pair of CSS 11050's.  I need to block traffic between the two subnets (one contains our stuff, and the other contains stuff we're hosting for another company).  I can use an ACL to do this, but it seems that any sort of ACL will prevent servers on either subnet from making outbound passive FTP connections.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ref: "Understanding and Configuring FTP on the CSS 11000"&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/customer/products/hw/contnetw/ps789/products_tech_note09186a0080093de6.shtml" target="_blank"&gt;http://www.cisco.com/en/US/customer/products/hw/contnetw/ps789/products_tech_note09186a0080093de6.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each subnet is on a separate VLAN on the CSS, with a third VLAN for the uplink to the PIX firewall.  All traffic between VLANs is bridged through the CSS--no one-arm setups.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way I can prevent communication between the two internal VLANs while allowing outbound passive FTP from each?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2004 21:35:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378805#M6584</guid>
      <dc:creator>mromer</dc:creator>
      <dc:date>2004-12-13T21:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378806#M6585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like I panicked too soon.  The problem appears to only come up if I NAT across the CSS.  If I don't NAT, I can do outbound passive FTP and still keep the ACL in place.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Dec 2004 22:31:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378806#M6585</guid>
      <dc:creator>mromer</dc:creator>
      <dc:date>2004-12-13T22:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378807#M6586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can do this by using ACL's and Source Groups separately (i.e. - don't use an ACL to map traffic into a Source Group). Ex:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN10 = 10.10.10.0/24&lt;/P&gt;&lt;P&gt;Services: VLAN10-1, VLAN10-2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VLAN11 = 10.10.11.0/24&lt;/P&gt;&lt;P&gt;Services: VLAN11-1, VLAN11-2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!--Write some ACL's to block traffic&lt;/P&gt;&lt;P&gt;acl 10&lt;/P&gt;&lt;P&gt;clause 5 deny any 10.10.10.0 255.255.255.0 destination 10.10.11.0 255.255.255.0&lt;/P&gt;&lt;P&gt;clause 10 permit any any destination any&lt;/P&gt;&lt;P&gt;apply circuit-(VLAN10)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;acl 11&lt;/P&gt;&lt;P&gt;clause 5 deny any 10.10.11.0 255.255.255.0 destination 10.10.10.0 255.255.255.0&lt;/P&gt;&lt;P&gt;clause 10 permit any any destination any&lt;/P&gt;&lt;P&gt;apply circuit-(VLAN11)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!--Create some src groups to NAT outbound traffic&lt;/P&gt;&lt;P&gt;group VLAN10&lt;/P&gt;&lt;P&gt;vip address x.x.x.x&lt;/P&gt;&lt;P&gt;add service VLAN10-1&lt;/P&gt;&lt;P&gt;add service VLAN10-2&lt;/P&gt;&lt;P&gt;active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group VLAN11&lt;/P&gt;&lt;P&gt;vip address y.y.y.y&lt;/P&gt;&lt;P&gt;add service VLAN11-1&lt;/P&gt;&lt;P&gt;add service VLAN11-2&lt;/P&gt;&lt;P&gt;active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Zach&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Dec 2004 22:48:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378807#M6586</guid>
      <dc:creator>seilsz</dc:creator>
      <dc:date>2004-12-13T22:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378808#M6587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.  That's the last piece of the puzzle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Dec 2004 23:05:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378808#M6587</guid>
      <dc:creator>mromer</dc:creator>
      <dc:date>2004-12-13T23:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378809#M6588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It also looks like the behavior described in the document you referenced (not being able to use an ACL to assign ftp pasv traffic to a src group) was the result of a bug (id CSCdv02486).  This was fixed in the 04.01.046, 05.00.021 and 05.01.010 code trains.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Zach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Dec 2004 23:39:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378809#M6588</guid>
      <dc:creator>seilsz</dc:creator>
      <dc:date>2004-12-13T23:39:47Z</dc:date>
    </item>
    <item>
      <title>Re: Block traffic while allowing Passive FTP</title>
      <link>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378810#M6589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, that's interesting.  I'm using 6.10.304 on the CSS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again for your help.&lt;/P&gt;&lt;P&gt;-Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Dec 2004 14:37:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/block-traffic-while-allowing-passive-ftp/m-p/378810#M6589</guid>
      <dc:creator>mromer</dc:creator>
      <dc:date>2004-12-14T14:37:05Z</dc:date>
    </item>
  </channel>
</rss>

