Lectures notes for 2010 - KTH
Lectures notes for 2010 - KTH Lectures notes for 2010 - KTH
RIP extensions (aka RIP-2) Defined in RFC 1388 [3] and revised in RFC 2453[4]. Version number is 2. • for each of up to 25 entries we add the fields: • Route tag - carries the AS number • Subnetmask - subnetmask to be used with this address (to support classless addressing) • Next-hop IP address, either the IP address of where packets to this destination should be sent or zero [which means send them to the system which sent the RIP message] • One entry can be replaced by Authentication data RIP-2 supports multicast to address 224.0.0.9, to reduce load on hosts not interested in RIP-2 messages 0 7 8 15 16 23 24 31 Command Version = 2 Reserved 0xFFFF Authentication type Authentication data (16 bytes) if Authentication type = 2, this is a clear text password to be used to authenticate this message Family Network Address Subnet mask Next-hop address Distance Figure 4: RIPv2 message format (see Forouzan figures 14.13 pg. 397 and 14.14 pg. 398) Route tag Maguire RIP extensions (aka RIP-2) 7: 19 of 70 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
Why would anyone use RIP? After all these problems you might ask this question. Answer • Because RIP is generally the only routing protocol which all UNIX machines understand! • Relatively easy to configure • It it widely available, since it must exist if the device is capable of routing! Maguire Why would anyone use RIP? 7: 20 of 70 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
- Page 395 and 396: COOKIE ECHO Chunk 0 7 8 15 16 23 24
- Page 397 and 398: Data Chunk 0 7 8 15 16 23 24 31 Typ
- Page 399 and 400: Selective Acknowledgement (SACK) Ch
- Page 401 and 402: Association Termination Two forms o
- Page 403 and 404: 0 7 8 15 16 23 24 31 Type = 14 Flag
- Page 405 and 406: ethereal capture - daytime - INIT F
- Page 407 and 408: ethereal capture - daytime - COOKIE
- Page 409 and 410: ethereal capture - daytime - DATA F
- Page 411 and 412: ethereal capture - daytime - SHUTDO
- Page 413 and 414: ethereal capture - daytime - SHUTDO
- Page 415 and 416: HEARTBEAT and HEARTBEAT ACK Chunks
- Page 417 and 418: Differences from TCP Congestion Con
- Page 419 and 420: 3 When retransmitting to a remote a
- Page 421 and 422: Forward Cumulative TSN Allows an en
- Page 423 and 424: SCTP Performance See the upcoming e
- Page 425 and 426: Summary This lecture we have discus
- Page 427 and 428: 2002 http://www.ietf.org/rfc/rfc330
- Page 429 and 430: • Dynamic Routing Protocols Outli
- Page 431 and 432: Routing Principles • Routing Mech
- Page 433 and 434: Processing Rouing daemon route comm
- Page 435 and 436: Autonomous systems (ASs) - RFC1930
- Page 437 and 438: Routing Algorithms • Static vs. D
- Page 439 and 440: Routing Information Protocol (RIP)
- Page 441 and 442: When are routes sent? Solicited res
- Page 443 and 444: Count to Infinity C network 1 netwo
- Page 445: Triggered updates and Hold-Downs To
- Page 449 and 450: IGRP Metrics • a vector of metric
- Page 451 and 452: IGRP Default Gateway Rather than us
- Page 453 and 454: Open Shortest Path First (OSPF) OSP
- Page 455 and 456: OSPF building blocks 1. Hello proto
- Page 457 and 458: Hello packet 0 7 8 15 16 23 24 31 V
- Page 459 and 460: Link State Announcement (LSA) heade
- Page 461 and 462: Link state update packet 0 7 8 15 1
- Page 463 and 464: Link state acknowledgement packet 0
- Page 465 and 466: Exterior Gateway Protocol (EGP) an
- Page 467 and 468: Local vs. Transit traffic Local tra
- Page 469 and 470: BGP does not transmit metrics. Howe
- Page 471 and 472: Redistribution of Route Information
- Page 473 and 474: • Open • Update • Keepalive
- Page 475 and 476: BGP Update Message 0 7 8 15 16 23 2
- Page 477 and 478: BGP Notification Message 0 7 8 15 1
- Page 479 and 480: Federal Internet eXchange (FIX) A t
- Page 481 and 482: Global Internet eXchange (GIX) Glob
- Page 483 and 484: Network Access Points (NAPs) At the
- Page 485 and 486: Router Arbiter Project Router Arbit
- Page 487 and 488: Euro6IX The European IPv6 Internet
- Page 489 and 490: Flows A flow is defined as a “uni
- Page 491 and 492: A Tag Edge router labels a packet b
- Page 493 and 494: Creating tags Since tag switching d
- Page 495 and 496: Summary This lecture we have discus
RIP extensions (aka RIP-2)<br />
Defined in RFC 1388 [3] and revised in RFC 2453[4]. Version number is 2.<br />
• <strong>for</strong> each of up to 25 entries we add the fields:<br />
• Route tag - carries the AS number<br />
• Subnetmask - subnetmask to be used with this address (to support classless addressing)<br />
• Next-hop IP address, either the IP address of where packets to this destination should be<br />
sent or zero [which means send them to the system which sent the RIP message]<br />
• One entry can be replaced by Authentication data<br />
RIP-2 supports multicast to address 224.0.0.9, to reduce load on hosts not interested in RIP-2 messages<br />
0 7 8 15 16 23 24 31<br />
Command Version = 2 Reserved<br />
0xFFFF<br />
Authentication type<br />
Authentication data (16 bytes)<br />
if Authentication type = 2, this is a clear text password to be used to authenticate this message<br />
Family<br />
Network Address<br />
Subnet mask<br />
Next-hop address<br />
Distance<br />
Figure 4: RIPv2 message <strong>for</strong>mat (see Forouzan figures 14.13 pg. 397 and 14.14 pg. 398)<br />
Route tag<br />
Maguire RIP extensions (aka RIP-2) 7: 19 of 70<br />
maguire@kth.se <strong>2010</strong>.03.21 Internetworking/Internetteknik