<?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 Firepower Threat Defense dropping relayed dhcp from adjacent switch in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-threat-defense-dropping-relayed-dhcp-from-adjacent/m-p/4019702#M937157</link>
    <description>&lt;P&gt;Hello&lt;BR /&gt;We just installed an ASA 5516-X to productions as an east/west routed firewall. It is Firepower Threat Defense 6.4.0.4-34 managed by onboard Firepower Defense Manager.&lt;BR /&gt;The DHCP server is 192.168.5.21&lt;BR /&gt;The inside of the ASA is 192.168.5.1&lt;BR /&gt;The outside of the ASA is 192.168.20.2&lt;BR /&gt;The nexthop switch from the ASA is 192.168.20.1&lt;BR /&gt;The switch has a l3 interface for VLAN 8 which is 192.168.16.1 and is configured with "ip helper-address 192.168.5.21"&lt;BR /&gt;It looks like DHCP requests from VLAN 8 are not making it through the ASA.&lt;BR /&gt;"packet-tracer input outside udp 192.168.16.1 4321 192.168.5.21 67" shows the traffic allowed.&lt;BR /&gt;"capture cap1 interface outside type raw-data match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows lot of packets.&lt;BR /&gt;"caputure cap2 interface outside type asp-drop all match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows 0 packets.&lt;BR /&gt;"caputure cap3 interface inside type raw-data match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows 0 packets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We rolled back the install and have a TAC case open.&amp;nbsp; We are waiting to schedule a maintenance windows when an engineer can help troubleshoot this, but I wanted to see if anyone else has run into this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also tried setting up a DHCP relay on the ASA using a FlexConfig template, and then point the helper on the switch to the ASA so it is a double relay.&amp;nbsp; We didn't get a chance to actually test if that was successful or not though, and its not ideal.&amp;nbsp; The unicast traffic should be able to pass the ASA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Leon&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 17:52:30 GMT</pubDate>
    <dc:creator>Leon Jaimes</dc:creator>
    <dc:date>2020-02-21T17:52:30Z</dc:date>
    <item>
      <title>Firepower Threat Defense dropping relayed dhcp from adjacent switch</title>
      <link>https://community.cisco.com/t5/network-security/firepower-threat-defense-dropping-relayed-dhcp-from-adjacent/m-p/4019702#M937157</link>
      <description>&lt;P&gt;Hello&lt;BR /&gt;We just installed an ASA 5516-X to productions as an east/west routed firewall. It is Firepower Threat Defense 6.4.0.4-34 managed by onboard Firepower Defense Manager.&lt;BR /&gt;The DHCP server is 192.168.5.21&lt;BR /&gt;The inside of the ASA is 192.168.5.1&lt;BR /&gt;The outside of the ASA is 192.168.20.2&lt;BR /&gt;The nexthop switch from the ASA is 192.168.20.1&lt;BR /&gt;The switch has a l3 interface for VLAN 8 which is 192.168.16.1 and is configured with "ip helper-address 192.168.5.21"&lt;BR /&gt;It looks like DHCP requests from VLAN 8 are not making it through the ASA.&lt;BR /&gt;"packet-tracer input outside udp 192.168.16.1 4321 192.168.5.21 67" shows the traffic allowed.&lt;BR /&gt;"capture cap1 interface outside type raw-data match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows lot of packets.&lt;BR /&gt;"caputure cap2 interface outside type asp-drop all match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows 0 packets.&lt;BR /&gt;"caputure cap3 interface inside type raw-data match udp host 192.168.16.1 host 192.168.5.21 eq 67" shows 0 packets.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We rolled back the install and have a TAC case open.&amp;nbsp; We are waiting to schedule a maintenance windows when an engineer can help troubleshoot this, but I wanted to see if anyone else has run into this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We also tried setting up a DHCP relay on the ASA using a FlexConfig template, and then point the helper on the switch to the ASA so it is a double relay.&amp;nbsp; We didn't get a chance to actually test if that was successful or not though, and its not ideal.&amp;nbsp; The unicast traffic should be able to pass the ASA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Leon&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:52:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-threat-defense-dropping-relayed-dhcp-from-adjacent/m-p/4019702#M937157</guid>
      <dc:creator>Leon Jaimes</dc:creator>
      <dc:date>2020-02-21T17:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Threat Defense dropping relayed dhcp from adjacent switch</title>
      <link>https://community.cisco.com/t5/network-security/firepower-threat-defense-dropping-relayed-dhcp-from-adjacent/m-p/4020013#M937159</link>
      <description>&lt;P&gt;There was a bug in 6.3.0.x that was fixed a while back and version 6.4.0.4 was a recent recommended (Gold Starred) release and I have not seen others having this issue. With that said, working with TAC is the best next steps for this issue. Please keep us posted on the progress/resolution.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2020 04:50:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-threat-defense-dropping-relayed-dhcp-from-adjacent/m-p/4020013#M937159</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2020-01-29T04:50:55Z</dc:date>
    </item>
  </channel>
</rss>

