Scribd
Upload
42 views17 pages

Address Mapping

This document discusses address mapping between logical and physical addresses. It covers topics like ARP, RARP, BOOTP, DHCP and how they allow mapping between the two address types. Specific examples are provided, like an ARP request and reply encapsulated in Ethernet frames between two hosts on the same network.

Uploaded by

NIDHI SHARMA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
42 views17 pages

Address Mapping

This document discusses address mapping between logical and physical addresses. It covers topics like ARP, RARP, BOOTP, DHCP and how they allow mapping between the two address types. Specific examples are provided, like an ARP request and reply encapsulated in Ethernet frames between two hosts on the same network.

Uploaded by

NIDHI SHARMA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

21-1 ADDRESS MAPPING

The delivery of a packet to a host or a router requires


two levels of addressing: logical and physical. We need
to be able to map a logical address to its corresponding
physical address and vice versa. This can be done by
using either static or dynamic mapping.

Topics discussed in this section:


Mapping Logical to Physical Address
Mapping Physical to Logical Address

21.1
Figure 21.1 Mapping Logical to Physical Address
ARP (address resolution protocol)

21.2
Note

ARP can be useful if the ARP reply is


cached (kept in cache memory for a
while).

21.3
Figure 21.2 ARP packet

21.4
Figure 21.3 Encapsulation of ARP packet

21.5
Figure 21.4 Four cases using ARP

21.6
Note

An ARP request is broadcast;


an ARP reply is unicast.

21.7
Example 21.1

A host with IP address 130.23.43.20 and physical address


B2:34:55:10:22:10 has a packet to send to another host
with IP address 130.23.43.25 and physical address
A4:6E:F4:59:83:AB. The two hosts are on the same
Ethernet network. Show the ARP request and reply
packets encapsulated in Ethernet frames.

Solution
Figure 21.5 shows the ARP request and reply packets.
Note that the ARP data field in this case is 28 bytes, and
that the individual addresses do not fit in the 4-byte
boundary. That is why we do not show the regular 4-byte
boundaries for these addresses.
21.8
Figure 21.5 Example 21.1, an ARP request and reply

21.9
Figure 21.6 Proxy ARP

21.10
Mapping Phy to Logical Address:
RARP, BOOTP, and DHCP
◼ A diskless station just booted.
◼ An organization does not have enough IP
addresses to assign to each station.

21.11
Reverse Address Resolution
Protocol (ARP)
◼ A machine can use the phy address to get the
logical address using RARP.
◼ A RARP messages is created and brodcast on
the local network.
◼ The machine on the local network that knows
the logical address will respond with a RARP
reply.
◼ Broadcasting is done at data link layer.
◼ Broadcast requests does not pass the
boundaries of a network.

21.12
Figure 21.7 BOOTP client and server on the same and different networks

21.13
Note

DHCP provides static and dynamic


address allocation that can be
manual or automatic.

21.14
DHCP: Dynamic Host Configuration Protocol
Goal: allow host to dynamically obtain its IP address from
network server when it joins network
Can renew its lease on address in use
Allows reuse of addresses (only hold address while connected an
“on”
Support for mobile users who want to join network (more
shortly)
DHCP overview:
◼ host broadcasts “DHCP discover” msg
◼ DHCP server responds with “DHCP offer” msg
◼ host requests IP address: “DHCP request” msg
◼ DHCP server sends address: “DHCP ack” msg
DHCP client-server scenario

A DHCP 223.1.2.1
223.1.1.1
server
223.1.1.2
223.1.1.4 223.1.2.9
B
223.1.2.2 arriving DHCP
223.1.1.3 223.1.3.27 E
client needs
223.1.3.1 223.1.3.2
address in this
network
DHCP client-server scenario
DHCP server: 223.1.2.5 arriving
DHCP discover
client
src : 0.0.0.0, 68
dest.: 255.255.255.255,67
yiaddr: 0.0.0.0
transaction ID: 654

DHCP offer
src: 223.1.2.5, 67
dest: 255.255.255.255, 68
yiaddrr: 223.1.2.4
transaction ID: 654
Lifetime: 3600 secs
DHCP request
src: 0.0.0.0, 68
dest:: 255.255.255.255, 67
yiaddrr: 223.1.2.4
transaction ID: 655
time Lifetime: 3600 secs

DHCP ACK
src: 223.1.2.5, 67
dest: 255.255.255.255, 68
yiaddrr: 223.1.2.4
transaction ID: 655
Lifetime: 3600 secs

You might also like