DHCP: Difference between revisions
(Created page with "A DHCP server allows the client to get an IP address automatically without having to manually configure a static IP. <nowiki>Category: Terminology</nowiki>") |
No edit summary |
||
| Line 1: | Line 1: | ||
A DHCP server allows the client to get an IP address automatically without having to manually configure a static IP. | A DHCP server allows the client to get an IP address automatically without having to manually configure a static IP. | ||
== DHCP relay == | |||
DHCP relay listens to local broadcast messages from client and forwards these messages on another network towards the DHCP server. The DHCP server responds and the replies is then forwarded back to the client. | |||
== DHCP proxy == | |||
DHCP proxy is a fully-functional DHCP server and client built inside. The client 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. | |||
== Example == | |||
Cisco PIX/ASA Firewalls supports both method. Generally, 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.<ref>https://community.cisco.com/t5/network-security/dhcp-proxy-vs-relay/td-p/1992635</ref> | |||
== Reference == | |||
<references /> | |||
<nowiki>[[Category: Terminology]]</nowiki> | <nowiki>[[Category: Terminology]]</nowiki> | ||
Revision as of 09:46, 17 April 2023
A DHCP server allows the client to get an IP address automatically without having to manually configure a static IP.
DHCP relay
DHCP relay listens to local broadcast messages from client and forwards these messages on another network towards the DHCP server. The DHCP server responds and the replies is then forwarded back to the client.
DHCP proxy
DHCP proxy is a fully-functional DHCP server and client built inside. The client 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.
Example
Cisco PIX/ASA Firewalls supports both method. Generally, 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.[1]
Reference
[[Category: Terminology]]