[quagga-dev 16646] Re: PBR(policy based routing in quagga)
Anki Abhi <[email protected]> Tue, 22 Aug 2017 08:38:55 +0530
| Newsgroups | gmane.network.quagga.devel,gmane.network.quagga.user |
|---|---|
| Message-ID | <CAOTXYWVdoYbWmDdC-Miwm+36z+Kcc7q6ER+you-mDfum4ss-Pg@mail.gmail.com> |
Thanks a lot. Will reduce the ad and try. Thanks, Anki On Monday, August 21, 2017, Guillaume Barrot <[email protected]> wrote: > Try to lower the administrative distance for the static route. > PBR shall use a lower AD, so the static route is still present. > > 2017-08-21 13:07 GMT+02:00 Anki Abhi <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>>: > >> Hi all, >> >> >> Could you please let me know PBR (Policy Based Routing) functionality >> support is present in Quagga for both Static routes and Dynamic routing >> cases or not. >> >> >> >> I am able to see the configuration option to configure the route-map >> config, but the next hop was not modified. >> >> >> >> Below is my config for static case, Please correct me if I missed any >> config. >> >> >> >> Before applying the PBR config, route table info >> >> >> >> K>* 0.0.0.0/0 via 10.200.8.1,vmmgmt >> >> K>* 1.0.0.0/24 via 2.0.0.1, enp2s0f3 >> >> C>* 2.0.0.0/24 is directly connected, enp2s0f3 >> >> C>* 3.0.0.0/24 is directly connected, enp2s0f1 >> >> C>* 10.200.8.0/24 is directly connected, vmmgmt >> >> S>* 25.25.0.0/24 [1/0] via 2.0.0.20, enp2s0f3 >> >> S>* 30.0.0.0/24 [1/0] via 3.0.0.40, enp2s0f1 >> >> >> >> Tried configuring PBR below two ways >> >> 1. Using access list >> >> access-list anki permit 25.25.0.0/24 >> >> ! >> >> route-map qwe permit 5 >> >> match ip address anki >> >> set ip next-hop 3.0.0.40 >> >> 1. Directly applying matching ip >> >> route-map aaa permit 2 >> >> match ip address 25.25.0.0/24 >> >> set ip next-hop 3.0.0.40 >> >> >> >> Note: I am not seeing any configuration support to apply the PBR config >> under interface. >> >> >> >> After applying the above config , show ip route in Quagga displays the >> same output, next hop was not modified. >> >> >> >> K>* 1.0.0.0/24 via 2.0.0.1, enp2s0f3 >> >> C>* 2.0.0.0/24 is directly connected, enp2s0f3 >> >> C>* 3.0.0.0/24 is directly connected, enp2s0f1 >> >> C>* 10.200.8.0/24 is directly connected, vmmgmt >> >> S>* 25.25.0.0/24 [1/0] via 2.0.0.20, enp2s0f3 >> >> S>* 30.0.0.0/24 [1/0] via 3.0.0.40, enp2s0f1 >> >> C>* 127.0.0.0/8 is directly connected, lo >> >> C>* 192.168.122.0/24 is directly connected, virbr0 >> >> >> >> Thanks a lot for your help in advance. >> >> >> >> >> >> Thanks, >> >> Anki >> >> _______________________________________________ >> Quagga-users mailing list >> [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> >> https://lists.quagga.net/mailman/listinfo/quagga-users >> >> > > > -- > Cordialement, > > Guillaume BARROT >