[dev] Reg: FRR PBR Configuration

Donald Sharp sharpd at cumulusnetworks.com
Tue Dec 4 07:05:41 EST 2018


Valli -

It looks like it is installed correctly to me.  Do the rules created look
good to you?

donald

On Tue, Dec 4, 2018 at 3:11 AM valli rama <pvallirama at gmail.com> wrote:

> Hi Donald
>
> Please find the below is the ip rule show output
>
> sudo ip rule show
> 0: from all lookup local
> 300: from 192.168.59.10/24 to 192.168.56.10/24 iif enp0s3 lookup 10000
> 301: from 192.168.55.10/24 to 192.168.54.11/24 iif enp0s3 lookup 10000
> 32766: from all lookup main
> 32767: from all lookup default
>
> sudo ip route ls table 10000
> default via 192.168.58.11 dev enp0s9  proto 195  metric 20
>
>
> Thanks,
> Valli
>
>
> On Mon, 3 Dec 2018 at 19:32, Donald Sharp <sharpd at cumulusnetworks.com>
> wrote:
>
>> Can we get the output of `ip rule show` from the linux cli?
>>
>> On Mon, Dec 3, 2018 at 8:36 AM valli rama <pvallirama at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> We have the below setup with RIP and PBR configurations
>>>
>>>
>>> [image: image.png]
>>>
>>> We have RIP default learned for 192.168.57.0 and we are trying to
>>> install the PBR Policeis with the Next-hop 192.168.58.0 (other than the
>>> default one)
>>>
>>> Step -1 First we are trying to install the PBR Policy “One” with
>>> Sequance Number “1” and binded it to an interface on both the FRRouters A
>>> and B
>>>
>>> [image: image.png]
>>>
>>> Step -2 And we observed that the Traffic is redirected to the Nexhop
>>> given in the policy. Which is working Fine.
>>>
>>> Step -3 Now we are trying to update and re-install the PBR Policy “One”
>>> with Sequance Number “2” and bound it to the same interface on both the
>>> FRRouters A and B
>>>
>>>
>>> [image: image.png]
>>> [image: image.png]
>>>
>>> Step-4 We observed that the Traffic is NOT redirected to the Nexhop for
>>> Policy with Sequance Number “2”.
>>>
>>> As per my understanding both the Policies Seq “1” and “2” are belongs to
>>> same Policy-Map and Binded to the Interface and Both should work as per the
>>> Policy Rules... But Rule with Sequance Number “1” is working as per the
>>> Policy Rule But Rule with Sequance Number “2” is not working.
>>>
>>> Could you please guide me whether I’m missing any configuration steps
>>> that should be considered for getting the above stuff working.
>>>
>>> And could you please let me know how to check the corresponding insalled
>>> iptable entry in the linux kernel for the configured FRR PBR policy.
>>>
>>>
>>> Thanks and Regards,
>>>
>>> Valli
>>> _______________________________________________
>>> dev mailing list
>>> dev at lists.frrouting.org
>>> https://lists.frrouting.org/listinfo/dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20181204/f5ac97f8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 6600 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20181204/f5ac97f8/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 1185 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20181204/f5ac97f8/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 27999 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20181204/f5ac97f8/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 36260 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20181204/f5ac97f8/attachment-0007.png>


More information about the dev mailing list