Professional Documents
Culture Documents
networks
Network layer
Sosina M.
Addis Ababa institute of technology
Data communication & computer networks 2012 E.C.
Network layer protocols
Address mapping
Maps a logical address to its corresponding physical address and vice versa
Static mapping
Creation of a table that associates a logical address with a physical address
Dynamic mapping
A machine that knows one of the two addresses, can use a protocol to find the other one
Cache memory
ARP rely is stored in the cache memory (for about 20 to 30 minutes)
Before sending ARP request, the system first checks it cache
Packet format
Finds the logical address for a machine that knows only its physical address
A RARP request is created and broadcasted on the local network
A machine on the local network that knows all the IP addresses will respond with a
RARP reply
The requesting machine must be running a RARP client program
The responding machine must be running a RARP server program
BOOTP
A client/server protocol designed to provide physical address to logical address
mapping
An application layer protocol
A client uses all 0s as the source address and all 1s as the destination
address
But, a broadcast IP datagram cannot passes through any router
One of the host can be used as a relay agent
The relay agent knows the address of a BOOTP server
Encapsulates the message in a unicast datagram and sends the request to the BOOTP
server
The relay agent, after receiving the reply, sends it to the BOOTP client
Data communication & computer networks 10
BOOTP
DHCP provides static and dynamic address allocation that can be manual
or automatic
Static address allocation (manual configuration)
DHCP acts as BOOTP does
Dynamic address allocation (dynamic configuration)
Pool of available IP addresses
When a DHCP client requests a temporary IP address, the DHCP assigns one the available
addresses in the pool for a negotiable period of time
Error reporting
ICMP reports error ( doesn’t correct error)
Error messages are always sent to the original source
Error types
Destination unreachable
Error => A router cannot route a datagram or a host cannot deliver a datagram
Source quench
Error => a datagram is discarded due to congestion
Warns the source that there is a congestion somewhere in the path and that the source should
slow down the sending process
Time exceeded
Error=>TTL value reaches zero or not all fragments that make up a message arrive at the
destination host within a certain time limit
Parameter problem
Error=> ambiguous or missing value in any field of the datagram
Redirection
Redirection message to the sending host
Ping
The source host sends ICMP each request messages
The destination responds with ICMP echo-reply message
Used to trace the route of packet from the source to the destination
For each group there is one router that has the duty of distributing the multicast
packets destined for that group
A host or multicast router can have membership in a group
Default method
The routing table is sorted from longest mask to the shortest mask
The least-cost route between any two nodes is the route with minimum
distance
Each node maintains a vector of minimum distance to every node
Each node shares it routing table with its immediate neighbors periodically and when
there is a change
Initialization
Updating
Solutions
Defining infinity – to redefine infinity to a smaller number
Most implementation define Infinity=16
Implies - the distance vector routing cannot be used in large system
Split horizon
Each node sends only part of its table through each interface
If the optimum path to x is through A, the node doesn’t advertise this piece of information to A
Split horizon and poison reverse
DV- if there is no news about a route within a giver time, the node deletes the route
Node B can still advertise the value for X, but if the source of information is A, it can replace the
distance with infinity
When the instability is between three nodes, split horizon and poison
reverse cannot guarantee stability
The loop stops when the cost in each node reaches infinity
Each node has the entire topology of the domain, the list of nodes and link,
how they are connected (type, cost, condition of the link (up or down)
Employs Dijkstra's algorithm
The whole topology is established from partial knowledge of each node
Contains
Node identity
List of links
Sequence number
To distinguished new LSP from old ones
Age
Prevents old LSPs from remaining in the domain for a long time
Generated
When there is a change in the topology of the domain
On a periodic basis
The creating node sends a copy of the LSP out of each interface
A node that receives an LSP compares it with the copy it may already have
If older than the one it has – discards the LSP
Otherwise, sends a copy of it out of each interface except the one from which the
packet arrived
There is one node (can be more than one) in each AS that acts on behalf of
the entire AS
Let us call it the speaker node
The speaker node in an AS creates a routing table and advertises it to
speaker nodes in the neighboring Ass
speaker node advertises the path, not the metric of the nodes
Updating
When a speaker node receives a two-column table from a neighbor, it updates its
own table
The instability of distance vector routing and the creation of loops can be
avoided in path vector routing
When a router receives a message, it checks to see if its AS is in the path list to the
destination.
If it is, looping is involved and the message is ignored
Policy routing
When a router receives a message, it can check the path
If one of the autonomous systems listed in the path is against its policy, it can ignore
that path and that destination
Optimum path
The optimum path is the path that fits the organization