Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | Korea Communication Market Data | List of Contributors | Become a Contributor |    
 
 
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
 
Real World Private 5G Cases   4 Deployment Models On-Premise Cases 5G Core Control Plane Sharing Cases

5G Core Sharing Cases

   
 
Private 5G Deployment   • Private 5G Frequency Allocation Status in Korea  South Korean government's regulations on private 5G and KT's strategy for entering the market
Cases in Korea   Private 5G Operators |   SK Networks Service (SI) Sejong Telecom (Wire-line Carrier) KT MOS (Affiliate of KT) • Newgens (SI) • NAVER Cloud more >>  
    Enterprise DIY |   Korea Hydro & Nuclear Power (Power Plant) Korea Electric Power Corporation (Energy) • Republic of Korea Navy more >>
 
CHANNELS     HFR Private 5G Solution (my5G)       my5G Solution Components       my5G Key Features        my5G Resources        my5G News          
 
banner
banner
What is a DHCP Relay Agent?
August 01, 2013 | By Chris Yoo (tech@netmanias.com)
Online viewer:
Comments (1)
8

We talked about the basic operations of DHCP in our previous blog post, "What is DHCP?”. Today, we will find out what kind of agent a DHCP relay agent is.

 

 

Generally, DHCP messages are broadcasted. So, in order for the messages to be exchanged between a DHCP client (PC) and DHCP server, both the client and server have to reside on the same subnet. That is because routers do not forward any broadcast IP packet (i.e. one with a destination MAC address of FF:FF:FF:FF:FF:FF and a destination IP address of 255.255.255.255) to other interfaces. Thus, a broadcast DHCP packet sent by a DHCP client cannot be delivered to DHCP server(s) on different subnet(s) through a router (shown in Figure (a)). This restriction requires all individual subnets have its own DHCP server for DHCP operations, which is practically not feasible in network operators' networks or corporate networks (Too many DHCP servers are required in the network!).

 

To address this problem, the concept of a DHCP relay agent has long been adopted. As shown in Figure 1 (b), enabling the DHCP relay agent function in the router allows DHCP messages to be exchanged between DHCP clients and DHCP servers residing on different subnets. The core function of this DHCP relay agent is to convert broadcast DHCP packets into unicast messages and then forward them to DHCP servers.

DHCP message flows in a network with a DHCP relay agent are as follows: 
 

1. [DHCP client (PC) -> DHCP server] DHCP Discover Message

When a client PC broadcasts a DHCP Discover message, a DHCP relay agent receives and converts the message (SIP=DHCP Relay Agent, DIP=DHCP Server), and forwards it to the DHCP server (here, SIP=Source IP address, DIP=Destination IP address in IP header).

 

2. [DHCP client (PC) <- DHCP server] DHCP Offer Message

When the DHCP server unicasts a DHCP Offer message to the DHCP relay agent (SIP=DHCP Server, DIP=DHCP Relay Agent), the DHCP relay agent converts the received message and broadcasts it to the client PC (Note: messages are not broadcasted in all cases. Please click the link below and refer to our technical document “Understanding the Detailed Operations of DHCP”).

 

3. [DHCP client (PC) -> DHCP server] DHCP Request Message

When the client PC broadcasts a DHCP Request message, the DHCP relay agent converts the received message (SIP=DHCP Relay Agent, DIP=DHCP Server), and forwards it to the DHCP server.

4. [DHCP client (PC) <- DHCP server] DHCP Ack Message

When the DHCP server unicasts a DHCP Ack message to the DHCP relay agent (SIP=DHCP server, DIP=DHCP Relay Agent), the DHCP relay agent converts and broadcasts the message to the client PC (Note: Messages are not broadcasted in all cases. Please click the link below and refer to our technical document “Understanding the Detailed Operations of DHCP”).

 

 

thx 2021-02-24 04:15:35

Thx

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
 
 
 
 

[HFR Private 5G: my5G]

 

Details >>

 

 

 

     
         
     

 

     
     

Subscribe FREE >>

Currently, 55,000+ subscribed to Netmanias.

  • You can get Netmanias Newsletter

  • You can view all netmanias' contents

  • You can download all netmanias'

    contents in pdf file

     
     

 

     
         
     

 

 

 

View All (854)
4.5G (1) 5G (101) AI (7) AR (1) ARP (3) AT&T (1) Akamai (1) Authentication (5) BSS (1) Big Data (2) Billing (1) Blockchain (3) C-RAN/Fronthaul (18) CDN (4) CPRI (4) Carrier Ethernet (3) Charging (1) China (1) China Mobile (2) Cisco (1) Cloud (5) CoMP (6) Connected Car (4) DHCP (5) EDGE (1) Edge Computing (1) Ericsson (2) FTTH (6) GSLB (1) GiGAtopia (2) Gigabit Internet (19) Google (7) Google Global Cache (3) HLS (5) HSDPA (2) HTTP Adaptive Streaming (5) Handover (1) Huawei (1) IEEE 802.1 (1) IP Routing (7) IPTV (21) IoST (3) IoT (56) KT (43) Korea (20) Korea ICT Market (1) Korea ICT Service (13) Korea ICT Vendor (1) LG U+ (18) LSC (1) LTE (78) LTE-A (16) LTE-B (1) LTE-H (2) LTE-M (3) LTE-U (4) LoRa (7) MEC (4) MPLS (2) MPTCP (3) MWC 2015 (8) NB-IoT (6) Netflix (2) Network Protocol (21) Network Slice (1) Network Slicing (4) New Radio (9) Nokia (1) OSPF (2) OTT (3) PCRF (1) Platform (2) Private 5G (10) QoS (3) RCS (4) Roaming (1) SD-WAN (17) SDN/NFV (71) SIM (1) SK Broadband (2) SK Telecom (35) Samsung (5) Security (16) Self-Driving (1) Small Cell (2) Spectrum Sharing (2) Switching (6) TAU (2) UHD (5) VR (2) Video Streaming (12) VoLTE (8) VoWiFi (2) Wi-Fi (31) YouTube (6) blockchain (1) eICIC (1) eMBMS (1) iBeacon (1) security (1) telecoin (1) uCPE (2)
Password confirmation
Please enter your registered comment password.
Password