Transcript DNS and ARP

Communication Networks
Recitation 3
Netcomm 2005
1
DNS & ARP
Netcomm 2005
2
Addressing Schemes
• host names: convenient app-to-app communication
medellin.cs.columbia.edu
• IP: efficient large-scale network communication
• MAC: quick-n-easy LAN forwarding
128.119.40.7
E6-E9-00-17-BB-4B
Netcomm 2005
3
Routing Example
Starting at A, given IP datagram
addressed to B:
• look up network address of B,
find B on same network as A
• link layer sends datagram to B
inside link-layer frame
frame source,
dest. address
B’s MAC A’s MAC
addr
addr
A
223.1.1.1
223.1.2.1
223.1.1.2
223.1.1.4 223.1.2.9
B
223.1.1.3
datagram source,
dest. address
A’s IP
addr
B’s IP
addr
223.1.3.27
223.1.3.1
223.1.2.2
E
223.1.3.2
IP payload
datagram
frame
Netcomm 2005
4
Translating between addresses
Hostname (medellin.cs.columbia.edu)
DNS
IP address (128.119.40.7)
ARP
MAC address (E6-E9-00-17-BB-4B)
Netcomm 2005
5
DNS Servers
• Contacted by local
name server when can
not resolve name
• Root name server:
– contacts
authoritative name
server if name
mapping not known
– gets mapping
– returns mapping to
local name server
Netcomm 2005
6
DNS Hierarchy
edu
com
org
jp
rpi albany
DNS Distributed Database
rpi.edu
DNS rpi.edu
DB rpi.edu
DNS DNS
DB DB
Netcomm 2005
7
Simple DNS example
root name server
host surf.eurecom.fr
wants IP address of
gaia.cs.umass.edu
2
4
5
1. Contacts its local DNS
server, dns.eurecom.fr
2. dns.eurecom.fr contacts
local name server
root name server, if
dns.eurecom.fr
necessary
1
6
3. root name server contacts
authoritative name server,
dns.umass.edu, if
requesting host
necessary
surf.eurecom.fr
Netcomm 2005
3
authorititive name server
dns.umass.edu
gaia.cs.umass.edu
8
DNS example
root name server
Root name server:
• may not know
authoritative name
server
• may know
intermediate name
server: who to
contact to find
authoritative name
server
6
2
7
local name server
dns.eurecom.fr
1
8
requesting host
3
intermediate name server
dns.umass.edu
4
5
authoritative name server
dns.cs.umass.edu
surf.eurecom.fr
gaia.cs.umass.edu
Netcomm 2005
9
DNS: iterated queries
root name server
recursive query:
• puts burden of
name resolution on
contacted name
server
• heavy load
iterated query:
• contacted server
replies with name
of server to contact
• “I don’t know this
name, but ask this
server”
iterated query
2
3
4
7
local name server
dns.eurecom.fr
1
8
requesting host
intermediate name server
dns.umass.edu
5
6
authoritative name server
dns.cs.umass.edu
surf.eurecom.fr
gaia.cs.umass.edu
Netcomm 2005
10
DNS library functions
struct hostent *gethostbyname(
const char *hostname);
struct hostent *gethostbyaddr(
const char *addr
size_t len,
int family);
Netcomm 2005
11
LAN Addresses and ARP
32-bit IP address:
• network-layer address
• used to get datagram to destination network
LAN (or MAC or physical) address:
• used to get datagram from one interface to
another physically-connected interface (same
network)
• 48 bit MAC address (for most LANs)
burned into the adapter’s ROM
Netcomm 2005
12
LAN Addresses and ARP
Each adapter on the LAN has a unique LAN address
Netcomm 2005
13
ARP: Address Resolution Protocol
Question: how to determine
MAC address of B
given B’s IP address?
• Each IP node (Host, Router)
on LAN has ARP module and
table
• ARP Table: IP/MAC address
mappings for some LAN
nodes
< IP address; MAC address;
TTL>
<
…………………………..
>
– TTL (Time To Live): time of
day after which address
mapping will be forgotten
(typically 20 minutes)
Netcomm 2005
14
ARP protocol
Arp Arp!
• A knows B's IP address, wants to learn
physical address of B
• A broadcasts ARP query packet, containing
B's IP address
– all machines on LAN receive ARP query
• B receives ARP packet, replies to A with its
(B's) physical layer address
• A caches (saves) IP-to-physical address pairs
until information becomes old (times out)
– soft state: information that times out (goes
away) unless refreshed
Netcomm 2005
15
ARP Conversation
HEY - Everyone please listen!
Will 128.213.1.5 please send me
her Ethernet address?
not me
Hi Green! I’m 128.213.1.5, and
my Ethernet address is
87:A2:15:35:02:C3
Netcomm 2005
16
Problem 1
1. Calculate the completion time of
transferring a file of size 1KB over a link
with speed 10Mb/s and length 3000km.
Propagation speed is 200,000Km/s
Netcomm 2005
17
Solution 1
The completion time is calculated as follows:
T = Prop. Delay + Trans. Time
We obtain that:
• Prop. Delay = 3000 km /(0.2 km/usec) = 15ms
• Trans. Time = 1KB/1.25MB/s = 8.2 ms
T = 15ms + 8.2 ms = 23.2 ms
Netcomm 2005
18
Problem 2: CRC bits
• Bits represent a polynomial over GF(2)
• Example: 100101 = x5+x2+1
• Addition and subtraction are actually
XORs
• Example: 1101 + 111 = 1010
Netcomm 2005
19
Calculating CRC
• For data D and Generator G find bits R
such that DR = n*G (over GF(2)).
• Same as D00…0 = n*G + R (over
GF(2))
• R will always be 1 bit shorter than G
• Use long Division with XOR
Netcomm 2005
20
Solution 2
• D = 01011000, G=1101, R=???
• 01011000000 | 1101
R=011
1101
n=1100111
1100
1101
DR=01011000011
1000
1101
1010
1101
1110
1101
Netcomm 2005
11
21
Solution 2 – In reverse
• DR = 01011000011, G=1101
• 01011000011 | 1101
1101
1100
1101
1000
1101
1011
1101
1101
1101
Netcomm 2005
0
22
CRC – Concluding Remarks
• If R has r bits, there are 2r different CRCs
• A random string will not be detected as
an error in probability 2-r.
• Robustness for common errors depends
on G.
• Some standards try to avoid trailing 0’s.
Netcomm 2005
23
Problem 3
2. In CSMA/CD network there are two computers A
and B which collide in round 1. Give the table of
possible outcomes of the second round and their
probabilities. Assume that the initial delay period
after the collision is D=1 (the hosts pick a
random number between 0 and D before trying
to re-transmit).
Netcomm 2005
24
Solution 3
Case A
B
Probability Comment
--------------------------------------------------------------a
0
0
0.25
Collide in round 2
b
0
1
0.25
A successful in round 2
B successful in round 3
c
1
0
0.25
B successful in round 2
A successful in round 3
d
1
1
0.25
Collide in round 3
Netcomm 2005
25