Hi Venumadhav, By those commands: set interface ip table vpp-intf19/0/1 100 set interface ip address vpp-intf19/0/1 10.53.1.189/23
you set interface vpp-intf19/0/1 into the ip table 100, and that's why 10.53.0.1 (which is inside net 10.53.0.0/23) is also reachable from ip table 100. That means you need to specify an ip table for the nexthop as well. In you case it'd be: ip route add 10.43.0.170/32 table 100 via 10.53.0.1 next-hop-table 100 But make sure you've deleted the previous "wrong" route. On Thu, 8 Apr 2021 at 10:54, Venumadhav Josyula <vjosy...@gmail.com> wrote: > Hi Stanislav, > > > By default it'd be nexthop in default fib. > i) by default meaning table id 0 ? > i) So we want it to be default fib, what should be in the default fib ? > meaning default route ? > ii) But we want to only for dest ip ( 10.43.0.170/32) > > What needs to be done? > > Thanks, > Regards, > Venu > > > On Thu, 8 Apr 2021 at 13:18, Stanislav Zaikin <zsta...@gmail.com> wrote: > >> Hi Venumadhav, >> >> You should specify an ip table for the nexthop with "next-hop-table XX". >> By default it'd be nexthop in default fib. >> >> On Thu, 8 Apr 2021 at 10:40, Venumadhav Josyula <vjosy...@gmail.com> >> wrote: >> >>> Hi All, >>> For VRF configuration does not seem to work for us, we using vpp-20.09. >>> vpp# show version >>> vpp v20.09.0-1~0-g94f29f6 built by root on >>> devdocker2.parallelwireless.net at 2021-04-05T21:52:02 >>> vpp# >>> >>> We are trying to following configuration >>> >>> ip table add 100 >>> set interface ip table vpp-intf19/0/1 100 >>> set interface ip address vpp-intf19/0/1 10.53.1.189/23 >>> ip route add 10.43.0.170/32 table 100 via 10.53.0.1 >>> >>> here is dump >>> vpp# show ip fib table 100 >>> ipv4-VRF:100, fib_index:1, flow hash:[src dst sport dport proto ] >>> epoch:0 flags:none locks:[CLI:2, ] >>> 0.0.0.0/0 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:16 buckets:1 uRPF:17 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 0.0.0.0/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:17 buckets:1 uRPF:20 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 10.43.0.170/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:27 buckets:1 uRPF:29 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 10.53.0.0/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:19 buckets:1 uRPF:14 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 10.53.0.0/23 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:12 to:[0:0]] >>> [0] [@4]: ipv4-glean: vpp-intf19/0/1: mtu:9000 next:2 >>> ffffffffffff3cecef1f59df0806 >>> 10.53.1.189/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:25 buckets:1 uRPF:30 to:[0:0]] >>> [0] [@2]: dpo-receive: 10.53.1.189 on vpp-intf19/0/1 >>> 10.53.1.255/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:18 buckets:1 uRPF:28 >>> to:[3:234]] >>> [0] [@0]: dpo-drop ip4 >>> 224.0.0.0/4 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:14 buckets:1 uRPF:18 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 240.0.0.0/4 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:15 buckets:1 uRPF:19 to:[0:0]] >>> [0] [@0]: dpo-drop ip4 >>> 255.255.255.255/32 >>> unicast-ip4-chain >>> [@0]: dpo-load-balance: [proto:ip4 index:13 buckets:1 uRPF:16 >>> to:[214:19084]] >>> [0] [@0]: dpo-drop ip4 >>> vpp# >>> >>> Can anyone pinpoint what could be the problem ? >>> >>> Thanks, >>> Regards, >>> Venu >>> >>> >>> >>> >> >> -- >> Best regards >> Stanislav Zaikin >> > -- Best regards Stanislav Zaikin
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19143): https://lists.fd.io/g/vpp-dev/message/19143 Mute This Topic: https://lists.fd.io/mt/81936718/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
