1. Lecture 9 Ethernet and other Link Layer protocols
Computer Networking: A Top Down Approach
From Kurose & Ross Book
slightly modified by
Romaric Duvignau
Bring the pen for the laser !
7th edition Jim Kurose, Keith Ross Pearson/Addison Wesley April 2016
Thanks and enjoy! JFK/KWR
All material copyright
J.F Kurose and K.W. Ross, All Rights Reserved
Network Layer: Control Plane

2. Link layer, LANs: outline
addressing, ARP
Ethernet
switches
VLANS
6.6 data center networking
6.7 a day in the life of a web request
Link Layer and LANs

3. MAC addresses and ARP 32-bit IP address:
network-layer address for interface
used for layer 3 (network layer) forwarding
MAC (or LAN or physical or Ethernet) address:
function: used ‘locally” to get frame from one interface to another physically-connected interface (same network, in IP-addressing sense)
48 bit MAC address (for most LANs) burned in NIC ROM, also sometimes software settable
e.g.: 1A-2F-BB AD
Q> What’s the point to have both IP and MAC addresses ? -> IP addresses can be grouped (easier to route), -> MAC might be needed for other protocol than IP (or even newer version). Theoretically nothing stop to use only IP.
hexadecimal (base 16) notation
(each “numeral” represents 4 bits)
Link Layer and LANs

4. LAN addresses and ARP each adapter on LAN has unique LAN address LAN
1A-2F-BB AD
LAN
(wired or
wireless)
adapter
71-65-F7-2B-08-53
58-23-D7-FA-20-B0
0C-C4-11-6F-E3-98
Link Layer and LANs

5. LAN addresses (more) MAC address allocation administered by IEEE
manufacturer buys portion of MAC address space (to assure uniqueness)
analogy:
MAC address: like Social Security Number
IP address: like postal address
MAC flat address ➜ portability
can move LAN card from one LAN to another
IP hierarchical address not portable
address depends on IP subnet to which node is attached
Good analogy! “Personnummer” and address
Link Layer and LANs

6. ARP: address resolution protocol
Question: how to determine
interface’s MAC address, knowing its IP address?
ARP table: each IP node (host, router) on LAN has table
IP/MAC address mappings for some LAN nodes:
< IP address; MAC address; TTL>
TTL (Time To Live): time after which address mapping will be forgotten (typically 20 min)
1A-2F-BB AD
LAN
71-65-F7-2B-08-53
58-23-D7-FA-20-B0
0C-C4-11-6F-E3-98
Link Layer and LANs

7. ARP protocol: same LAN A wants to send datagram to B
B’s MAC address not in A’s ARP table.
A broadcasts ARP query packet, containing B's IP address
destination MAC address = FF-FF-FF-FF-FF-FF
all nodes on LAN receive ARP query
B receives ARP packet, replies to A with its (B's) MAC address
frame sent to A’s MAC address (unicast)
A caches (saves) IP-to-MAC address pair in its ARP table until information becomes old (times out)
soft state: information that times out (goes away) unless refreshed
ARP is “plug-and-play”:
nodes create their ARP tables without intervention from net administrator
Let’s make an example!
Link Layer and LANs

8. Addressing: routing to another LAN
walkthrough: send datagram from A to B via R
focus on addressing – at IP (datagram) and MAC layer (frame)
assume A knows B’s IP address
assume A knows IP address of first hop router, R (how?)
assume A knows R’s MAC address (how?) R
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
C-E8-FF-55 A
49-BD-D2-C7-56-2A
88-B2-2F-54-1A-0F B
Link Layer and LANs

9. Addressing: routing to another LAN
A creates IP datagram with IP source A, destination B
A creates link-layer frame with R's MAC address as destination address, frame contains A-to-B IP datagram
MAC src: C-E8-FF-55
MAC dest: E6-E BB-4B IP
Eth
Phy
IP src:
IP dest: R
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
C-E8-FF-55 A
49-BD-D2-C7-56-2A
88-B2-2F-54-1A-0F B
Link Layer and LANs

10. Addressing: routing to another LAN
frame sent from A to R
frame received at R, datagram removed, passed up to IP
MAC src: C-E8-FF-55
MAC dest: E6-E BB-4B
IP src:
IP dest:
IP src:
IP dest: IP
Eth
Phy IP
Eth
Phy R
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
C-E8-FF-55 A
49-BD-D2-C7-56-2A
88-B2-2F-54-1A-0F B
Link Layer and LANs

11. Addressing: routing to another LAN
R forwards datagram with IP source A, destination B
R creates link-layer frame with B's MAC address as destination address, frame contains A-to-B IP datagram
MAC src: 1A-23-F9-CD-06-9B
MAC dest: 49-BD-D2-C7-56-2A IP
Eth
Phy
IP src:
IP dest: IP
Eth
Phy R
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
C-E8-FF-55 A
49-BD-D2-C7-56-2A
88-B2-2F-54-1A-0F B
Link Layer and LANs

12. Addressing: routing to another LAN
R forwards datagram with IP source A, destination B
R creates link-layer frame with B's MAC address as destination address, frame contains A-to-B IP datagram
IP src:
IP dest:
MAC src: 1A-23-F9-CD-06-9B
MAC dest: 49-BD-D2-C7-56-2A IP
Eth
Phy IP
Eth
Phy R
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
C-E8-FF-55 A
49-BD-D2-C7-56-2A
88-B2-2F-54-1A-0F B
Link Layer and LANs

13. Addressing: routing to another LAN
R forwards datagram with IP source A, destination B
R creates link-layer frame with B's MAC address as dest, frame contains A-to-B IP datagram
MAC src: 1A-23-F9-CD-06-9B
MAC dest: 49-BD-D2-C7-56-2A
IP src:
IP dest: IP
Eth
Phy B A R
49-BD-D2-C7-56-2A
C-E8-FF-55
1A-23-F9-CD-06-9B
E6-E BB-4B
CC-49-DE-D0-AB-7D
88-B2-2F-54-1A-0F
* Check out the online interactive exercises for more examples:
Link Layer and LANs

14. Link layer, LANs: outline
addressing, ARP
Ethernet
switches
VLANS
6.6 data center networking
6.7 a day in the life of a web request
Link Layer and LANs

15. Ethernet “dominant” wired LAN technology:
single chip, multiple speeds (e.g., Broadcom BCM5761)
first widely used LAN technology
simpler, cheap
kept up with speed race: 10 Mbps – 10 Gbps
Q>What’s the trick, I thought “Ethernet” was a Medium Access Protocol ? All in one! Plus, Cable, MAP, +Physical layer (). Named after Luminiferous aether
(medium for light)  disproven! Originally: shared-medium.
Metcalfe’s Ethernet sketch
Link Layer and LANs

16. Ethernet: physical topology
bus: popular through mid 90s
all nodes in same collision domain (can collide with each other)
star: prevails today
active switch in center
each “spoke” runs a (separate) Ethernet protocol (nodes do not collide with each other)
switch
star
bus: coaxial cable
Link Layer and LANs

17. Ethernet frame structure
sending adapter encapsulates IP datagram (or other network layer protocol packet) in Ethernet frame
preamble:
7 bytes with pattern followed by one byte with pattern
used to synchronize receiver, sender clock rates
dest.
address
source
data (payload)
CRC
preamble
type
Syncword. (+”special” end of frame symbol, physical layer). 73x23=1679 Arecibo (more elaborated
Link Layer and LANs

18. Ethernet frame structure (more)
addresses: 6 byte source, destination MAC addresses
if adapter receives frame with matching destination address, or with broadcast address (e.g. ARP packet), it passes data in frame to network layer protocol
otherwise, adapter discards frame
type: indicates higher layer protocol (mostly IP but others possible, e.g., Novell IPX, AppleTalk)
CRC: cyclic redundancy check at receiver
error detected: frame is dropped
Important because it’s the last thing that’s left of the original Ethernet (higher speed, etc)
Type: Similar to Protocol
dest.
address
source
data (payload)
CRC
preamble
type
Link Layer and LANs

19. Ethernet: unreliable, connectionless
connectionless: no handshaking between sending and receiving NICs
unreliable: receiving NIC doesn't send acks or nacks to sending NIC
data in dropped frames recovered only if initial sender uses higher layer rdt (e.g., TCP), otherwise dropped data lost
Ethernet’s MAC protocol: unslotted CSMA/CD with binary backoff
Unreliable like IP/UDP. Remember now it’s mostly collision-free (switch architecture).
Link Layer and LANs

20. Link layer, LANs: outline
addressing, ARP
Ethernet
switches
VLANS
6.6 data center networking
6.7 a day in the life of a web request
Link Layer and LANs

21. Ethernet switch link-layer device: takes an active role
store, forward Ethernet frames
examine incoming frame’s MAC address, selectively forward frame to one-or-more outgoing links when frame is to be forwarded on segment, uses CSMA/CD to access segment
transparent
hosts are unaware of presence of switches
plug-and-play, self-learning
switches do not need to be configured
Link Layer and LANs

22. Switch: multiple simultaneous transmissions
hosts have dedicated, direct connection to switch
switches buffer packets
Ethernet protocol used on each incoming link, but no collisions; full duplex
each link is its own collision domain
switching: A-to-A’ and B-to-B’ can transmit simultaneously, without collisions
switch with six interfaces
(1,2,3,4,5,6) A A’ B B’ C C’ 1 2 3 4 5 6
Q>Switch Table. Routing protocol you think ? And why not ?
Link Layer and LANs

23. Switch forwarding table
Q: how does switch know A’ reachable via interface 4, B’ reachable via interface 5?
switch with six interfaces
(1,2,3,4,5,6) A A’ B B’ C C’ 1 2 3 4 5 6
A: each switch has a switch table, each entry:
(MAC address of host, interface to reach host, time stamp)
looks like a routing table!
Q: how are entries created, maintained in switch table?
something like a routing protocol?
Link Layer and LANs

24. Switch: self-learning
Source: A
Dest: A’ A A’ B B’ C C’ 1 2 3 4 5 6
A A’
switch learns which hosts can be reached through which interfaces
when frame received, switch “learns” location of sender: incoming LAN segment
records sender/location pair in switch table
MAC addr interface TTL A 1 60
Switch table
(initially empty)
Link Layer and LANs

25. Switch: frame filtering/forwarding
when frame received at switch:
1. record incoming link, MAC address of sending host
2. index switch table using MAC destination address
3. if entry found for destination then {
if destination on segment from which frame arrived then drop frame
else forward frame on interface indicated by entry }
else flood /* forward on all interfaces except arriving
interface */
Link Layer and LANs

26. Self-learning, forwarding: example
Source: A
Dest: A’ A A’ B B’ C C’ 1 2 3 4 5 6
A A’
frame destination, A’, location unknown:
flood
destination A location known:
selectively send
on just one link
A A’
A A’
A A’
A A’
A A’
A’ A
MAC addr interface TTL A 1 60
switch table
(initially empty) A’ 4 60
Link Layer and LANs

27. Interconnecting switches
self-learning switches can be connected together: D E F S2 S4 S3 H I G A B S1 C
Q: sending from A to G - how does S1 know to forward frame destined to G via S4 and S3?
A: self learning! (works exactly the same as in single-switch case!)
Link Layer and LANs

28. Self-learning multi-switch example
Suppose C sends frame to I, I responds to C D E F S2 S4 S3 H I G A B S1 C
Q: show switch tables and packet forwarding in S1, S2, S3, S4
Link Layer and LANs

29. Institutional network
mail server
to external
network
web server
router
IP subnet
Link Layer and LANs

30. Switches vs. routers both are store-and-forward:
application
transport
network
link
physical
both are store-and-forward:
routers: network-layer devices (examine network-layer headers)
switches: link-layer devices (examine link-layer headers)
both have forwarding tables:
routers: compute tables using routing algorithms, IP addresses
switches: learn forwarding table using flooding, learning, MAC addresses
datagram
frame
link
physical
frame
switch
network
link
physical
datagram
frame
application
transport
network
link
physical
Link Layer and LANs

31. VLANs: motivation consider:
CS user moves office to EE, but wants connect to CS switch?
single broadcast domain:
all layer-2 broadcast traffic (ARP, DHCP, unknown location of destination MAC address) must cross entire LAN
security/privacy, efficiency issues
Computer
Science
Computer
Engineering
Electrical
Engineering
Main reason -> to isolate traffic!
Link Layer and LANs

32. VLANs
port-based VLAN: switch ports grouped (by switch management software) so that single physical switch ……
Virtual Local
Area Network 1 7 9 15 2 8 10 16
switch(es) supporting VLAN capabilities can be configured to define multiple virtual LANS over single physical LAN infrastructure. … …
Electrical Engineering
(VLAN ports 1-8)
Computer Science
(VLAN ports 9-15)
Electrical Engineering
(VLAN ports 1-8) … 1 8 2 7 9 16 10 15
Computer Science
(VLAN ports 9-16)
… operates as multiple virtual switches
Link Layer and LANs

33. Link layer, LANs: outline
addressing, ARP
Ethernet
switches
VLANS
6.6 data center networking
6.7 a day in the life of a web request
Link Layer and LANs

34. Data center networks
10’s to 100’s of thousands of hosts, often closely coupled, in close proximity:
e-business (e.g. Amazon)
content-servers (e.g., YouTube, Akamai, Apple, Microsoft)
search engines, data mining (e.g., Google)
challenges:
multiple applications, each serving massive numbers of clients
managing/balancing load, avoiding processing, networking, data bottlenecks
Inside a 40-ft Microsoft container,
Chicago data center
Link Layer and LANs

35. Data center networks load balancer: application-layer routing
receives external client requests
directs workload within data center
returns results to external client (hiding data center internals from client)
Internet
Border router
Load
balancer
Load
balancer
Access router
Tier-1 switches B A
Normal architecture -> problem to send from one host to another can easily saturate links ! C
Tier-2 switches
TOR switches
Server racks 1 2 3 4 5 6 7 8
Link Layer and LANs

36. Data center networks rich interconnection among switches, racks:
increased throughput between racks (multiple routing paths possible)
increased reliability via redundancy
Server racks
TOR switches
Tier-1 switches
Tier-2 switches 1 2 3 4 5 6 7 8
Link Layer and LANs

37. Link layer, LANs: outline
addressing, ARP
Ethernet
switches
VLANS
6.6 data center networking
6.7 a day in the life of a web request
Hopefully, DEMO! it’s more interactive ;)
Link Layer and LANs

38. Synthesis: a day in the life of a web request
journey down protocol stack complete!
application, transport, network, link
putting-it-all-together: synthesis!
goal: identify, review, understand protocols (at all layers) involved in seemingly simple scenario: requesting www page
scenario: student attaches laptop to campus network, requests/receives
Link Layer and LANs

39. A day in the life: scenario
browser
DNS server
Comcast network
/13
school network
/24
web page
web server
Google’s network
/19
Link Layer and LANs

40. A day in the life… connecting to the Internet
DHCP
UDP IP
Eth
Phy
DHCP
DHCP
connecting laptop needs to get its own IP address, addr of first-hop router, addr of DNS server: use DHCP
router
(runs DHCP)
DHCP
DHCP request encapsulated in UDP, encapsulated in IP, encapsulated in Ethernet
DHCP
DHCP
UDP IP
Eth
Phy
DHCP
Ethernet frame broadcast (dest: FFFFFFFFFFFF) on LAN, received at router running DHCP server
Ethernet demuxed to IP demuxed, UDP demuxed to DHCP
Link Layer and LANs

41. A day in the life… connecting to the Internet
DHCP
DHCP
UDP IP
Eth
Phy
DHCP server formulates DHCP ACK containing client’s IP address, IP address of first-hop router for client, name & IP address of DNS server
router
(runs DHCP)
encapsulation at DHCP server, frame forwarded (switch learning) through LAN, demultiplexing at client
DHCP
UDP IP
Eth
Phy
DHCP
DHCP
DHCP client receives DHCP ACK reply
DHCP
Client now has IP address, knows name & addr of DNS
server, IP address of its first-hop router
Link Layer and LANs

42. A day in the life… ARP (before DNS, before HTTP)
before sending HTTP request, need IP address of DNS
DNS
UDP IP
Eth
Phy
DNS
router
(runs DHCP)
ARP
ARP query
DNS query created, encapsulated in UDP, encapsulated in IP, encapsulated in Eth. To send frame to router, need MAC address of router interface: ARP
Eth
Phy
ARP
ARP reply
ARP query broadcast, received by router, which replies with ARP reply giving MAC address of router interface
client now knows MAC address of first hop router, so can now send frame containing DNS query
Link Layer and LANs

43. A day in the life… using DNS
UDP IP
Eth
Phy
DNS
DNS server
DNS
UDP IP
Eth
Phy
DNS
router
(runs DHCP)
DNS
DNS
DNS
DNS
Comcast network
/13
IP datagram forwarded from campus network into Comcast network, routed (tables created by RIP, OSPF, IS-IS and/or BGP routing protocols) to DNS server
IP datagram containing DNS query forwarded via LAN switch from client to 1st hop router
demuxed to DNS server
DNS server replies to client with IP address of
Link Layer and LANs

44. A day in the life…TCP connection carrying HTTPIP
Eth
Phy
router
(runs DHCP)
SYN
SYNACK
SYN
to send HTTP request, client first opens TCP socket to web server
TCP IP
Eth
Phy
TCP SYN segment (step 1 in 3-way handshake) inter-domain routed to web server
SYNACK
SYN
SYNACK
web server responds with TCP SYNACK (step 2 in 3-way handshake)
web server
TCP connection established!
Link Layer and LANs

45. A day in the life… HTTP request/reply
web page finally (!!!) displayed
HTTP
HTTP
HTTP
TCP IP
Eth
Phy
router
(runs DHCP)
HTTP
HTTP
HTTP request sent into TCP socket
IP datagram containing HTTP request routed to
HTTP
TCP IP
Eth
Phy
HTTP
HTTP
web server responds with HTTP reply (containing web page)
web server
IP datagram containing HTTP reply routed back to client
Link Layer and LANs

46. Chapter 6: Summary principles behind data link layer services:
error detection, correction
sharing a broadcast channel: multiple access
link layer addressing
instantiation and implementation of various link layer technologies
Ethernet
switched LANS, VLANs
virtualized networks as a link layer: MPLS
synthesis: a day in the life of a web request
Link Layer and LANs

47. Chapter 6: let’s take a breath
journey down protocol stack complete (except PHY)
solid understanding of networking principles, practice
….. could stop here …. but lots of interesting topics!
wireless
multimedia
security
Link Layer and LANs

48. Lecture 9: Review Questions
Why is it important to have both IP and MAC addresses ?
Can an Ethernet frame contain an undetected error, and is yes, when would it be detected ?
Can a fragment cycle through a switch network, why ?
Link Layer and LANs

49. Lecture 9: Extra Material
Ethernet standards
Some more about VLAN
Link virtualization: MPLS
Link Layer and LANs

50. 802.3 Ethernet standards: link & physical layers
many different Ethernet standards
common MAC protocol and frame format
different speeds: 2 Mbps, 10 Mbps, 100 Mbps, 1Gbps, 10 Gbps, 40 Gbps
different physical layer media: fiber, cable
MAC protocol
and frame format
application
transport
network
link
physical
copper (twister
pair) physical layer
100BASE-TX
fiber physical layer
100BASE-T2
100BASE-FX
100BASE-T4
100BASE-SX
100BASE-BX
Link Layer and LANs

51. Electrical Engineering
Port-based VLAN
router
traffic isolation: frames to/from ports 1-8 can only reach ports 1-8
can also define VLAN based on MAC addresses of endpoints, rather than switch port
forwarding between VLANS: done via routing (just as with separate switches)
in practice vendors sell combined switches plus routers 1 7 9 15 2 8 10 16
dynamic membership: ports can be dynamically assigned among VLANs … …
Electrical Engineering
(VLAN ports 1-8)
Computer Science
(VLAN ports 9-15)
Link Layer and LANs

52. VLANS spanning multiple switches1 7 9 16 1 15 3 5 7 2 8 10 2 4 6 8 … …
Electrical Engineering
(VLAN ports 1-8)
Computer Science
(VLAN ports 9-15)
Ports 2,3,5 belong to EE VLAN
Ports 4,6,7,8 belong to CS VLAN
trunk port: carries frames between VLANS defined over multiple physical switches
frames forwarded within VLAN between switches can’t be vanilla frames (must carry VLAN ID info)
802.1q protocol adds/removed additional header fields for frames forwarded between trunk ports
Link Layer and LANs

53. 802.1Q VLAN frame format 802.1 frame 802.1Q frame
type
dest.
address
source
address
preamble
data (payload)
CRC
802.1 frame
type
dest.
address
source
preamble
802.1Q frame
data (payload)
CRC
2-byte Tag Protocol Identifier
(value: 81-00)
Recomputed
CRC
Tag Control Information (12 bit VLAN ID field,
3 bit priority field like IP TOS)
Link Layer and LANs

54. Link layer, LANs: outline
6.1 introduction, services
6.2 error detection, correction
6.3 multiple access protocols
6.4 LANs
addressing, ARP
Ethernet
switches
VLANS
6.5 link virtualization: MPLS
6.6 data center networking
6.7 a day in the life of a web request
Link Layer and LANs

55. Multiprotocol label switching (MPLS)
initial goal: high-speed IP forwarding using fixed length label (instead of IP address)
fast lookup using fixed length identifier (rather than shortest prefix matching)
borrowing ideas from Virtual Circuit (VC) approach
but IP datagram still keeps IP address!
PPP or Ethernet
header
MPLS header
IP header
remainder of link-layer frame
label
Exp S
TTL 20 3 1 5
Link Layer and LANs

56. MPLS capable routers a.k.a. label-switched router
forward packets to outgoing interface based only on label value (don’t inspect IP address)
MPLS forwarding table distinct from IP forwarding tables
flexibility: MPLS forwarding decisions can differ from those of IP
use destination and source addresses to route flows to same destination differently (traffic engineering)
re-route flows quickly if link fails: pre-computed backup paths (useful for VoIP)
Link Layer and LANs

57. MPLS versus IP paths R6 D R4 R3 R5 A R2
IP routing: path to destination determined by destination address alone
IP router
Link Layer and LANs

58. MPLS versus IP paths
entry router (R4) can use different MPLS routes to A based, e.g., on source address R6 D R4 R3 R5 A R2
IP routing: path to destination determined by destination address alone
IP-only
router
MPLS routing: path to destination can be based on source and destination address
fast reroute: precompute backup routes in case of link failure
MPLS and
IP router
Link Layer and LANs

59. MPLS signaling
modify OSPF, IS-IS link-state flooding protocols to carry info used by MPLS routing,
e.g., link bandwidth, amount of “reserved” link bandwidth
entry MPLS router uses RSVP-TE signaling protocol to set up MPLS forwarding at downstream routers
RSVP-TE R6
modified
link state
flooding D R4 R5 A
Link Layer and LANs

60. MPLS forwarding tables
in out out
label label dest interface A
in out out
label label dest interface A D D A R6 D 1 1 R4 R3 R5 A R2
in out out
label label dest interface A R1
in out out
label label dest interface A
Link Layer and LANs