> Can we mix, ABF and VRF ? I'd think so, something like this should work: abf policy add id <ID> acl <INDEX> via ip4-lookup-in-table <VRF>
ben > On Mon, 19 Apr 2021 at 17:31, Benoit Ganne (bganne) <bga...@cisco.com > <mailto:bga...@cisco.com> > wrote: > > > Hi Venu, > > You can do that with ABF, see https://wiki.fd.io/view/VPP/ABF > > Best > ben > > > -----Original Message----- > > From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <vpp- > d...@lists.fd.io <mailto:vpp-dev@lists.fd.io> > On Behalf Of Venumadhav > > Josyula > > Sent: lundi 19 avril 2021 13:17 > > To: vpp-dev <vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> > > > Subject: [vpp-dev] route based on the source ip > > > > Hi, > > > > We have a requirement such that > > i) we want to have a vrf table for each vlan interface. Each vrf > will have > > it own default route > > ii)for packets from the host interface , we want to have a route > based on > > the source ip such we can redirect to use vrf table as next hop > table. > > iii) We are using strongswan for ipsec, and we don't want to > enable the > > install_route option of strongswan, so that we can packet remote > host to > > be sent to default route in the vrf table. Please our problem is > not > > specific to ipsec processing by routes > > > > > > The problem statement is how do we route the host interface > packets to > > appropriate vrf table corresponding to the vlan interface. We > donot know > > the remote ip for which we want install route. > > > > So is it possible to have a route based on source ip ? > > > > > > Thanks, > > Regards, > > Venu > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19252): https://lists.fd.io/g/vpp-dev/message/19252 Mute This Topic: https://lists.fd.io/mt/82206233/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
