Hoi Brian, I think that Linux CP does not consume the netlink message that assigns the interface to a new VRF (table)- doing it the other way around will likely work better.
It would be pretty slick if "sudo ip link set dev ge0 master vrf-blue" could pivot the VPP-side interface into the correct table in the dataplane, but that message is not consumed. A previous discussion (and a workaround, which is to put the interface in the table on the VPP side, and then copy that forward into the Linux side as you did above), may work for you. See here: https://lists.fd.io/g/vpp-dev/topic/89678481#20995 If there's a larger interest, I could give it a go, to consume the 'create vrf V' and 'set interface X in vrf V' netlink messages, although this stuff can get tricky :) groet, Pim On Wed, Jan 11, 2023 at 8:48 PM Brian Saunders <brian.t.saund...@gmail.com> wrote: > Hello All, > > I've been playing around with VPP and have a question about VRFs created > in linux and how they are supposed to appear within the VPP fib when one > has the Linux CP/NL plugins enabled. I saw the following post here > https://lists.fd.io/g/vpp-dev/topic/89678481#21001 which seemed a little > conflicting on the responses so I just wanted to get a bit of clarification > on the expected behavior. Here are the commands that I'm inputting: > > vppctl commands: > create interface vmxnet3 0000:0b:00.0 bind > lcp create vmxnet3-0/b/0/0 host-if ge0 > > linux commands: > sudo ip link set ge0 up > sudo ip link add vrf-blue type vrf table 10 > sudo ip link set dev vrf-blue up > sudo ip link set dev ge0 master vrf-blue > sudo ip addr add 192.168.1.1/24 dev ge0 > > From the linux side all is well. When I go into vppctl I see table 10 but > 192.168.1.1/24 is not in table 10. Below if the output from show ip > fib. Is this the expected behavior or should 192.168.1.1/24 be in the > table 10 fib? > > vpp# show ver > vpp v22.10.0-3~gb89dcf824 built by root on ubuntu20 at 2023-01-11T16:05:42 > vpp# show ip fib > ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel ] > epoch:0 flags:none locks:[default-route:1, ] > 0.0.0.0/0 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:1 buckets:1 uRPF:0 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 0.0.0.0/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:2 buckets:1 uRPF:1 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 192.168.1.0/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:15 buckets:1 uRPF:14 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 192.168.1.0/24 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:14 buckets:1 uRPF:13 to:[0:0]] > [0] [@4]: ipv4-glean: [src:192.168.1.0/24] vmxnet3-0/b/0/0: mtu:9000 > next:1 flags:[] ffffffffffff00505694bf900806 > 192.168.1.1/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:17 buckets:1 uRPF:18 to:[0:0]] > [0] [@13]: dpo-receive: 192.168.1.1 on vmxnet3-0/b/0/0 > 192.168.1.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:16 buckets:1 uRPF:16 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 224.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:4 buckets:1 uRPF:3 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 240.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:3 buckets:1 uRPF:2 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 255.255.255.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:5 buckets:1 uRPF:4 to:[0:0]] > [0] [@0]: dpo-drop ip4 > ipv4-VRF:10, fib_index:1, flow hash:[src dst sport dport proto flowlabel ] > epoch:0 flags:none locks:[lcp-rt:1, ] > 0.0.0.0/0 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:18 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:19 buckets:1 uRPF:19 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 224.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:21 buckets:1 uRPF:21 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 240.0.0.0/4 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:20 to:[0:0]] > [0] [@0]: dpo-drop ip4 > 255.255.255.255/32 > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:22 buckets:1 uRPF:23 to:[0:0]] > [0] [@13]: dpo-receive: 0.0.0.0 on local0 > vpp# > > Thanks, > > Brian > > > > -- Pim van Pelt <p...@ipng.nl> PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22450): https://lists.fd.io/g/vpp-dev/message/22450 Mute This Topic: https://lists.fd.io/mt/96207643/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
