<?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: FTD: Inline interface and routed interface in same VLAN? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5230869#M1117895</link>
    <description>&lt;P&gt;Version 7.7 introduces geolocation based RAVPN filtering.&lt;/P&gt;</description>
    <pubDate>Sat, 30 Nov 2024 20:18:01 GMT</pubDate>
    <dc:creator>Peter Koltl</dc:creator>
    <dc:date>2024-11-30T20:18:01Z</dc:date>
    <item>
      <title>FTD: Inline interface and routed interface in same VLAN?</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5230466#M1117872</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm thinking about follwing internet edge FTD setup for branch offices. Firewall pair FTD1a/b has two interfaces in public provider outside VLAN.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Interface "inline-outside" is an inline-set to threat protect access to AnyConnect VPN peer FTD2a/b because FTD still is lacking threat-protection for control-plane traffic. One would do IPS here and also block access via geolocation objects.&lt;/LI&gt;&lt;LI&gt;Interface "outside" is a routed interface for dynamic NAT and outbound internet access from internal network and office network.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The local AnyConnect VPN peer on FTD2a/b should be accessible from the local guest network, hence it can't be on the same firewall that provides outbound access (FTD1a/b). In the lab I did such a setup and am able to access from inside through FTD1a/b the outside IP of the device FTD2a/b behind the inline interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this a supported and common setup or am I walking here on uncharted territory full of boobie traps?&lt;/P&gt;&lt;P&gt;When looking on FMC connection events, I see that the unicast traffic that FTD1a/b receives from inside and should be sent to the router&amp;nbsp;also is sent to the inline interface. Is this normal? I would expect only to see broadcast traffic from the same VLAN to be seen on the inline interface. The FMC management guide [1] states: "&lt;SPAN&gt;Inline interfaces receive all traffic unconditionally, but all traffic received on these interfaces is retransmitted out of an inline set unless explicitly dropped.&lt;/SPAN&gt;" So inline interface behaves like a hub and not a switch?&lt;/P&gt;&lt;P&gt;An alternative would be a FTD pair in transparent mode to do threat-protection of AnyConnect VPN peer, but then this would require one additional firewall pair.&lt;/P&gt;&lt;P&gt;Thanks in advance for enlightenment.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bernd&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ftd-inline-interfaces.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/234803i05037678A0E64C26/image-size/large?v=v2&amp;amp;px=999" role="button" title="ftd-inline-interfaces.jpg" alt="ftd-inline-interfaces.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[1]&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/70/configuration/guide/fpmc-config-guide-v70/inline_sets_and_passive_interfaces_for_firepower_threat_defense.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/70/configuration/guide/fpmc-config-guide-v70/inline_sets_and_passive_interfaces_for_firepower_threat_defense.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2024 09:13:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5230466#M1117872</guid>
      <dc:creator>Network Diver</dc:creator>
      <dc:date>2024-11-29T09:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: FTD: Inline interface and routed interface in same VLAN?</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5230869#M1117895</link>
      <description>&lt;P&gt;Version 7.7 introduces geolocation based RAVPN filtering.&lt;/P&gt;</description>
      <pubDate>Sat, 30 Nov 2024 20:18:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5230869#M1117895</guid>
      <dc:creator>Peter Koltl</dc:creator>
      <dc:date>2024-11-30T20:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: FTD: Inline interface and routed interface in same VLAN?</title>
      <link>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5231865#M1117952</link>
      <description>&lt;P&gt;FTD 7.7 is a long way to go. Current suggested release is 7.4.2. Also original question was more about having inline interface and routed interface in same VLAN causing troubles as also unicast traffic that should go to default gateway is being seen on the inline interface.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 12:35:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-inline-interface-and-routed-interface-in-same-vlan/m-p/5231865#M1117952</guid>
      <dc:creator>Network Diver</dc:creator>
      <dc:date>2024-12-03T12:35:05Z</dc:date>
    </item>
  </channel>
</rss>

