Header
Home | Set as homepage | Add to favorites
  Search the Site     » Advanced Search
Sections
Syndication


Blogroll:

||||| ALL Cisco-Network ARTICLES |||||  
CCIE Journey,
The CCIE Journey,


You Can't Just Send DataYou Have to Send a Frame Relay Frame

Nov 25,2008 by alperen

image

You Can't Just Send DataYou Have to Send a Frame Relay Frame

In this example, Hannah will be opening a browser to connect to the www.example.com website. After using DNS to discover that www.example.com's IP address is 150.1.3.3, Hannah sends a packet to 150.1.3.3. Because 150.1.3.3 is in a different subnet, Hannah's PC sends the packet to her default gatewaynamely, R1. When R1 receives the Ethernet frame, it checks to see if errors occurred. If no errors occurred, R1 extracts the IP packet and begins the process of making a routing decision.

Figure 15-9 picks up the routing process at this point. R1 has the packet with destination address 150.1.3.3. That destination address matches the route for subnet 150.1.3.0, which lists outgoing interface Serial0, and next-hop IP address 150.1.2.2, which is R2's IP address on its serial0 interface.


121 times read

Related news

» You Can't Just Send Data; You Have to Send a Frame
by alperen posted on Nov 25,2008
» Yet Another Short-Lived Ethernet Frame
by alperen posted on Nov 24,2008
» R2's Routing TableSame Destinations, Different Instructions
by alperen posted on Nov 24,2008
» The Still Useful, but Still Short Life of an Ethernet Frame
by alperen posted on Nov 24,2008
» Encapsulating an IP Packet in an Ethernet Frame
by alperen posted on Nov 24,2008
Did you enjoy this article?
(total 0 votes)

comment Comments (0 posted) 

More Top News
CCSP-Cisco Certified Security Professional
Most Popular
Most Commented
Featured Author