[quagga-users 14026] Re: query w.r.t generic behaviour of quagga engine when PBR is in place

durga c.vijaya.durga at gmail.com
Thu Jun 25 11:08:32 BST 2015


Thank you very much.
I did disable reverse path filter, but the set up still doesnot seem to
work.
Will check the multipath solution as well.

Cheers!
Durga


On Thu, Jun 25, 2015 at 5:54 PM, Alexis Rosen <
quagga-users at alexis.users.panix.com> wrote:

> On Jun 25, 2015, at 2:56 AM, durga <c.vijaya.durga at gmail.com> wrote:
> > additional information:
> > I am running quagga engine on linux OS.
> >
> > On Thu, Jun 25, 2015 at 4:40 PM, durga <c.vijaya.durga at gmail.com> wrote:
> > I am just looking for a clarification on quagga engine behaviour in the
> below scenario.
> >                            _1_____________1_
> >                            |                            |_
> > 10.10.10.100--(R1)                           _(R2) -- 3(40.40.40.100)
> >                            |_2____________2_|
> >
> > the router R2 has learnt the route to destination network 10.10.10.100
> via interface 2, through OSPF
> >
> > Currently , the behaviour that I notice is that R2 drops all packets
> destined to 40.40.40.100 from 10.10.10.100 received on interface 1, but
> permits packets  from interface 2.  I was wondering if quagga engine is
> intrinsically filtering packets from 10.10.10.100 on interface 1.
>
> You're probably running into RPF. For more info look at the first couple
> of links in this: https://www.google.com/search?q=linux+ip+rpf
>
> The simple solution is to turn it off. Alternatively, you can look into
> multipath support, which is supposed to work now, but I haven't messed with
> it yet.
>
> /a
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20150625/fce4af39/attachment.html>


More information about the Quagga-users mailing list