<?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 Traffic Flow between Transparent and Routed FW. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233367#M348503</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need to confirm here the traffic flow between 2 FW.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say we have Core Switch 1&amp;nbsp; it is learning route to subnet 172.x.x.x&amp;nbsp; via interface x of Routed FW.&lt;/P&gt;&lt;P&gt;Routed FW learns Route to Destination subnet 172.x.x.x&amp;nbsp;&amp;nbsp; via its&amp;nbsp; interface Y.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now Interface Y connects to interface Y of Transparent FW.&lt;/P&gt;&lt;P&gt;Transparent FW has interface Z&amp;nbsp; which has destination subnet 172.x.x.x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in short we can say that if someone need to reach the Destination subnet 172..x.x.x&amp;nbsp; and its default gateway is core switch then traffic will follow the&lt;/P&gt;&lt;P&gt;above path to reach the subnet 172.x.x.x??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:54:17 GMT</pubDate>
    <dc:creator>mahesh18</dc:creator>
    <dc:date>2019-03-12T01:54:17Z</dc:date>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233367#M348503</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need to confirm here the traffic flow between 2 FW.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Say we have Core Switch 1&amp;nbsp; it is learning route to subnet 172.x.x.x&amp;nbsp; via interface x of Routed FW.&lt;/P&gt;&lt;P&gt;Routed FW learns Route to Destination subnet 172.x.x.x&amp;nbsp;&amp;nbsp; via its&amp;nbsp; interface Y.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now Interface Y connects to interface Y of Transparent FW.&lt;/P&gt;&lt;P&gt;Transparent FW has interface Z&amp;nbsp; which has destination subnet 172.x.x.x.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in short we can say that if someone need to reach the Destination subnet 172..x.x.x&amp;nbsp; and its default gateway is core switch then traffic will follow the&lt;/P&gt;&lt;P&gt;above path to reach the subnet 172.x.x.x??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:54:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233367#M348503</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T01:54:17Z</dc:date>
    </item>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233368#M348504</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Well,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Transparent Firewall cannot route so I would say that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interface Y of the Router FW and both interfaces on the transparent firewall on the 172.16.x.x..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That would make sense but you cannot route to a subnet via a transparent firewall IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The transparent firewall does not have a routing table to route traffic across itself.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 16:44:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233368#M348504</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-06-07T16:44:13Z</dc:date>
    </item>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233369#M348505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are correct as transparent FW is just layer 2 and both&amp;nbsp; interfaces Y and Z have same IP address.&lt;/P&gt;&lt;P&gt;So in order to&amp;nbsp; move packet from&amp;nbsp; interface Y to Z&amp;nbsp; transparent FW uses&amp;nbsp; arp table to get the mac of device connected to interface Z of transparent FW?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 16:53:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233369#M348505</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-06-07T16:53:20Z</dc:date>
    </item>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233370#M348506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the FW Y interface and Transparent Firewall is on the 172.x subnet ( the destination you are trying to go you are going to be fine),&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this the case?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 16:57:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233370#M348506</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-06-07T16:57:33Z</dc:date>
    </item>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233371#M348507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes Dest subnet and Y interface of Transparent FW&amp;nbsp; are on same subnet.&lt;/P&gt;&lt;P&gt;So FW just forward the packet to device by looking at mac address table right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mahesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 17:00:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233371#M348507</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2013-06-07T17:00:30Z</dc:date>
    </item>
    <item>
      <title>Traffic Flow between Transparent and Routed FW.</title>
      <link>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233372#M348508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exactly, the packet will be forward to the LAN, then the devices in between FW transparent and switches will send the traffic to the right ports,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 17:01:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/traffic-flow-between-transparent-and-routed-fw/m-p/2233372#M348508</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-06-07T17:01:36Z</dc:date>
    </item>
  </channel>
</rss>

