<?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 Redirect traffic through FTD in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773440#M132614</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a couple of web server in my network which accessible from outside also from inside, I am trying to force on vlan to access this servers from outside, but whenever the request from this vlan hit the FTD it resolve the egress interface and use the private ip of the server (Inside-Zone), is there anyway to force this vlan to access the server from outside only ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here is the packet tracer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Phase: 1&lt;BR /&gt;Type: CAPTURE&lt;BR /&gt;Subtype: &lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0623af40, priority=13, domain=capture, deny=false&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=195571, user_data=0xff65d31360, cs_id=0x0, l3_type=0x0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=Wireless, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Phase: 2&lt;BR /&gt;Type: ACCESS-LIST&lt;BR /&gt;Subtype: &lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Implicit Rule&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0610be40, priority=1, domain=permit, deny=false&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=71899, user_data=0x0, cs_id=0x0, l3_type=0x8&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst mac=0000.0000.0000, mask=0100.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=Wireless, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Phase: 3&lt;BR /&gt;Type: ROUTE-LOOKUP&lt;BR /&gt;Subtype: Resolve Egress Interface&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;found next-hop &lt;STRONG&gt;192.168.1.80&lt;/STRONG&gt; using egress ifc&amp;nbsp; Inside&lt;BR /&gt;&lt;BR /&gt;Phase: 4&lt;BR /&gt;Type: ACCESS-LIST&lt;BR /&gt;Subtype: log&lt;BR /&gt;Result: DROP&lt;BR /&gt;Config:&lt;BR /&gt;access-group CSM_FW_ACL_ global&lt;BR /&gt;access-list CSM_FW_ACL_ advanced deny ip ifc Wireless any ifc Inside any rule-id 268435721 event-log flow-start &lt;BR /&gt;access-list CSM_FW_ACL_ remark rule-id 268435721: ACCESS POLICY: NISR-Policy - Mandatory&lt;BR /&gt;access-list CSM_FW_ACL_ remark rule-id 268435721: L4 RULE: Block access to sales&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0ed2ffe0, priority=12, domain=permit, deny=true&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=6344, user_data=0xffa8552300, cs_id=0x0, use_real_addr, flags=0x0, protocol=0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src ip/id=0.0.0.0, mask=0.0.0.0, port=0, tag=any, ifc=Wireless&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst ip/id=0.0.0.0, mask=0.0.0.0, port=0, tag=any, ifc=Inside, vlan=0, dscp=0x0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=any, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Result:&lt;BR /&gt;input-interface: Wireless&lt;BR /&gt;input-status: up&lt;BR /&gt;input-line-status: up&lt;BR /&gt;output-interface: Inside&lt;BR /&gt;output-status: up&lt;BR /&gt;output-line-status: up&lt;BR /&gt;Action: drop&lt;BR /&gt;Drop-reason: (acl-drop) Flow is denied by configured rule&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 16:37:59 GMT</pubDate>
    <dc:creator>muath1987</dc:creator>
    <dc:date>2020-02-21T16:37:59Z</dc:date>
    <item>
      <title>Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773440#M132614</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a couple of web server in my network which accessible from outside also from inside, I am trying to force on vlan to access this servers from outside, but whenever the request from this vlan hit the FTD it resolve the egress interface and use the private ip of the server (Inside-Zone), is there anyway to force this vlan to access the server from outside only ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here is the packet tracer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Phase: 1&lt;BR /&gt;Type: CAPTURE&lt;BR /&gt;Subtype: &lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0623af40, priority=13, domain=capture, deny=false&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=195571, user_data=0xff65d31360, cs_id=0x0, l3_type=0x0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=Wireless, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Phase: 2&lt;BR /&gt;Type: ACCESS-LIST&lt;BR /&gt;Subtype: &lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Implicit Rule&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0610be40, priority=1, domain=permit, deny=false&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=71899, user_data=0x0, cs_id=0x0, l3_type=0x8&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src mac=0000.0000.0000, mask=0000.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst mac=0000.0000.0000, mask=0100.0000.0000&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=Wireless, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Phase: 3&lt;BR /&gt;Type: ROUTE-LOOKUP&lt;BR /&gt;Subtype: Resolve Egress Interface&lt;BR /&gt;Result: ALLOW&lt;BR /&gt;Config:&lt;BR /&gt;Additional Information:&lt;BR /&gt;found next-hop &lt;STRONG&gt;192.168.1.80&lt;/STRONG&gt; using egress ifc&amp;nbsp; Inside&lt;BR /&gt;&lt;BR /&gt;Phase: 4&lt;BR /&gt;Type: ACCESS-LIST&lt;BR /&gt;Subtype: log&lt;BR /&gt;Result: DROP&lt;BR /&gt;Config:&lt;BR /&gt;access-group CSM_FW_ACL_ global&lt;BR /&gt;access-list CSM_FW_ACL_ advanced deny ip ifc Wireless any ifc Inside any rule-id 268435721 event-log flow-start &lt;BR /&gt;access-list CSM_FW_ACL_ remark rule-id 268435721: ACCESS POLICY: NISR-Policy - Mandatory&lt;BR /&gt;access-list CSM_FW_ACL_ remark rule-id 268435721: L4 RULE: Block access to sales&lt;BR /&gt;Additional Information:&lt;BR /&gt;&amp;nbsp;Forward Flow based lookup yields rule:&lt;BR /&gt;&amp;nbsp;in&amp;nbsp; id=0xff0ed2ffe0, priority=12, domain=permit, deny=true&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;hits=6344, user_data=0xffa8552300, cs_id=0x0, use_real_addr, flags=0x0, protocol=0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;src ip/id=0.0.0.0, mask=0.0.0.0, port=0, tag=any, ifc=Wireless&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;dst ip/id=0.0.0.0, mask=0.0.0.0, port=0, tag=any, ifc=Inside, vlan=0, dscp=0x0&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &amp;nbsp;input_ifc=any, output_ifc=any&lt;BR /&gt;&lt;BR /&gt;Result:&lt;BR /&gt;input-interface: Wireless&lt;BR /&gt;input-status: up&lt;BR /&gt;input-line-status: up&lt;BR /&gt;output-interface: Inside&lt;BR /&gt;output-status: up&lt;BR /&gt;output-line-status: up&lt;BR /&gt;Action: drop&lt;BR /&gt;Drop-reason: (acl-drop) Flow is denied by configured rule&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:37:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773440#M132614</guid>
      <dc:creator>muath1987</dc:creator>
      <dc:date>2020-02-21T16:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773459#M132615</link>
      <description>&lt;P&gt;As long as they FTD is running routed interfaces, the system will always use the best known route for egress. You cannot force the traffic to go through the appliance to the outside interface and then "turn around" and re-enter the appliance.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 12:50:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773459#M132615</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-01-05T12:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773470#M132616</link>
      <description>&lt;P&gt;Thank you Marvin, is there any work around can help here ?&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 13:42:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773470#M132616</guid>
      <dc:creator>muath1987</dc:creator>
      <dc:date>2019-01-05T13:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773475#M132617</link>
      <description>&lt;P&gt;There's often some way we can "hack" a technical solution.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What's the underlying functional requirement that you're trying to achieve?&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 14:17:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773475#M132617</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-01-05T14:17:46Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773477#M132618</link>
      <description>&lt;P&gt;I am only looking to allow web browsing for those servers from outside just to keep this VLAN totally isolated from internal network.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 14:23:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773477#M132618</guid>
      <dc:creator>muath1987</dc:creator>
      <dc:date>2019-01-05T14:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: Redirect traffic through FTD</title>
      <link>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773478#M132619</link>
      <description>&lt;P&gt;Since you are going to allow access to those servers why not just put in ACP rules to permit that specific access and block all other access?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That would be a standard way of handling it and not incur the technical debt of a more complex solution.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Jan 2019 14:28:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/redirect-traffic-through-ftd/m-p/3773478#M132619</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-01-05T14:28:10Z</dc:date>
    </item>
  </channel>
</rss>

