Scribd Logo
Upload

Welcome to Scribd!

  • 19 views

    Week14 - Lec1-DLL Wrap Up

    Uploaded by

    Krish Vaghela
    This document summarizes the steps involved when a student requests a web page from their laptop connected to a campus network: 1. The laptop uses DHCP to obtain an IP address and network configuration from the campus router. 2. ARP is used to discover the MAC address of the router in order to send a DNS query for the IP address of the requested website. 3. DNS and TCP are used to look up and establish a connection to the website's IP address. 4. HTTP is used to send the request and receive the response over the TCP connection, completing the retrieval of the requested web page.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Week14 - Lec1-DLL Wrap Up

    Uploaded by

    Krish Vaghela
    19 views9 pages
    This document summarizes the steps involved when a student requests a web page from their laptop connected to a campus network: 1. The laptop uses DHCP to obtain an IP address and network configuration from the campus router. 2. ARP is used to discover the MAC address of the router in order to send a DNS query for the IP address of the requested website. 3. DNS and TCP are used to look up and establish a connection to the website's IP address. 4. HTTP is used to send the request and receive the response over the TCP connection, completing the retrieval of the requested web page.

    Original Title

    Week14_Lec1-DLL Wrap Up (2)

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document summarizes the steps involved when a student requests a web page from their laptop connected to a campus network: 1. The laptop uses DHCP to obtain an IP address and network configuration from the campus router. 2. ARP is used to discover the MAC address of the router in order to send a DNS query for the IP address of the requested website. 3. DNS and TCP are used to look up and establish a connection to the website's IP address. 4. HTTP is used to send the request and receive the response over the TCP connection, completing the retrieval of the requested web page.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    19 views9 pages

    Week14 - Lec1-DLL Wrap Up

    Uploaded by

    Krish Vaghela
    This document summarizes the steps involved when a student requests a web page from their laptop connected to a campus network: 1. The laptop uses DHCP to obtain an IP address and network configuration from the campus router. 2. ARP is used to discover the MAC address of the router in order to send a DNS query for the IP address of the requested website. 3. DNS and TCP are used to look up and establish a connection to the website's IP address. 4. HTTP is used to send the request and receive the response over the TCP connection, completing the retrieval of the requested web page.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 9

    Week 14-Lec1

    DLL Wrap Up
    Synthesis: a day in the life of a web request
     our journey down the protocol stack is now 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
    www.google.com

    Link Layer: 6-2


    A day in the life: scenario
    scenario:
    browser DNS server  arriving mobile
    Airtel network client attaches
    68.80.0.0/13 to network …
     requests web
    school network page:
    68.80.2.0/24
    www.google.com
    web page

    Sounds
    web server Google’s network
    simple!
    64.233.169.105 64.233.160.0/19

    Link Layer: 6-3


    A day in the life: connecting to the Internet
    DHCP
    DHCP
    DHCP
    UDP
     connecting laptop needs to get its own IP
    DHCP IP address, addr of first-hop router, addr of
    arriving mobile:
    DHCP Eth
    Phy DHCP client DNS server: use DHCP
    DHCP

     DHCP request encapsulated in UDP,


    DHCP DHCP encapsulated in IP, encapsulated in 802.3
    DHCP
    DHCP
    UDP
    IP
    Ethernet
    DHCP Eth
    Phy
    router has
     Ethernet frame broadcast (dest:
    DHCP server FFFFFFFFFFFF) on LAN, received at router
    running DHCP server
     Ethernet de-muxed to IP de-muxed, UDP
    de-muxed to DHCP
    Link Layer: 6-4
    A day in the life: connecting to the Internet
    DHCP
    DHCP UDP  DHCP server formulates DHCP ACK
    DHCP IP
    Eth arriving mobile: containing client’s IP address, IP address
    of first-hop router for client, name & IP
    DHCP

    DHCP Phy DHCP client


    address of DNS server
    DHCP
    DHCP  encapsulation at DHCP server, frame
    forwarded (switch learning) through LAN,
    DHCP
    UDP
    DHCP
    IP
    DHCP
    Eth demultiplexing at client
    DHCP Phy
    router has
    DHCP server  DHCP client receives DHCP ACK reply

    Client now has IP address, knows name & addr of DNS


    server, IP address of its first-hop router
    Link Layer: 6-5
    A day in the life… ARP (before DNS, before HTTP)
    DNS DNS  before sending HTTP request, need IP address
    UDP
    of www.google.com: DNS
    DNS

    ARP IP
    DNS
    ARP query Eth arriving mobile:
    Phy ARP client  DNS query created, encapsulated in UDP,
    encapsulated in IP, encapsulated in Eth. To
    send frame to router, need MAC address of
    router interface: ARP
    ARP  ARP query broadcast, received by router, which
    Eth
    replies with ARP reply giving MAC address of
    ARP reply

    Phy
    router has router interface
    ARP server
     client now knows MAC address of first hop
    router, so can now send frame containing
    DNS query

    Link Layer: 6-6


    A day in the life… using DNS
    DNS
    DNS DNS
    DNS UDP
    DNS DNS  de-muxed to DNS
    DNS UDP
    DNS IP
    DNS IP  DNS replies to client
    Eth DNS
    DNS Phy
    DNS Eth
    server
    with IP address of
    Phy
    DNS
    www.google.com

    Comcast network
    68.80.0.0/13

     IP datagram
     IP datagram forwarded from campus
    containing DNS query
    network into Comcast network,
    forwarded via LAN
    routed (tables created by RIP, OSPF,
    switch from client to
    IS-IS and/or BGP routing protocols)
    1st hop router
    to DNS server
    Link Layer: 6-7
    A day in the life…TCP connection carrying HTTP
    HTTP
    HTTP  to send HTTP request,
    SYNACK
    SYN TCP
    SYNACK
    SYN IP client first opens TCP
    SYNACK
    SYN Eth
    Phy Airtel network
    socket to web server
    68.80.0.0/13
     TCP SYN segment (step 1 in TCP
    3-way handshake) inter-domain
    routed to web server
     web server responds with
    SYNACK
    SYN
    SYNACK
    SYN
    TCP
    IP
    TCP SYNACK (step 2 in TCP 3-
    SYNACK
    SYN Eth way handshake)
    Phy
    Google web server
     TCP connection established!
    64.233.169.105

    Link Layer: 6-8


    A day in the life… HTTP request/reply
    HTTP
    HTTP
    HTTP
    HTTP
    HTTP
    TCP
     HTTP request sent into
    HTTP
    HTTP IP  web page finally (!!!) TCP socket
    HTTP
    HTTP Eth displayed
    Phy Airtel network  IP datagram containing
    68.80.0.0/13
    HTTP request routed to
    www.google.com
     web server responds with
    HTTP
    HTTP
    HTTP
    TCP
    HTTP reply (containing web
    HTTP
    IP page)
    HTTP Eth
    Phy  IP datagram containing
    Google web server HTTP reply routed back to
    64.233.169.105
    client
    Link Layer: 6-9

    You might also like