CS 457 Networking and the Internet. Shortest-Path Problem. Dijkstra s Shortest-Path Algorithm 9/29/16. Fall 2016

Transcription

1 9/9/6 S 7 Networking and the Internet Fall 06 Shortest-Path Problem Given: network topology with link costs c(x,y): link cost from node x to node y Infinity if x and y are not direct neighbors ompute: least-cost paths to all nodes From a given source u to all other nodes p(v): predecessor node along path from source to v u p(v) v Dijkstra s Shortest-Path lgorithm Iterative algorithm fter k iterations, know least-cost path to k nodes S: nodes whose least-cost path definitively known Initially, S = {u} where u is the source node dd one node to S in each iteration D(v): current cost of path from source to node v Initially, D(v) = c(u,v) for all nodes v adjacent to u and D(v) = for all other nodes v ontinually update D(v) as shorter paths are learned

2 9/9/6 Dijsktra s Shortest Path lgorithm Notation: Initialization: c(x,y): link cost from node x to y; = if not direct neighbors N' = {u} D(v): current value of cost of path for all nodes v from source to dest. v if v adjacent to u p(v): predecessor node along path then D(v) = c(u,v) from source to v 6 else D(v) = N': set of nodes whose least cost path is definitively known 7 8 Loop 9 find w not in N' such that D(w) is a minimum 0 add w to N' update D(v) for all v adjacent to w and not in N' : D(v) = min( D(v), D(w) + c(w,v) ) /* new cost to v is either old cost to v or known shortest path cost to w plus cost from w to v */ until all nodes in N' Dijkstra s lgorithm Example Dijkstra s lgorithm Example

3 9/9/6 Shortest-Path Tree Shortest-path tree from u u v w x s y t Forwarding table at u link z v (u,v) w (u,w) x (u,w) y (u,v) z (u,v) s (u,w) t (u,w) Dijkstra s lgorithm Limitations lgorithm complexity: n nodes each iteration: need to check all nodes, w, not in N n(n+)/ comparisons: O(n ) more efficient implementations possible: O(mlogn) Oscillations possible when link costs change: e.g., link cost = amount of carried traffic +e D 0 0 B 0 e e initially +e 0 D B 0 +e 0 recompute routing 0 +e D 0 B 0 +e recompute +e 0 D B 0 +e e recompute Link-State Routing Each router keeps track of its incident links Whether the link is up or down The cost on the link Each router broadcasts the link state To give every router a complete view of the graph Each router runs Dijkstra s algorithm To compute the shortest paths and construct the forwarding table Example protocols Open Shortest Path First (OSPF) Intermediate System Intermediate System (IS-IS)

4 9/9/6 Detecting Topology hanges Beaconing Periodic hello messages in both directions Detect a failure after a few missed hellos hello Performance trade-offs Detection speed Overhead on link bandwidth and PU Likelihood of false detection Broadcasting the Link State Flooding Node sends link-state information out its links nd then the next node sends out all of its links except the one where the information arrived X X B D (a) B D (b) X X B D (c) B D (d) Broadcasting the Link State Reliable flooding Ensure all nodes receive link-state information and that they use the latest version hallenges Packet loss Out-of-order arrival Solutions cknowledgments and retransmissions Sequence numbers Time-to-live for each packet

5 9/9/6 When to Initiate Flooding Topology change Link or node failure Link or node recovery onfiguration change Link cost change Periodically Refresh the link-state information Typically (say) 0 minutes orrects for possible corruption of the data onvergence Getting consistent routing information to all nodes E.g., all nodes having the same link-state database onsistent forwarding after convergence ll nodes have the same link-state database ll nodes forward packets on shortest paths The next router on the path forwards to the next hop Transient Disruptions Detection delay node does not detect a failed link immediately and forwards data packets into a blackhole Depends on timeout for detecting lost hellos

6 9/9/6 Transient Disruptions Inconsistent link-state database Some routers know about failure before others The shortest paths are no longer consistent an cause transient forwarding loops onvergence Delay Sources of convergence delay Detection latency Flooding of link-state information Shortest-path computation reating the forwarding table Performance during convergence period Lost packets due to blackholes and TTL expiry Looping packets consuming resources Out-of-order packets reaching the destination Very bad for VoIP, online gaming, and video Reducing onvergence Delay Faster detection Smaller hello timers Link-layer technologies that can detect failures Faster flooding Flooding immediately Sending link-state packets with high-priority Faster computation Faster processors on the routers Incremental Dijkstra algorithm Faster forwarding-table update Data structures supporting incremental updates 6

7 9/9/6 omparison of LS and DV algorithms Message complexity LS: with n nodes, E links, O(nE) messages sent DV: exchange between neighbors only onvergence time varies Speed of onvergence LS: O(n ) algorithm requires O(nE) messages DV: convergence time varies May be routing loops ount-to-infinity problem Robustness: what happens if router malfunctions? LS: Node can advertise incorrect link cost Each node computes only its own table DV: DV node can advertise incorrect path cost Each node s table used by others (error propagates) Summary Routing is a distributed algorithm React to changes in the topology ompute the shortest paths Two main shortest-path algorithms Dijkstra à link-state routing (e.g., OSPF and IS-IS) Bellman-Ford à distance vector routing (e.g., RIP) onvergence process hanging from one topology to another Transient periods of inconsistency across routers Routing in Practice 7

8 9/9/6 RIP (Routing Information Protocol) Distance vector algorithm Included in BSD-UNIX Distribution in 98 Distance metric: # of hops (max = hops) Distance vectors: exchanged among neighbors every 0 sec via Response Message (also called advertisement) Each advertisement: list of up to destination nets RIP: Example w x y D B z Destination Network Next Router Num. of hops to dest. w y B z B 7 x Routing table in D RIP: Example Dest Next hops w - - x - - z.... dvertisement from to D w x y D B z Destination Network Next Router Num. of hops to dest. w y B z B 7 x Routing table in D 8

9 9/9/6 RIP: Link Failure and Recovery If no advertisement heard after 80 sec --> neighbor/link declared dead routes via neighbor invalidated new advertisements sent to neighbors neighbors in turn send out new advertisements (if tables changed) link failure info quickly propagates to entire net poison reverse used to prevent ping-pong loops (infinite distance = 6 hops) RIP Table processing RIP routing tables managed by application-level process called route-d (daemon) advertisements sent in UDP packets, periodically repeated routed routed Transport (UDP) Network (IP) Link Physical Forwarding Table Forwarding Table Transport (UDP) Network (IP) Link Physical RIP Table example (continued) Router: giroflee.eurocom.fr Destination Gateway Flags Ref Use Interface UH 0 69 lo U fa U 80 le U qaa U 0 le0 default UG 0 Three attached networks (LNs) Router only knows routes to attached LNs Default router used to go up Route multicast address: Loopback interface (for debugging) 9

10 9/9/6 OSPF (Open Shortest Path First) open : publicly available Uses Link State algorithm LS packet dissemination Topology map at each node Route computation using Dijkstra s algorithm OSPF advertisement carries one entry per neighbor router dvertisements disseminated via flooding arried in OSPF messages directly over IP (rather than TP or UDP OSPF advanced features (not in RIP) Security: all OSPF messages authenticated (to prevent malicious intrusion) Multiple same-cost paths allowed (only one path in RIP) For each link, multiple cost metrics for different TOS (e.g., satellite link cost set low for best effort; high for real time) Integrated uni- and multicast support: Multicast OSPF (MOSPF) uses same topology data base as OSPF Hierarchical OSPF in large domains. Hierarchical Routing Our routing study thus far - idealization all routers identical network flat not true in practice scale: with 00 million destinations: can t store all dest s in routing tables! routing table exchange would swamp links! administrative autonomy internet = network of networks each network admin may want to control routing in its own network 0

11 9/9/6 Hierarchical Routing aggregate routers into regions, autonomous systems (S) routers in same S run same routing protocol intra-s routing protocol routers in different S can run different intra-s routing protocol gateway routers special routers in S run intra-s routing protocol with all other routers in S also responsible for routing to destinations outside S run inter-s routing protocol with other gateway routers Routing in the Internet The Global Internet consists of utonomous Systems (S) interconnected with each other: Stub S: small corporation: one connection to other S s Multihomed S: large corporation (no transit): multiple connections to other S s Transit S: provider, hooking many S s together Two-level routing: Intra-S: administrator responsible for choice of routing algorithm within network Inter-S: unique standard for inter-s routing: BGP Internet S Hierarchy Intra-S border (exterior gateway) routers Inter-S interior (gateway) routers Network Layer -

12 9/9/6 Intra-S Routing lso known as Interior Gateway Protocols (IGP) Most common Intra-S routing protocols: RIP: Routing Information Protocol OSPF: Open Shortest Path First IGRP: Interior Gateway Routing Protocol (isco proprietary) Intra-S and Inter-S routing a Host h.b b.a.c a d b c Intra-S routing within S Inter-S routing between and B B.a a B c b Intra-S routing within S B Host h We ll examine specific inter-s and intra-s Internet routing protocols shortly Intra-S and Inter-S routing a.b b d.a a b.c c B.a a B c Gateways: perform inter-s routing amongst themselves b perform intra-s routers with other routers in their S inter-s, intra-s routing in gateway.c network layer link layer physical layer

13 9/9/6 Hierarchical OSPF -7 Hierarchical OSPF Two-level hierarchy: local area, backbone. Link-state advertisements only in area each nodes has detailed area topology; only know direction (shortest path) to nets in other areas. rea border routers: summarize distances to nets in own area, advertise to other rea Border routers. Backbone routers: run OSPF routing limited to backbone. Boundary routers: connect to other S s. Network ddress Translation

14 9/9/6 NT: Network ddress Translation rest of Internet local network (e.g., home network) 0.0.0/ ll datagrams leaving local network have same single source NT IP address: , different source port numbers Datagrams with source or destination in this network have 0.0.0/ address for source, destination (as usual) NT: Network ddress Translation Motivation: local network uses just one IP address as far as outside word is concerned: no need to be allocated range of addresses from ISP: - just one IP address is used for all devices can change addresses of devices in local network without notifying outside world can change ISP without changing addresses of devices in local network devices inside local net not explicitly addressable, visible by outside world (a security plus). NT: Network ddress Translation Implementation: NT router must: outgoing datagrams: replace (source IP address, port #) of every outgoing datagram to (NT IP address, new port #)... remote clients/servers will respond using (NT IP address, new port #) as destination addr. remember (in NT translation table) every (source IP address, port #) to (NT IP address, new port #) translation pair incoming datagrams: replace (NT IP address, new port #) in dest fields of every incoming datagram with corresponding (source IP address, port #) stored in NT table

15 9/9/6 NT: Network ddress Translation : NT router changes datagram source addr from , to , 00, updates table NT translation table WN side addr LN side addr , , S: , 00 D: , S: , 80 D: , 00 : Reply arrives dest. address: , S: , D: , 80 S: , 80 D: , : host sends datagram to 8.9.0, : NT router changes datagram dest addr from , 00 to , NT: Network ddress Translation 6-bit port-number field: 60,000 simultaneous connections with a single LN-side address! NT is controversial: routers should only process up to layer violates end-to-end argument NT possibility must be taken into account by app designers, eg, PP applications address shortage should instead be solved by IPv6