Re: RA learned prefix added to routing table is not deleted on ra route flush

--000000000000714d1b05e27384d3
Content-Type: text/plain; charset="UTF-8"

Thanks, Marc for the response.  However, the route was created because of
the prefix that was received in the RA. Hence it should be marked as "ra"
too. I feel that makes more sense. We will be able to correctly identify
all the routes that were added due to a received RA.

Dheeraj

On Sat, Jun 25, 2022 at 1:32 AM Marc Haber <[email protected]>
wrote:

> On Fri, Jun 24, 2022 at 11:11:05AM -0400, Dheeraj Kandula wrote:
> >       When I enabled Router Advertisement on the interface on which I
> want
> > to receive RA, the received prefix was added to the routing table. The
> > default route was added with the tag "ra" but not the prefix.
>
> I can only guess, but my guess is that it doesn't marked that way
> because it strictly speaking didnt come from an RA but was generated
> because an IP address was configured on the Interface. That is most
> probably the same mechanism that is used when an IP address is manually
> configured on the interface.
>
> > When I flush the ra learned routes using the following command, only the
> > default route gets removed. Why doesn't the prefix which is *bolded*
> above
> > get deleted too?
>
> Because the route was not learned via RA. I find that correct behavior.
>
> Greetings
> Marc
>
> --
>
> -----------------------------------------------------------------------------
> Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
>
>

--000000000000714d1b05e27384d3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks, Marc for the response.=C2=A0 However, the rou=
te was created because of the prefix that was received in the RA. Hence it =
should be marked as &quot;ra&quot; too. I feel that makes more sense. We wi=
ll be able to correctly identify all the routes that were added due to a re=
ceived RA.<br></div><div><br></div><div>Dheeraj<br></div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 25, 20=
22 at 1:32 AM Marc Haber &lt;<a href=3D"mailto:mh%[email protected]=
e">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">On Fri, Jun 24, 2022 at 11:11:05AM -0400, Dhe=
eraj Kandula wrote:<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0When I enabled Router Advertisement on the i=
nterface on which I want<br>
&gt; to receive RA, the received prefix was added to the routing table. The=
<br>
&gt; default route was added with the tag &quot;ra&quot; but not the prefix=
.<br>
<br>
I can only guess, but my guess is that it doesn&#39;t marked that way<br>
because it strictly speaking didnt come from an RA but was generated<br>
because an IP address was configured on the Interface. That is most<br>
probably the same mechanism that is used when an IP address is manually<br>
configured on the interface.<br>
<br>
&gt; When I flush the ra learned routes using the following command, only t=
he<br>
&gt; default route gets removed. Why doesn&#39;t the prefix which is *bolde=
d* above<br>
&gt; get deleted too?<br>
<br>
Because the route was not learned via RA. I find that correct behavior.<br>
<br>
Greetings<br>
Marc<br>
<br>
-- <br>
---------------------------------------------------------------------------=
--<br>
Marc Haber=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| &quot;I don&#39;t trust Compu=
ters. They | Mailadresse im Header<br>
Leimen, Germany=C2=A0 =C2=A0 |=C2=A0 lose things.&quot;=C2=A0 =C2=A0 Winona=
 Ryder | Fon: *49 6224 1600402<br>
Nordisch by Nature |=C2=A0 How to make an American Quilt | Fax: *49 6224 16=
00421<br>
<br>
</blockquote></div>

--000000000000714d1b05e27384d3--