<?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 Intercept and redirect traffic in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/intercept-and-redirect-traffic/m-p/3945206#M936197</link>
    <description>&lt;P&gt;On a FMC/FTD environment, any ideas how to intercept and redirect NTP and/or DNS traffic from specific clients? There are a few appliances with hardcoded NTP/DNS entries, which I would totally prefer to use my internal systems to provide them access to these resources, instead of blocking them, or letting them go thru on their own. The catch is, I don't always know the destination IP address - particularly true for the pool of NTP servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know I can do a static NAT when I do know the destination address(es): have this working on a similar scenario, but with the randomness of the NTP pool of servers, this is pretty tricky...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Edit] Well, never mind: it seems I can add my very own "IPv4-Any" object instead of trying to use the system provided "any-ipv4", and that does the trick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:36:59 GMT</pubDate>
    <dc:creator>HQuest</dc:creator>
    <dc:date>2020-02-21T17:36:59Z</dc:date>
    <item>
      <title>Intercept and redirect traffic</title>
      <link>https://community.cisco.com/t5/network-security/intercept-and-redirect-traffic/m-p/3945206#M936197</link>
      <description>&lt;P&gt;On a FMC/FTD environment, any ideas how to intercept and redirect NTP and/or DNS traffic from specific clients? There are a few appliances with hardcoded NTP/DNS entries, which I would totally prefer to use my internal systems to provide them access to these resources, instead of blocking them, or letting them go thru on their own. The catch is, I don't always know the destination IP address - particularly true for the pool of NTP servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know I can do a static NAT when I do know the destination address(es): have this working on a similar scenario, but with the randomness of the NTP pool of servers, this is pretty tricky...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[Edit] Well, never mind: it seems I can add my very own "IPv4-Any" object instead of trying to use the system provided "any-ipv4", and that does the trick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:36:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intercept-and-redirect-traffic/m-p/3945206#M936197</guid>
      <dc:creator>HQuest</dc:creator>
      <dc:date>2020-02-21T17:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: Intercept and redirect traffic</title>
      <link>https://community.cisco.com/t5/network-security/intercept-and-redirect-traffic/m-p/4860621#M1101884</link>
      <description>&lt;P&gt;I know this thread is rather old, but I'm looking for a solution to external hardcoded ntp or dns on certain devices and would like to use the firewall to intercept these requests from certain vrf's and redirect to internal ntp servers.&amp;nbsp; It appears that you determined a solution, but didn't post the details.&amp;nbsp; Can you elaborate?&amp;nbsp; Many Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jun 2023 12:23:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intercept-and-redirect-traffic/m-p/4860621#M1101884</guid>
      <dc:creator>wherewolf</dc:creator>
      <dc:date>2023-06-22T12:23:32Z</dc:date>
    </item>
  </channel>
</rss>

