Mario Another update to one of your questions
the Key number 1 on the cisco side is purely local as explained in cisco documentations: http://www.cisco.com/en/US/docs/ios/11_3/np1/configuration/guide/1cindep.html#wp5061 "Each key has its own key identifier (specified with the *key* /number/ command), which is stored locally. " There is no statement like this one on the Juniper side as the configuration is organized another way regards Alain Antoniou, Mario a écrit : >Hi all, > >I would like to implement RIPv2 MD5 authentication between an M320 >running Junos 8.4 and a Cisco 877 running 12.4T IOS in a PE-CE scenario. >However, I am seeing RIP authentication failure on the M320 end, whereas >the 877 authenticates the RIP update just fine. I am using 'key 1' on >the IOS end. > >As I understand, RFC2082 defines the key identifier, which IOS does >implement with the "key <number>" statement in the key chain definition. >I can not see where I can specify the key identifier within Junos... >Does anyone know what key Junos uses with using MD5 RIP authentication? >Also, whether anybody has successfully implemented RIP MD5 >authentication between Junos and IOS, and with what settings. I would >like to confirm whether there is interoperability between Junos and IOS >regarding MD5 RIP authentication. > >Thanks for your help. > >Regards, > >Mario. > > >Email disclaimer: > >The information contained in or attached to this communication may contain >confidential or privileged information and is intended for the addressee only. >If you are not the intended recipient of this email communication, you are >notified that any use, dissemination, distribution or copying of this message >or data is prohibited. If you have received this email in error, please notify >the sender by return email and permanently delete the document. > >The views expressed in this message are those of the individual sender, except >where the sender specifically states them to be the views of VicTrack. > >VicTrack does not guarantee that the integrity of this communication has been >maintained nor that this communication is free of viruses, interceptions or >interference. > >Please consider the environment before printing this Email. >_______________________________________________ >juniper-nsp mailing list juniper-nsp@puck.nether.net >https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
