hi all
i've found a possibile bug in quagga's ripv2 implementation. When there
is a route in the routing table, and the router receive a response for
the same route, with same netmask and metric but with different nexthop
it is silently ignored. conforming to the standards, if the router is
the same that announced this route the first time, nexthop field must be
updated.
Patch attached.
--
mydecay
S.P.I.N.E. Group - http://www.spine-group.org
Key Fingerprint: 667A 4E73 EA53 66AC E2AB D0CA 2908 1484 1F26 4C40
GnuPG Key: http://www.spine-group.org/keys/mydecay.asc
--
mydecay
S.P.I.N.E. Group - http://www.spine-group.org
Key Fingerprint: 667A 4E73 EA53 66AC E2AB D0CA 2908 1484 1F26 4C40
GnuPG Key: http://www.spine-group.org/keys/mydecay.asc
i've found a possibile bug in quagga's ripv2 implementation. When there
is a route in the routing table, and the router receive a response for
the same route, with same netmask and metric but with different nexthop
it is silently ignored. conforming to the standards, if the router is
the same that announced this route the first time, nexthop field must be
updated.
Patch attached.
--
mydecay
S.P.I.N.E. Group - http://www.spine-group.org
Key Fingerprint: 667A 4E73 EA53 66AC E2AB D0CA 2908 1484 1F26 4C40
GnuPG Key: http://www.spine-group.org/keys/mydecay.asc
--
mydecay
S.P.I.N.E. Group - http://www.spine-group.org
Key Fingerprint: 667A 4E73 EA53 66AC E2AB D0CA 2908 1484 1F26 4C40
GnuPG Key: http://www.spine-group.org/keys/mydecay.asc