{"id":1682,"date":"2020-11-28T18:47:00","date_gmt":"2020-11-28T17:47:00","guid":{"rendered":"http:\/\/blogperso.union31.fr\/?p=1682"},"modified":"2020-12-02T12:23:02","modified_gmt":"2020-12-02T11:23:02","slug":"gns3-rip-v2","status":"publish","type":"post","link":"https:\/\/blogperso.union31.fr\/?p=1682","title":{"rendered":"GNS3 : Rip V2"},"content":{"rendered":"\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Sommaire<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#I_Introduction\" >I Introduction<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#II_Configuration_initiale_des_routeurs\" >II Configuration initiale des routeurs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#II1_Routeur_R1\" >II.1 Routeur R1<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#II2_Routeur_R2_et_R3\" >II.2 Routeur R2 et R3<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#II3_Les_PC_virtuels_PC1_PC2_et_PC3\" >II.3 Les PC virtuels : PC1, PC2 et PC3<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#II4_Verifier_la_connectivite_des_elements\" >II.4 V\u00e9rifier la connectivit\u00e9 des \u00e9l\u00e9ments<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III_implementation_du_RIPv2\" >III impl\u00e9mentation du RIPv2<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III1_Listes_de_commandes_possibles\" >III.1 Listes de commandes possibles<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III2_configuration_des_routeurs\" >III.2 configuration des routeurs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III3_Verification\" >III.3 V\u00e9rification<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III4_Mode_debug\" >III.4 Mode debug<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III5_Optimisations\" >III.5 Optimisations<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III51_Option_%C2%AB_passive-interface_%C2%BB\" >III.5.1 Option \u00ab\u00a0passive-interface\u00a0\u00bb<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III42_Option_%C2%AB_auto-summary_%C2%BB\" >III.4.2 Option \u00ab\u00a0auto-summary\u00a0\u00bb<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#III5_Cas_dune_defaillance_dun_lien\" >III.5 Cas d&rsquo;une d\u00e9faillance d&rsquo;un lien<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#IV_Aller_plus_loin\" >IV Aller plus loin<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#IV1_Securisation_des_echanges_RIP_entre_routeurs\" >IV.1 S\u00e9curisation des \u00e9changes RIP entre routeurs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/blogperso.union31.fr\/?p=1682\/#IV2_Pour_aller_plus_loin_et_comprendre_dautres_options_du_RIP\" >IV.2 Pour aller plus loin et comprendre d&rsquo;autres options du RIP<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"I_Introduction\"><\/span>I Introduction<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Comment impl\u00e9menter un routage dynamique entre 3 routeurs avec le protocole RIP v2.<\/p>\n\n\n\n<p>Sch\u00e9ma de travail :<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"566\" src=\"http:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1-1024x566.png\" alt=\"\" class=\"wp-image-1684\" srcset=\"https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1-1024x566.png 1024w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1-300x166.png 300w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1-768x424.png 768w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1.png 1280w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Nous aurons 3 routeurs interconnect\u00e9s entre eux. Chaque routeur dessert un VLAN propre.<\/p>\n\n\n\n<p>L&rsquo;objectif est d&rsquo;impl\u00e9menter le protocole RIPv2 pour que les tables de routages de chaque routeur se mettent \u00e0 jour automatiquement.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"II_Configuration_initiale_des_routeurs\"><\/span>II Configuration initiale des routeurs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>La configuration initiale de chaque routeur consiste \u00e0 :<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>d\u00e9clarer le vlan<\/li><li>donner une adresse IP de passerelle des VLAN<\/li><li>fixer les adresses IP des ports connect\u00e9s vers las autres routeurs<\/li><\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"II1_Routeur_R1\"><\/span>II.1 Routeur R1<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#vlan database \nR1(vlan)#vlan 10\nVLAN 10 added:\n    Name: VLAN0010\nR1(vlan)#apply\nAPPLY completed.\nR1(vlan)#exit\nAPPLY completed.\nExiting....\n\nR1#conf t\nR1(config)#interface fastEthernet 1\/0\nR1(config-if)#no switchport \nR1(config-if)#ip address 192.168.100.1 255.255.255.0\nR1(config-if)#no shutdown\nR1(config-if)#exit\nR1(config)#interface fastEthernet 1\/1\nR1(config-if)#no switchport \nR1(config-if)#ip address 192.168.101.1 255.255.255.0   \nR1(config-if)#no shutdown\nR1(config-if)#exit\nR1(config)#interface range fastEthernet 1\/2 -15\nR1(config-if-range)#switchport \nR1(config-if-range)#switchport mode access \nR1(config-if-range)#switchport acces vlan 10\nR1(config-if-range)#no shutdown \nR1(config-if-range)#exit\nR1(config)#exit<\/code><\/pre>\n\n\n\n<p>V\u00e9rification de la pr\u00e9sence du LAN :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show vlan-switch brief \n\nVLAN Name                             Status    Ports\n---- -------------------------------- --------- -------------------------------\n1    default                          active    \n10   VLAN0010                         active    Fa1\/2, Fa1\/3, Fa1\/4, Fa1\/5\n                                                Fa1\/6, Fa1\/7, Fa1\/8, Fa1\/9\n                                                Fa1\/10, Fa1\/11, Fa1\/12, Fa1\/13\n                                                Fa1\/14, Fa1\/15\n1002 fddi-default                     active    \n1003 token-ring-default               active    \n1004 fddinet-default                  active    \n1005 trnet-default                    active    \n<\/code><\/pre>\n\n\n\n<p>V\u00e9rification des interfaces :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show ip interface brief \nInterface                  IP-Address      OK? Method Status                Protocol\nFastEthernet0\/0            unassigned      YES NVRAM  administratively down down    \nFastEthernet0\/1            unassigned      YES NVRAM  administratively down down    \nFastEthernet1\/0            192.168.100.1   YES NVRAM  up                    up      \nFastEthernet1\/1            192.168.101.1   YES NVRAM  up                    up      \nFastEthernet1\/2            unassigned      YES unset  up                    down    \nFastEthernet1\/3            unassigned      YES unset  up                    down    \nFastEthernet1\/4            unassigned      YES unset  up                    down    \nFastEthernet1\/5            unassigned      YES unset  up                    down    \nFastEthernet1\/6            unassigned      YES unset  up                    down    \nFastEthernet1\/7            unassigned      YES unset  up                    down    \nFastEthernet1\/8            unassigned      YES unset  up                    down    \nFastEthernet1\/9            unassigned      YES unset  up                    down    \nFastEthernet1\/10           unassigned      YES unset  up                    down    \nFastEthernet1\/11           unassigned      YES unset  up                    down    \nFastEthernet1\/12           unassigned      YES unset  up                    down    \nFastEthernet1\/13           unassigned      YES unset  up                    down    \nFastEthernet1\/14           unassigned      YES unset  up                    down    \nFastEthernet1\/15           unassigned      YES unset  up                    up      \nVlan1                      unassigned      YES NVRAM  up                    down    \nVlan10                     192.168.10.254  YES NVRAM  up                    up      \n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"II2_Routeur_R2_et_R3\"><\/span>II.2 Routeur R2 et R3<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Effectuer les m\u00eames type d&rsquo;op\u00e9rations que pour le routeur R1 en indiquant les valeurs appropri\u00e9es.<\/p>\n\n\n\n<p>V\u00e9rifier que les r\u00e9sultats soient identiques.<\/p>\n\n\n\n<p>Routeur R2 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R2#show ip interface brief \nInterface                  IP-Address      OK? Method Status                Protocol\nFastEthernet0\/0            unassigned      YES NVRAM  administratively down down    \nFastEthernet0\/1            unassigned      YES NVRAM  administratively down down    \nFastEthernet1\/0            192.168.100.2   YES NVRAM  up                    up      \nFastEthernet1\/1            192.168.102.1   YES NVRAM  up                    up      \nFastEthernet1\/2            unassigned      YES unset  up                    down    \nFastEthernet1\/3            unassigned      YES unset  up                    down    \nFastEthernet1\/4            unassigned      YES unset  up                    down    \nFastEthernet1\/5            unassigned      YES unset  up                    down    \nFastEthernet1\/6            unassigned      YES unset  up                    down    \nFastEthernet1\/7            unassigned      YES unset  up                    down    \nFastEthernet1\/8            unassigned      YES unset  up                    down    \nFastEthernet1\/9            unassigned      YES unset  up                    down    \nFastEthernet1\/10           unassigned      YES unset  up                    down    \nFastEthernet1\/11           unassigned      YES unset  up                    down    \nFastEthernet1\/12           unassigned      YES unset  up                    down    \nFastEthernet1\/13           unassigned      YES unset  up                    down    \nFastEthernet1\/14           unassigned      YES unset  up                    down    \nFastEthernet1\/15           unassigned      YES unset  up                    up      \nVlan1                      unassigned      YES NVRAM  up                    down    \nVlan20                     192.168.20.254  YES NVRAM  up                    up      \n<\/code><\/pre>\n\n\n\n<p>Routeur R3 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R3#show ip interface brief \nInterface                  IP-Address      OK? Method Status                Protocol\nFastEthernet0\/0            unassigned      YES NVRAM  administratively down down    \nFastEthernet0\/1            unassigned      YES NVRAM  administratively down down    \nFastEthernet1\/0            192.168.101.2   YES NVRAM  up                    up      \nFastEthernet1\/1            192.168.102.2   YES NVRAM  up                    up      \nFastEthernet1\/2            unassigned      YES unset  up                    down    \nFastEthernet1\/3            unassigned      YES unset  up                    down    \nFastEthernet1\/4            unassigned      YES unset  up                    down    \nFastEthernet1\/5            unassigned      YES unset  up                    down    \nFastEthernet1\/6            unassigned      YES unset  up                    down    \nFastEthernet1\/7            unassigned      YES unset  up                    down    \nFastEthernet1\/8            unassigned      YES unset  up                    down    \nFastEthernet1\/9            unassigned      YES unset  up                    down    \nFastEthernet1\/10           unassigned      YES unset  up                    down    \nFastEthernet1\/11           unassigned      YES unset  up                    down    \nFastEthernet1\/12           unassigned      YES unset  up                    down    \nFastEthernet1\/13           unassigned      YES unset  up                    down    \nFastEthernet1\/14           unassigned      YES unset  up                    down    \nFastEthernet1\/15           unassigned      YES unset  up                    up      \nVlan1                      unassigned      YES NVRAM  up                    down    \nVlan30                     192.168.30.254  YES NVRAM  up                    up     <\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"II3_Les_PC_virtuels_PC1_PC2_et_PC3\"><\/span>II.3 Les PC virtuels : PC1, PC2 et PC3<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Il faut configurer les adresses IP des PC virtuels manuellement et indiquer la gateway sur chacun.<\/p>\n\n\n\n<p>Sous GNS3, click droit sur l&rsquo;ic\u00f4ne du PC vituel, puis cliquer sur \u00ab\u00a0Edit config\u00a0\u00bb.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"710\" src=\"http:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC-1024x710.png\" alt=\"\" class=\"wp-image-1699\" srcset=\"https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC-1024x710.png 1024w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC-300x208.png 300w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC-768x533.png 768w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC.png 1064w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Rajouter la ligne indiquant l&rsquo;adresse IP et la gateaway.<\/p>\n\n\n\n<p>Effectuer le m\u00eame type de param\u00e9trage pour les 2 autres PC virtuels avec les valeurs d\u00e9di\u00e9es.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"II4_Verifier_la_connectivite_des_elements\"><\/span>II.4 V\u00e9rifier la connectivit\u00e9 des \u00e9l\u00e9ments<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Les PC doivent pinguer leurs adresses de passerelles :<\/p>\n\n\n\n<figure class=\"wp-block-image size-large is-style-default\"><img loading=\"lazy\" decoding=\"async\" width=\"1013\" height=\"375\" src=\"http:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC_ping.png\" alt=\"\" class=\"wp-image-1704\" srcset=\"https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC_ping.png 1013w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC_ping-300x111.png 300w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_VPC_ping-768x284.png 768w\" sizes=\"auto, (max-width: 1013px) 100vw, 1013px\" \/><\/figure>\n\n\n\n<p>Les routeurs doivent pinguer :<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>les autres @IP des routeurs qui sont en face d&rsquo;eux<\/li><li>l&rsquo;@ip du PC Virtuel<\/li><li>l&rsquo;@ip de la gateaway du VLAN<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"449\" src=\"http:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_R1_ping-1-1024x449.png\" alt=\"\" class=\"wp-image-1709\" srcset=\"https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_R1_ping-1-1024x449.png 1024w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_R1_ping-1-300x132.png 300w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_R1_ping-1-768x337.png 768w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_conf_R1_ping-1.png 1494w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Faire de m\u00eame pour les routeurs R2 et R3.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III_implementation_du_RIPv2\"><\/span>III impl\u00e9mentation du RIPv2<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III1_Listes_de_commandes_possibles\"><\/span>III.1 Listes de commandes possibles <span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>R1(config-router)#?\nRouter configuration commands:\n  address-family          Enter Address Family command mode\n  auto-summary            Enable automatic network number summarization\n  default                 Set a command to its defaults\n  default-information     Control distribution of default information\n  default-metric          Set metric of redistributed routes\n  distance                Define an administrative distance\n  distribute-list         Filter networks in routing updates\n  exit                    Exit from routing protocol configuration mode\n  flash-update-threshold  Specify flash update threshold in second\n  help                    Description of the interactive help system\n  input-queue             Specify input queue depth\n  maximum-paths           Forward packets over multiple paths\n  neighbor                Specify a neighbor router\n  network                 Enable routing on an IP network\n  no                      Negate a command or set its defaults\n  offset-list             Add or subtract offset from RIP metrics\n  output-delay            Interpacket delay for RIP updates\n  passive-interface       Suppress routing updates on an interface\n  redistribute            Redistribute information from another routing\n                          protocol\n  timers                  Adjust routing timers\n  traffic-share           How to compute traffic share over alternate paths\n  validate-update-source  Perform sanity checks against source address of\n                          routing updates\n  version                 Set routing protocol version<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III2_configuration_des_routeurs\"><\/span>III.2 configuration des routeurs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Il faut activer le protocole et d\u00e9finir les r\u00e9seaux de communication du routeur.<\/p>\n\n\n\n<p>Routeur R1 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#conf t\nR1(config)#router rip\nR1(config-router)#version 2\nR1(config-router)#network 192.168.10.0\nR1(config-router)#network 192.168.101.0\nR1(config-router)#network 192.168.100.0\nR1(config-router)#exit<\/code><\/pre>\n\n\n\n<p>Routeur R2 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R2#conf t\nR2(config)#router rip\nR2(config-router)#version 2\nR2(config-router)#network 192.168.20.0\nR2(config-router)#network 192.168.100.0\nR2(config-router)#network 192.168.102.0\nR2(config-router)#exit<\/code><\/pre>\n\n\n\n<p>Router R3 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R3#conf t\nR3(config)#router rip\nR3(config-router)#version 2\nR3(config-router)#network 192.168.30.0\nR3(config-router)#network 192.168.101.0\nR3(config-router)#network 192.168.102.0\nR3(config-router)#exit<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III3_Verification\"><\/span>III.3 V\u00e9rification<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Attendre quelques minutes puis regarder la table de routage.<\/p>\n\n\n\n<p>Table de routage pour R1 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show ip route \nCodes: C - connected, S - static, R - RIP, M - mobile, B - BGP\n       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area \n       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2\n       E1 - OSPF external type 1, E2 - OSPF external type 2\n       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2\n       ia - IS-IS inter area, * - candidate default, U - per-user static route\n       o - ODR, P - periodic downloaded static route\n\nGateway of last resort is not set\n\nR    192.168.30.0\/24 &#91;120\/1] via 192.168.101.2, 00:00:24, FastEthernet1\/1\nC    192.168.10.0\/24 is directly connected, Vlan10\nR    192.168.20.0\/24 &#91;120\/1] via 192.168.100.2, 00:00:03, FastEthernet1\/0\nR    192.168.102.0\/24 &#91;120\/1] via 192.168.101.2, 00:00:24, FastEthernet1\/1\n                      &#91;120\/1] via 192.168.100.2, 00:00:03, FastEthernet1\/0\nC    192.168.100.0\/24 is directly connected, FastEthernet1\/0\nC    192.168.101.0\/24 is directly connected, FastEthernet1\/1\n<\/code><\/pre>\n\n\n\n<p>Table de routage pour R2 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R2#show ip route rip\nR    192.168.30.0\/24 &#91;120\/1] via 192.168.102.2, 00:00:13, FastEthernet1\/1\nR    192.168.10.0\/24 &#91;120\/1] via 192.168.100.1, 00:00:10, FastEthernet1\/0\nR    192.168.101.0\/24 &#91;120\/1] via 192.168.102.2, 00:00:13, FastEthernet1\/1\n                      &#91;120\/1] via 192.168.100.1, 00:00:10, FastEthernet1\/0<\/code><\/pre>\n\n\n\n<p>Table de routage pour R3 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R3#show ip route Rip\nR    192.168.10.0\/24 &#91;120\/1] via 192.168.101.1, 00:00:14, FastEthernet1\/0\nR    192.168.20.0\/24 &#91;120\/1] via 192.168.102.1, 00:00:27, FastEthernet1\/1\nR    192.168.100.0\/24 &#91;120\/1] via 192.168.102.1, 00:00:27, FastEthernet1\/1\n                      &#91;120\/1] via 192.168.101.1, 00:00:14, FastEthernet1\/0<\/code><\/pre>\n\n\n\n<p>Pour avoir plus d&rsquo;information sur le protole, utiliser la commnde suivante :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show ip protocols \nRouting Protocol is \"rip\"\n  Outgoing update filter list for all interfaces is not set\n  Incoming update filter list for all interfaces is not set\n  Sending updates every 30 seconds, next due in 18 seconds\n  Invalid after 180 seconds, hold down 180, flushed after 240\n  Redistributing: rip\n  Default version control: send version 2, receive version 2\n    Interface             Send  Recv  Triggered RIP  Key-chain\n    FastEthernet1\/0       2     2                                    \n    FastEthernet1\/1       2     2                                    \n    Vlan10                2     2                                    \n  Automatic network summarization is not in effect\n  Maximum path: 4\n  Routing for Networks:\n    192.168.10.0\n    192.168.100.0\n    192.168.101.0\n  Routing Information Sources:\n    Gateway         Distance      Last Update\n    192.168.100.2        120      00:00:25\n    192.168.101.2        120      00:00:20\n  Distance: (default is 120)<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III4_Mode_debug\"><\/span>III.4 Mode debug<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Il est toujours interressant de voir si le protocole RIP fonctionne.<\/p>\n\n\n\n<p>Pour cela il faut activer le mode debug<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#debug ip rip\nRIP protocol debugging is on\nR1#\n*Mar  1 00:48:24.559: RIP: received v2 update from 192.168.100.2 on FastEthernet1\/0\n*Mar  1 00:48:24.559:      192.168.20.0\/24 via 0.0.0.0 in 1 hops\n*Mar  1 00:48:24.563:      192.168.30.0\/24 via 0.0.0.0 in 2 hops\n*Mar  1 00:48:24.563:      192.168.102.0\/24 via 0.0.0.0 in 1 hops\nR1#\n*Mar  1 00:48:27.475: RIP: received v2 update from 192.168.101.2 on FastEthernet1\/1\n*Mar  1 00:48:27.475:      192.168.20.0\/24 via 0.0.0.0 in 2 hops\n*Mar  1 00:48:27.475:      192.168.30.0\/24 via 0.0.0.0 in 1 hops\n*Mar  1 00:48:27.479:      192.168.102.0\/24 via 0.0.0.0 in 1 hops\nR1#\n*Mar  1 00:48:32.991: RIP: sending v2 update to 224.0.0.9 via FastEthernet1\/0 (192.168.100.1)\n*Mar  1 00:48:32.991: RIP: build update entries\n*Mar  1 00:48:32.991: \t192.168.10.0\/24 via 0.0.0.0, metric 1, tag 0\n*Mar  1 00:48:32.991: \t192.168.30.0\/24 via 0.0.0.0, metric 2, tag 0\n*Mar  1 00:48:32.995: \t192.168.101.0\/24 via 0.0.0.0, metric 1, tag 0\n<\/code><\/pre>\n\n\n\n<p>Pour le d\u00e9sactiver :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#no debug ip rip\nRIP protocol debugging is off<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III5_Optimisations\"><\/span>III.5 Optimisations<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III51_Option_%C2%AB_passive-interface_%C2%BB\"><\/span>III.5.1 Option \u00ab\u00a0passive-interface\u00a0\u00bb  <span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>Cette option permet de d\u00e9clarer une interface passive, c&rsquo;est \u00e0 dire une interface qui n&rsquo;est pas reli\u00e9e \u00e0 un autre routeur. En la d\u00e9clarant, les messages de MAJ de table de routage ne seront pas \u00e9mis sur cette interface. Ceci dans le but de limiter le traffic r\u00e9seau et de le s\u00e9curiser.<\/p>\n\n\n\n<p>Dans notre cas il est interresant de ne pas diffuser les tables de routage sur les vlan 10, 20 et 30.<\/p>\n\n\n\n<p>Pour le VLAN 10, nous allons sur le routeur 1.  La liste des interfaces pouvant \u00eatre d\u00e9clar\u00e9es :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1(config-router)#passive-interface ?\n  Async              Async interface\n  BVI                Bridge-Group Virtual Interface\n  CTunnel            CTunnel interface\n  Dialer             Dialer interface\n  FastEthernet       FastEthernet IEEE 802.3\n  Group-Async        Async Group interface\n  Lex                Lex interface\n  Loopback           Loopback interface\n  MFR                Multilink Frame Relay bundle interface\n  Multilink          Multilink-group interface\n  Null               Null interface\n  Port-channel       Ethernet Channel of interfaces\n  Tunnel             Tunnel interface\n  Vif                PGM Multicast Host interface\n  Virtual-PPP        Virtual PPP interface\n  Virtual-Template   Virtual Template interface\n  Virtual-TokenRing  Virtual TokenRing\n  Vlan               Catalyst Vlans\n  default            Suppress routing updates on all interfaces\n<\/code><\/pre>\n\n\n\n<p>Dans notre exemple nous allons d\u00e9clarer le vlan 10 (qui prendra toutes les interfaces fastEthernet 1\/2 \u00e0 1\/15)<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1(config)#router rip\nR1(config-router)#passive-interface vlan 10\nR1(config-router)#exit<\/code><\/pre>\n\n\n\n<p>A faire sur les routeurs R2 et R3 avec le bon vlan.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III42_Option_%C2%AB_auto-summary_%C2%BB\"><\/span>III.4.2 Option \u00ab\u00a0auto-summary\u00a0\u00bb<span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>Par d\u00e9faut, le protocole rip ne va pas afficher les adresses de sous-r\u00e9seaux. Il va faire une synth\u00e8se en n&rsquo;affichant que les adresses de classes.<\/p>\n\n\n\n<p>Pour pouvoir les voir il faudra ajouter cette option :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1(config)#router rip\nR1(config-router)#no auto-summary \nR1(config-router)#exit<\/code><\/pre>\n\n\n\n<p>Dans notre cas, il ne sera pas observ\u00e9 de changement car il n&rsquo;a pas \u00e9t\u00e9 utilis\u00e9 de classes de sous r\u00e9seau.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"III5_Cas_dune_defaillance_dun_lien\"><\/span>III.5 Cas d&rsquo;une d\u00e9faillance d&rsquo;un lien<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Nous allons simuler la coupure du lien entre le routeur R1 et R3.<\/p>\n\n\n\n<p>Mais avant, regardons la route lorsque le PC1 pingue le PC3 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PC1> ping 192.168.30.1\n\n84 bytes from 192.168.30.1 icmp_seq=1 ttl=62 time=49.529 ms\n84 bytes from 192.168.30.1 icmp_seq=2 ttl=62 time=22.360 ms\n84 bytes from 192.168.30.1 icmp_seq=3 ttl=62 time=21.765 ms\n^C\nPC1> trace 192.168.30.1\ntrace to 192.168.30.1, 8 hops max, press Ctrl+C to stop\n 1   192.168.10.254   10.107 ms  9.265 ms  9.399 ms\n 2   192.168.101.2   19.780 ms  19.364 ms  19.922 ms\n 3   *192.168.30.1   29.440 ms (ICMP type:3, code:3, Destination port unreachable)<\/code><\/pre>\n\n\n\n<p>et sur le routeur R1 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show ip route rip\nR    192.168.30.0\/24 &#91;120\/1] via 192.168.101.2, 00:00:01, FastEthernet1\/1\nR    192.168.20.0\/24 &#91;120\/1] via 192.168.100.2, 00:00:10, FastEthernet1\/0\nR    192.168.102.0\/24 &#91;120\/1] via 192.168.101.2, 00:00:01, FastEthernet1\/1\n                      &#91;120\/1] via 192.168.100.2, 00:00:10, FastEthernet1\/0<\/code><\/pre>\n\n\n\n<p>Ce qui est conforme.<\/p>\n\n\n\n<p>Maintenant, d\u00e9sactivation du lien :<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"542\" src=\"http:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_lien_desactive-1024x542.png\" alt=\"\" class=\"wp-image-1736\" srcset=\"https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_lien_desactive-1024x542.png 1024w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_lien_desactive-300x159.png 300w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_lien_desactive-768x407.png 768w, https:\/\/blogperso.union31.fr\/wp-content\/uploads\/2020\/11\/GNS3_Routage_RIP1_lien_desactive.png 1278w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>L&rsquo;effet im\u00e9diat est l&rsquo;arr\u00eat de communication entre les 2 PC :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PC1> trace 192.168.30.1\ntrace to 192.168.30.1, 8 hops max, press Ctrl+C to stop\n 1   192.168.10.254   9.081 ms  9.605 ms  10.045 ms\n 2     *  *  *\n 3     *  *  *\n^C 4     *\n\nPC1> ping 192.168.30.1 \n\n192.168.30.1 icmp_seq=1 timeout\n<\/code><\/pre>\n\n\n\n<p>Attendons entre 180 et 240s puis recommencons :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>PC1> ping 192.168.30.1 -t\n\n84 bytes from 192.168.30.1 icmp_seq=1 ttl=61 time=46.816 ms\n84 bytes from 192.168.30.1 icmp_seq=2 ttl=61 time=41.629 ms\n^C\nPC1> trace 192.168.30.1  \ntrace to 192.168.30.1, 8 hops max, press Ctrl+C to stop\n 1   192.168.10.254   1.837 ms  9.734 ms  9.939 ms\n 2   192.168.100.2   19.139 ms  30.388 ms  20.272 ms\n 3   192.168.102.2   39.458 ms  39.849 ms  39.683 ms\n 4   *192.168.30.1   50.519 ms (ICMP type:3, code:3, Destination port unreachable)\n<\/code><\/pre>\n\n\n\n<p>Le ping n&rsquo;est plus rout\u00e9 plus par l&rsquo;@ip 192.168.101.2 du router R3 mais par l&rsquo;@IP 192.168.100.2 du router R2.<\/p>\n\n\n\n<p>Sur le routeur R1, la table de routage a chang\u00e9 :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#show ip route rip\nR    192.168.30.0\/24 &#91;120\/2] via 192.168.100.2, 00:00:10, FastEthernet1\/0\nR    192.168.20.0\/24 &#91;120\/1] via 192.168.100.2, 00:00:10, FastEthernet1\/0\nR    192.168.102.0\/24 &#91;120\/1] via 192.168.100.2, 00:00:10, FastEthernet1\/0<\/code><\/pre>\n\n\n\n<p>Il en est de m\u00eame pour les tables de routages de R2 et R3.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"IV_Aller_plus_loin\"><\/span>IV Aller plus loin<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"IV1_Securisation_des_echanges_RIP_entre_routeurs\"><\/span>IV.1 S\u00e9curisation des \u00e9changes RIP entre routeurs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Par d\u00e9faut le protocole RIP v2 \u00e9change des informations entre routeur non chiffr\u00e9es. Pour plus de s\u00e9curit\u00e9, ces \u00e9changes doivent l&rsquo;\u00eatre.<\/p>\n\n\n\n<p>Pour cle cr\u00e9ation d&rsquo;une clef dans le routeur R1<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#conf t\nR1(config)#key chain clef_RIP\nR1(config-keychain)#key 1\nR1(config-keychain-key)#key-string lecontenudemaclef\nR1(config-keychain-key)#exit\nR1(config-keychain)#exit\n<\/code><\/pre>\n\n\n\n<p>Et maintenant on va dire de chiffrer les communication RIP avec cette clef sur chaque interface sur laquelle le protocole va discuter.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#conf t\nR1(config)#interface range fastEthernet 1\/0 -1\nR1(config-if-range)#ip rip authentication key-chain clef_RIP\nR1(config-if-range)#ip rip authentication mode md5 \nR1(config-if-range)#exit\nR1(config)#exit<\/code><\/pre>\n\n\n\n<p>A ce stade, le routeur n&rsquo;accepte plus les informations des autres routeurs (via debug ip rip) :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#\n*Mar  1 00:21:58.695: RIP: sending v2 update to 224.0.0.9 via FastEthernet1\/1 (192.168.101.1)\n*Mar  1 00:21:58.695: RIP: build update entries\n*Mar  1 00:21:58.695: \t192.168.10.0\/24 via 0.0.0.0, metric 1, tag 0\n*Mar  1 00:21:58.695: \t192.168.100.0\/24 via 0.0.0.0, metric 1, tag 0\nR1#\n*Mar  1 00:22:12.399: RIP: ignored v2 packet from 192.168.100.2 (invalid authentication)\nR1#<\/code><\/pre>\n\n\n\n<p>Il faut effectuer le m\u00eame type de configuration sur les autres routeurs et utiliser la m\u00eame clef<\/p>\n\n\n\n<p>Une fois fait, on s&rsquo;apercoit que les \u00e9changes se font de mani\u00e8re chiffr\u00e9e :<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>R1#\n*Mar  1 00:32:26.339: RIP: received packet with MD5 authentication\n*Mar  1 00:32:26.339: RIP: received v2 update from 192.168.101.2 on FastEthernet1\/1\n*Mar  1 00:32:26.339:      192.168.20.0\/24 via 0.0.0.0 in 2 hops\n*Mar  1 00:32:26.339:      192.168.100.0\/24 via 0.0.0.0 in 2 hops\nR1#\n*Mar  1 00:32:32.927: RIP: received packet with MD5 authentication\n*Mar  1 00:32:32.927: RIP: received v2 update from 192.168.100.2 on FastEthernet1\/0\n*Mar  1 00:32:32.927:      192.168.20.0\/24 via 0.0.0.0 in 1 hops\n*Mar  1 00:32:32.931:      192.168.30.0\/24 via 0.0.0.0 in 2 hops\n*Mar  1 00:32:32.931:      192.168.102.0\/24 via 0.0.0.0 in 1 hops\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"IV2_Pour_aller_plus_loin_et_comprendre_dautres_options_du_RIP\"><\/span>IV.2 Pour aller plus loin et comprendre d&rsquo;autres options du RIP<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<figure class=\"wp-block-embed-wordpress wp-block-embed is-type-wp-embed is-provider-www-expertcisco-fr\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\" data-secret=\"PpLNaktbY1\"><a href=\"https:\/\/www.expertcisco.fr\/rip-v2\/rip-v2-advanced-lab\">RIP v2 Advanced Lab<\/a><\/blockquote><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; clip: rect(1px, 1px, 1px, 1px);\" title=\"\u00ab\u00a0RIP v2 Advanced Lab\u00a0\u00bb &#8212; www.expertcisco.fr\" src=\"https:\/\/www.expertcisco.fr\/rip-v2\/rip-v2-advanced-lab\/embed#?secret=PpLNaktbY1\" data-secret=\"PpLNaktbY1\" width=\"600\" height=\"338\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe>\n<\/div><\/figure>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I Introduction Comment impl\u00e9menter un routage dynamique entre 3 routeurs avec le protocole RIP v2. Sch\u00e9ma de travail : Nous aurons 3 routeurs interconnect\u00e9s entre eux. Chaque routeur dessert un VLAN propre. L&rsquo;objectif est d&rsquo;impl\u00e9menter le protocole RIPv2 pour que<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1682","post","type-post","status-publish","format-standard","hentry","category-_systeme"],"_links":{"self":[{"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/posts\/1682","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1682"}],"version-history":[{"count":59,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/posts\/1682\/revisions"}],"predecessor-version":[{"id":1780,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=\/wp\/v2\/posts\/1682\/revisions\/1780"}],"wp:attachment":[{"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1682"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1682"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogperso.union31.fr\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1682"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}