<?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 dhcp proxy vs relay in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/m-p/1992636#M440765</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bro&lt;/P&gt;&lt;P&gt;DHCP relay listens to local broadcast messages from PC, and forwards these messages on another network towards the DHCP server. The DHCP server responds, and the replies is then forwarded back to the PC.&lt;BR /&gt; &lt;BR /&gt;DHCP proxy is a fully-functional DHCP server and client built inside. The PC establishes IP leases from the DHCP server on one interface, and then keeps these addresses in a pool. On another interface, the server side of the implementation provides leases to other machines using that pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX/ASA Firewalls supports both method. In many of my previous implementations, the FW interface on which it behaves as a DHCP server has a dedicated, manually-configured address pool, and the only thing the proxy feature does is get configuration parameters from another upstream server e.g. equipment configuration, as shown below;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Router(config)#boot ?&lt;BR /&gt;&amp;nbsp; bootstrap&amp;nbsp; Bootstrap image file&lt;BR /&gt;&amp;nbsp; config&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Configuration file&lt;BR /&gt;&amp;nbsp; host&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Router-specific config file&lt;BR /&gt;&amp;nbsp; network&amp;nbsp;&amp;nbsp;&amp;nbsp; Network-wide config file&lt;BR /&gt;&amp;nbsp; system&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; System image file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;P/S: If you think this comment was helpful, please do rate it nicely &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jul 2012 10:19:42 GMT</pubDate>
    <dc:creator>Ramraj Sivagnanam Sivajanam</dc:creator>
    <dc:date>2012-07-16T10:19:42Z</dc:date>
    <item>
      <title>dhcp proxy vs relay</title>
      <link>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/m-p/1992635#M440764</link>
      <description>&lt;P&gt;What is the difference between dhcp relay and dhcp proxy with respect to ASAs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kashish&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:20:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/m-p/1992635#M440764</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2019-03-11T23:20:17Z</dc:date>
    </item>
    <item>
      <title>dhcp proxy vs relay</title>
      <link>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/m-p/1992636#M440765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bro&lt;/P&gt;&lt;P&gt;DHCP relay listens to local broadcast messages from PC, and forwards these messages on another network towards the DHCP server. The DHCP server responds, and the replies is then forwarded back to the PC.&lt;BR /&gt; &lt;BR /&gt;DHCP proxy is a fully-functional DHCP server and client built inside. The PC establishes IP leases from the DHCP server on one interface, and then keeps these addresses in a pool. On another interface, the server side of the implementation provides leases to other machines using that pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco PIX/ASA Firewalls supports both method. In many of my previous implementations, the FW interface on which it behaves as a DHCP server has a dedicated, manually-configured address pool, and the only thing the proxy feature does is get configuration parameters from another upstream server e.g. equipment configuration, as shown below;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Router(config)#boot ?&lt;BR /&gt;&amp;nbsp; bootstrap&amp;nbsp; Bootstrap image file&lt;BR /&gt;&amp;nbsp; config&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Configuration file&lt;BR /&gt;&amp;nbsp; host&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Router-specific config file&lt;BR /&gt;&amp;nbsp; network&amp;nbsp;&amp;nbsp;&amp;nbsp; Network-wide config file&lt;BR /&gt;&amp;nbsp; system&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; System image file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;P/S: If you think this comment was helpful, please do rate it nicely &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 10:19:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/m-p/1992636#M440765</guid>
      <dc:creator>Ramraj Sivagnanam Sivajanam</dc:creator>
      <dc:date>2012-07-16T10:19:42Z</dc:date>
    </item>
  </channel>
</rss>

