<?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: VRF Question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370292#M1124469</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1726559"&gt;@N3om&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;This is a trick question.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Does it means that the ingress traffic via global routing table and egress traffic via vrf is working currently?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Why the return traffic is not using the same interface as ingress traffic?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you say "egresses via an interface in a user deifned vrf", then you might already have a routing send egress traffic to interface with&amp;nbsp;vrf.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wondering if this is not cause assymetric routing.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 16 Feb 2026 12:07:09 GMT</pubDate>
    <dc:creator>Flavio Miranda</dc:creator>
    <dc:date>2026-02-16T12:07:09Z</dc:date>
    <item>
      <title>VRF Question</title>
      <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370280#M1124467</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;We ahve an FTD and subnet 172.16.251.0/24 ingresses via a sub-interface in global routing then egresses via an interface in a user deifned vrf, my question is how do I route the return traffic to 172.16.251.0/24&lt;/P&gt;&lt;P&gt;1. Do I add a static route in the vrf pointing to the global interface for 172.16.251.0/24&lt;/P&gt;&lt;P&gt;2. Do I just add a static route in global pointing to the 172.16.251.0/24 network via the global interface&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 11:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370280#M1124467</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2026-02-16T11:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: VRF Question</title>
      <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370288#M1124468</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1726559"&gt;@N3om&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need route leaking ...&lt;/P&gt;
&lt;P&gt;Explore this documentation please:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/660/fdm/fptd-fdm-config-guide-660/fptd-fdm-virtual-routers.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/660/fdm/fptd-fdm-config-guide-660/fptd-fdm-virtual-routers.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 11:57:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370288#M1124468</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2026-02-16T11:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: VRF Question</title>
      <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370292#M1124469</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1726559"&gt;@N3om&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;This is a trick question.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Does it means that the ingress traffic via global routing table and egress traffic via vrf is working currently?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Why the return traffic is not using the same interface as ingress traffic?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you say "egresses via an interface in a user deifned vrf", then you might already have a routing send egress traffic to interface with&amp;nbsp;vrf.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wondering if this is not cause assymetric routing.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 12:07:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370292#M1124469</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2026-02-16T12:07:09Z</dc:date>
    </item>
    <item>
      <title>Re: VRF Question</title>
      <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370296#M1124470</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/178747"&gt;@Flavio Miranda&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Does it means that the ingress traffic via global routing table and egress traffic via vrf is working currently?&amp;nbsp; &lt;STRONG&gt;YES&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Why the return traffic is not using the same interface as ingress traffic?&amp;nbsp; &lt;STRONG&gt;Thats the question we dont have a route to the subnet yet&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 12:30:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370296#M1124470</guid>
      <dc:creator>N3om</dc:creator>
      <dc:date>2026-02-16T12:30:22Z</dc:date>
    </item>
    <item>
      <title>Re: VRF Question</title>
      <link>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370300#M1124471</link>
      <description>&lt;P&gt;considering the ingress interface is on global routing table, and if you intend to send traffic back, it should be necessary one static route return the traffic on that interface.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 12:54:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vrf-question/m-p/5370300#M1124471</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2026-02-16T12:54:53Z</dc:date>
    </item>
  </channel>
</rss>

