No subject


Sun Dec 6 23:23:09 GMT 2009


it advertises it to device2, device2 will store in the routing table
as 29.0.0.0/8 and
forwards to device1.

Device(1/2) Behavior:

   1) Change the rip version in cisco1 to 2 globally
   2) Change the rip version to 2 on corresponding interface to #1 in device2.

Now our device2 receives the classless route and stores it as
29.0.0.0/24, but will
not forward to the device1.It is not auto-summarizing and advertising
the route as
in the cisco's case.


But when a route for eg: 169.254.140.0/24 is received using RIPv2 this route is
forwarded across to the device1 even though its a  classless route and
it stored in
the device1 (received using RIPv1) as it is.

As per RFC, it should advertise the summarized route.

Device1 and Device 2 are using Quagga RIP.What is the expected
behavior when using RIPv1???

I am a newbie, so please bear with me for any mistakes.Thanks for the help.

--001636e0b9292c446b0481d38987
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<pre id=3D"comment_text_0">Below is the setup.<br>                         =
      PC 3 <br>                                | <br>                      =
          |<br>PC1 -------- Device1 ------  Device2------------CISCO1------=
---------CISCO2---------PC2<br>
                                                     FA0/0  FA0/1         F=
A0/0   FA0/1 <br><br>PC1&lt;---&gt;device1 169.254.129/24 (.135-.132)<br>de=
vice1&lt;--&gt;device2 169.254.130/24 (.133-.132)<br>device2&lt;--&gt;PC3 1=
69.254.148/24 (.132-.135)<br>
<br>devcie2&lt;--&gt;Cisco1 169.254.139/24(.132-.150)<br>Cisco1&lt;--&gt;Ci=
sco2 168.254.140/24 (.132-.150)<br>Cisco2&lt;--&gt; PC2 192.168.50/24 (.1-.=
50)<br><br><br>RIPv2 is configured in Cisco 2 globally and in Cisco 1 in in=
terface FA0/1.<br>
RIPv1 is configured else where.<br><br>Cisco Behavior:<br><br>From Cisco 2 =
we are redistributing a classless route (<a href=3D"http://29.0.0.0/24">29.=
0.0.0/24</a>) in cisco 1,<br>it advertises it to device2, device2 will stor=
e in the routing table as <a href=3D"http://29.0.0.0/8">29.0.0.0/8</a> and<=
br>
forwards to device1. <br><br>Device(1/2) Behavior:<br><br>   1) Change the =
rip version in cisco1 to 2 globally  <br>   2) Change the rip version to 2 =
on corresponding interface to #1 in device2.<br><br>Now our device2 receive=
s the classless route and stores it as <a href=3D"http://29.0.0.0/24">29.0.=
0.0/24</a>, but will<br>
not forward to the device1.It is not auto-summarizing and advertising the r=
oute as<br>in the cisco&#39;s case.<br><br><br>But when a route for eg: <a =
href=3D"http://169.254.140.0/24">169.254.140.0/24</a> is received using RIP=
v2 this route is<br>
forwarded across to the device1 even though its a  classless route and it s=
tored in<br>the device1 (received using RIPv1) as it is. <br><br>As per RFC=
, it should advertise the summarized route.<br><br>Device1 and Device 2 are=
 using Quagga RIP.What is the expected behavior when using RIPv1???<br>
<br>I am a newbie, so please bear with me for any mistakes.Thanks for the h=
elp. <br></pre><input id=3D"gwProxy" type=3D"hidden"><input onclick=3D"jsCa=
ll();" id=3D"jsProxy" type=3D"hidden"><input id=3D"gwProxy" type=3D"hidden"=
><input onclick=3D"jsCall();" id=3D"jsProxy" type=3D"hidden"><div id=3D"ref=
HTML">
</div>

--001636e0b9292c446b0481d38987--


More information about the Quagga-users mailing list