On Thu, Apr 04, 2019 at 05:29:40PM +0200, Remi Locherer wrote:
> On Tue, Apr 02, 2019 at 07:27:07PM +1000, Mitchell Krome wrote:
> > On 2/04/2019 3:30 pm, Remi Locherer wrote:
> > > Hi Mitchell
> > >
> > > On Sat, Mar 30, 2019 at 04:10:09PM +1000, Mitchell Krome wrote:
> > >> I kept finding I had
On Tue, Apr 02, 2019 at 07:27:07PM +1000, Mitchell Krome wrote:
> On 2/04/2019 3:30 pm, Remi Locherer wrote:
> > Hi Mitchell
> >
> > On Sat, Mar 30, 2019 at 04:10:09PM +1000, Mitchell Krome wrote:
> >> I kept finding I had a lingering /30 route when I turned off one of my
> >> test boxes. I
On 2/04/2019 3:30 pm, Remi Locherer wrote:
> Hi Mitchell
>
> On Sat, Mar 30, 2019 at 04:10:09PM +1000, Mitchell Krome wrote:
>> I kept finding I had a lingering /30 route when I turned off one of my
>> test boxes. I tracked it down to ospfd sending RTM_ADD for a stub
>> network with the
Hi Mitchell
On Sat, Mar 30, 2019 at 04:10:09PM +1000, Mitchell Krome wrote:
> I kept finding I had a lingering /30 route when I turned off one of my
> test boxes. I tracked it down to ospfd sending RTM_ADD for a stub
> network with the non-masked prefix. The RTM_ADD path applies the mask
> inside
I kept finding I had a lingering /30 route when I turned off one of my
test boxes. I tracked it down to ospfd sending RTM_ADD for a stub
network with the non-masked prefix. The RTM_ADD path applies the mask
inside the kernel, so the route got added as expected, but the
RTM_DELETE enforces an exact