[vpp-dev] VPP 20.01 Release Milestone RC2 is complete!
Hi All, I have created the v20.01-rc2 tag on stable/2001 and verified that 20.01-rc2 build artifacts are on packagecloud, and are installable. VPP 20.01 Release Milestone RC2 is complete! As a reminder, the VPP 20.01 Release is in one week on January 29 2020: https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_20.01 It is important that now we commit only bugs which address critical issues (as determined by the VPP committers), ideally limited to addressing bugs found by CSIT testing. Per the standard process, all bug fixes to stable branches should follow the best practices: All bug fixes must be double-committed to the release throttle as well as to the master branch Commit first to the release throttle, then "git cherry-pick" into master Manual merges may be required, depending on the degree of divergence between throttle and master All bug fixes need to have a Jira ticket Please put Jira IDs into the commit messages. Please use the same Jira ID for both the stable branch and master. --a (your friendly 20.01 release manager) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15233): https://lists.fd.io/g/vpp-dev/message/15233 Mute This Topic: https://lists.fd.io/mt/70043583/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] #vnet Any command to individually enable and disable IP forwarding per interface level
Thank you. Actually, I was looking for a command similar to the command in the Linux " *sysctl net.ipv4.ip_forward net.ipv4.ip_forward = 1* ". Even after executing the command *set interface feature ip4-lookup arc ip4-unicast disable* , packet is forwarded. Also, the command *set interface feature arp-reply arc arp disable* gives the error "unknown feature". Thanks -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15234): https://lists.fd.io/g/vpp-dev/message/15234 Mute This Topic: https://lists.fd.io/mt/69978408/21656 Mute #vnet: https://lists.fd.io/mk?hashtag=vnet&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] #vnet Any command to individually enable and disable IP forwarding per interface level
[Edited Message Follows] Thank you. Actually, I was looking for a command similar to the following command in the Linux " *sysctl net.ipv4.conf.eth0.forwarding=1" /*To enable ip forwarding*/ and* " **sysctl net.ipv4.conf.eth0.forwarding=0* "*. */*To disable ip forwarding*/ * Even after executing the command *set interface feature ip4-lookup arc ip4-unicast disable* , packet is forwarded. Also, the command *set interface feature arp-reply arc arp disable* gives the error "unknown feature". Thanks -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15234): https://lists.fd.io/g/vpp-dev/message/15234 Mute This Topic: https://lists.fd.io/mt/69978408/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] Coverity run FAILED as of 2020-01-23 14:00:23 UTC
Coverity run failed today. Current number of outstanding issues are 3 Newly detected: 0 Eliminated: 0 More details can be found at https://scan.coverity.com/projects/fd-io-vpp/view_defects -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15235): https://lists.fd.io/g/vpp-dev/message/15235 Mute This Topic: https://lists.fd.io/mt/70047900/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure
Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib drivers which are required for my NICs on Azure. I noticed that something was wrong when looking at the output of 'sudo vppctl show log'. I then went back and tried to get DPDK's testpmd application to work and from the output there it pointed to the missing drivers. I did manage to get testpmd to attach to my drivers. However, things are still not working correctly from the VPP side (maybe it's the way that VPP is initializing DPDK?). Getting back to your question, I'm not sure what you mean by the remote end of the FailsafeEthernet0 interface since this is a DPDK interface using the failsafe PMD (netvsc, in this case). The underlying hardware this device is related to are the eth1 and rename6 interfaces since they have the same MAC address and the PCI address of 0002:00:02.0: sudo lshw -class network -businfo Bus info Device Class Description pci@0001:00:02.0 rename5 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@ *0002:00:02.0* rename6 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0003:00:02.0 rename7 network MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] sudo ./dpdk-devbind.py --status Network devices using DPDK-compatible driver Network devices using kernel driver === 0001:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename5 drv=mlx4_core unused= *0002:00:02.0* 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename6 drv=mlx4_core unused= 0003:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename7 drv=mlx4_core unused= Now, if I try to bring up the interface on the link I get the following output in 'sudo vppctl show hardware': vpp# show hardware Name Idx Link Hardware FailsafeEthernet0 1 *up* FailsafeEthernet0 Link speed: 10 Gbps Ethernet address 00:0d:3a:f4:eb:8d FailsafeEthernet *carrier up* full duplex mtu 1504 flags: admin-up pmd maybe-multiseg rx-ip4-cksum rx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) tx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) max rx packet len: 1522 promiscuous: unicast off all-multicast off vlan offload: strip off filter off qinq off rx offload avail: ipv4-cksum udp-cksum tcp-cksum scatter rx offload active: ipv4-cksum scatter tx offload avail: ipv4-cksum udp-cksum tcp-cksum tcp-tso multi-segs tx offload active: multi-segs rss avail: ipv4-frag ipv4-tcp ipv4-udp ipv4-other ipv4 ipv6-tcp-ex ipv6-udp-ex ipv6-frag ipv6-tcp ipv6-udp ipv6-other ipv6-ex ipv6 rss active: none tx burst function: failsafe_tx_burst rx burst function: failsafe_rx_burst Errors: *rte_eth_dev_start[port:0, errno:-19]: Unknown error -19* So, it's showing as up with with an error on the call to rte_eth_dev_start. Now 'sudo vppctl show log' shows these log entries (and the attach device entries keep repeating): 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk EAL: VFIO support not initialized 2020/01/23 14:37:40:578 notice dpdk EAL: Couldn't map new region for DMA 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:42:510 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:42:510 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:33:24:210 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:33:24:210 notice dpdk EAL: Failed to attach d
Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure
cc-Damjan who is the DPDK expert. Not very conversant with failsafeEth. Looks like the driver isn’t able to connect to the device 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) Here is some info I looked up regarding initializing the DPDK for Failsafe https://dpdk.readthedocs.io/en/v17.08/nics/fail_safe.html#using-the-fail-safe-pmd-from-the-eal-command-line HTH. -- Regards, Balaji. From: on behalf of Chris King Date: Thursday, January 23, 2020 at 7:28 AM To: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib drivers which are required for my NICs on Azure. I noticed that something was wrong when looking at the output of 'sudo vppctl show log'. I then went back and tried to get DPDK's testpmd application to work and from the output there it pointed to the missing drivers. I did manage to get testpmd to attach to my drivers. However, things are still not working correctly from the VPP side (maybe it's the way that VPP is initializing DPDK?). Getting back to your question, I'm not sure what you mean by the remote end of the FailsafeEthernet0 interface since this is a DPDK interface using the failsafe PMD (netvsc, in this case). The underlying hardware this device is related to are the eth1 and rename6 interfaces since they have the same MAC address and the PCI address of 0002:00:02.0: sudo lshw -class network -businfo Bus info Device Class Description pci@0001:00:02.0 rename5 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0002:00:02.0 rename6 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0003:00:02.0 rename7 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] sudo ./dpdk-devbind.py --status Network devices using DPDK-compatible driver Network devices using kernel driver === 0001:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename5 drv=mlx4_core unused= 0002:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename6 drv=mlx4_core unused= 0003:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename7 drv=mlx4_core unused= Now, if I try to bring up the interface on the link I get the following output in 'sudo vppctl show hardware': vpp# show hardware NameIdx Link Hardware FailsafeEthernet0 1 up FailsafeEthernet0 Link speed: 10 Gbps Ethernet address 00:0d:3a:f4:eb:8d FailsafeEthernet carrier up full duplex mtu 1504 flags: admin-up pmd maybe-multiseg rx-ip4-cksum rx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) tx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) max rx packet len: 1522 promiscuous: unicast off all-multicast off vlan offload: strip off filter off qinq off rx offload avail: ipv4-cksum udp-cksum tcp-cksum scatter rx offload active: ipv4-cksum scatter tx offload avail: ipv4-cksum udp-cksum tcp-cksum tcp-tso multi-segs tx offload active: multi-segs rss avail: ipv4-frag ipv4-tcp ipv4-udp ipv4-other ipv4 ipv6-tcp-ex ipv6-udp-ex ipv6-frag ipv6-tcp ipv6-udp ipv6-other ipv6-ex ipv6 rss active:none tx burst function: failsafe_tx_burst rx burst function: failsafe_rx_burst Errors: rte_eth_dev_start[port:0, errno:-19]: Unknown error -19 So, it's showing as up with with an error on the call to rte_eth_dev_start. Now 'sudo vppctl show log' shows these log entries (and the attach device entries keep repeating): 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 14:37:40:578 notice dpdk
Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure
I’m far away from being dpdk-expert, I’m much closer to being expert in avoiding use of dpdk :) No idea what’s wrong here, never used this failsafe beast, maybe using native rdma driver can help -- Damjan On 23 Jan 2020, at 18:13, Balaji Venkatraman via Lists.Fd.Io wrote: cc-Damjan who is the DPDK expert. Not very conversant with failsafeEth. Looks like the driver isn’t able to connect to the device 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0003:00:02.0) Here is some info I looked up regarding initializing the DPDK for Failsafe https://dpdk.readthedocs.io/en/v17.08/nics/fail_safe.html#using-the-fail-safe-pmd-from-the-eal-command-line HTH. -- Regards, Balaji. From: on behalf of Chris King Date: Thursday, January 23, 2020 at 7:28 AM To: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure Update: I had forgotten to modprobe (i.e. load) the ib_uverbs and mlx4_ib drivers which are required for my NICs on Azure. I noticed that something was wrong when looking at the output of 'sudo vppctl show log'. I then went back and tried to get DPDK's testpmd application to work and from the output there it pointed to the missing drivers. I did manage to get testpmd to attach to my drivers. However, things are still not working correctly from the VPP side (maybe it's the way that VPP is initializing DPDK?). Getting back to your question, I'm not sure what you mean by the remote end of the FailsafeEthernet0 interface since this is a DPDK interface using the failsafe PMD (netvsc, in this case). The underlying hardware this device is related to are the eth1 and rename6 interfaces since they have the same MAC address and the PCI address of 0002:00:02.0: sudo lshw -class network -businfo Bus info Device Class Description pci@0001:00:02.0 rename5 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0002:00:02.0 rename6 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] pci@0003:00:02.0 rename7 networkMT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] sudo ./dpdk-devbind.py --status Network devices using DPDK-compatible driver Network devices using kernel driver === 0001:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename5 drv=mlx4_core unused= 0002:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename6 drv=mlx4_core unused= 0003:00:02.0 'MT27500/MT27520 Family [ConnectX-3/ConnectX-3 Pro Virtual Function] 1004' if=rename7 drv=mlx4_core unused= Now, if I try to bring up the interface on the link I get the following output in 'sudo vppctl show hardware': vpp# show hardware NameIdx Link Hardware FailsafeEthernet0 1 up FailsafeEthernet0 Link speed: 10 Gbps Ethernet address 00:0d:3a:f4:eb:8d FailsafeEthernet carrier up full duplex mtu 1504 flags: admin-up pmd maybe-multiseg rx-ip4-cksum rx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) tx: queues 1 (max 16), desc 1024 (min 0 max 65535 align 1) max rx packet len: 1522 promiscuous: unicast off all-multicast off vlan offload: strip off filter off qinq off rx offload avail: ipv4-cksum udp-cksum tcp-cksum scatter rx offload active: ipv4-cksum scatter tx offload avail: ipv4-cksum udp-cksum tcp-cksum tcp-tso multi-segs tx offload active: multi-segs rss avail: ipv4-frag ipv4-tcp ipv4-udp ipv4-other ipv4 ipv6-tcp-ex ipv6-udp-ex ipv6-frag ipv6-tcp ipv6-udp ipv6-other ipv6-ex ipv6 rss active:none tx burst function: failsafe_tx_burst rx burst function: failsafe_rx_burst Errors: rte_eth_dev_start[port:0, errno:-19]: Unknown error -19 So, it's showing as up with with an error on the call to rte_eth_dev_start. Now 'sudo vppctl show log' shows these log entries (and the attach device entries keep repeating): 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 14:37:40:578 notice dpdk EAL: Driver cannot attach the device (0002:00:02.0) 2020/01/23 14:37:40:578 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 14:37:40:578 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 14:37:40:578 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 14:37:40:578 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 14:37:40:578 notice dpdk EAL:
Re: [vpp-dev] interface activation problem using VPP in Azure with DPDK failsafe interfaces #vpp #dpdk #azure
Thanks for your reply and for looping in Damjan. I have had a fair bit of success initializing DPDK directly on this same box on the same adapters. Both of the following testpmd commands work for me and the interfaces are attached to properly: sudo ./testpmd -l 0-3 -n 4 --vdev='net_failsafe0,dev(0002:00:02.0)' --vdev='net_failsafe1,dev(0003:00:02.0)' -b 0001:00:02.0 -- -i sudo ./testpmd -l 0-3 -n 4 --vdev='net_vdev_netvsc0,iface=eth1' --vdev='net_vdev_netvsc1,iface=eth2' -b 0001:00:02.0 -- -i Now, my DPDK devices are configured like this in the VPP config: dev 0002:00:02.0 vdev net_vdev_netvsc0,iface=eth1 dev 0003:00:02.0 vdev net_vdev_netvsc1,iface=eth2 And when I try to start VPP I see the following EAL parameters and failure to attach to the devices: 2020/01/23 19:02:45:346 warn dpdk *EAL init args: -c 2 -n 4 --in-memory --vdev net_vdev_netvsc0,iface=eth1 --vdev net_vdev_netvsc1,iface=eth2* --file-prefix vpp -w 0002:00:02.0 -w 0003:00:02.0 --master-lcore 1 2020/01/23 19:02:45:570 warn dpdk unsupported rx offloads requested on port 0: jumbo-frame 2020/01/23 19:02:45:572 warn dpdk unsupported rx offloads requested on port 2: jumbo-frame 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 4 lcore(s) 2020/01/23 19:02:45:574 notice dpdk EAL: Detected 1 NUMA nodes 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No free hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: No available hugepages reported in hugepages-1048576kB 2020/01/23 19:02:45:574 notice dpdk EAL: Probing VFIO support... 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xa80001000 != 0x7f0ac000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xc2000 != 0x7f028000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xd80003000 != 0x7efa4000) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc0a64000 != 0x7ef63fe0) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc16c5000 != 0x7ef23fc0) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2326000 != 0x7eee3fa0) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING! Base virtual address hint (0xdc2f87000 != 0x7eea3f80) not respected! 2020/01/23 19:02:45:574 notice dpdk EAL: This may cause issues with mapping memory into secondary processes 2020/01/23 19:02:45:574 notice dpdk EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles ! 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3) 2020/01/23 19:02:45:574 notice dpdk *EAL: Driver cannot attach the device (0002:00:02.0)* 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (No such file or directory) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4) 2020/01/23 19:02:45:574 notice dpdk *EAL: Driver cannot attach the device (0003:00:02.0)* 2020/01/23 19:02:45:574 notice dpdk EAL: Failed to attach device on primary process 2020/01/23 19:02:45:574 notice dpdk net_failsafe: sub_device 0 probe failed (File exists) 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:45:574 notice dpdk EAL: VFIO support not initialized 2020/01/23 19:02:45:574 notice dpdk EAL: Couldn't map new region for DMA 2020/01/23 19:02:45:574 notice dpdk tun_alloc(): Rx trigger disabled: Device or resource busy 2020/01/23 19:02:
Re: [vpp-dev] #vnet Any command to individually enable and disable IP forwarding per interface level
From: on behalf of "Gigo Thomas via Lists.Fd.Io" Reply to: "gig...@thinkpalm.com" Date: Thursday 23 January 2020 at 22:31 To: "vpp-dev@lists.fd.io" Cc: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] #vnet Any command to individually enable and disable IP forwarding per interface level [Edited Message Follows] Thank you. Actually, I was looking for a command similar to the following command in the Linux "sysctl net.ipv4.conf.eth0.forwarding=1" /*To enable ip forwarding*/ and "sysctl net.ipv4.conf.eth0.forwarding=0". /*To disable ip forwarding*/ there is no VPP equivalent for this linux command. IP forwarding is always on in VPP and cannot be disabled. /neale Even after executing the command set interface feature ip4-lookup arc ip4-unicast disable, packet is forwarded. Also, the command set interface feature arp-reply arc arp disable gives the error "unknown feature". Thanks -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15240): https://lists.fd.io/g/vpp-dev/message/15240 Mute This Topic: https://lists.fd.io/mt/69978408/21656 Mute #vnet: https://lists.fd.io/mk?hashtag=vnet&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] #vnet Any command to individually enable and disable IP forwarding per interface level
I don’t know, never tried. I would suggest though enabling an interface for
receiving IP packets the ‘standard way’
/neale
From: Paul Vinciguerra
Date: Thursday 23 January 2020 at 04:39
To: "Neale Ranns (nranns)"
Cc: "gig...@thinkpalm.com" , "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev] #vnet Any command to individually enable and disable IP
forwarding per interface level
Hi Neale,
Can you not also do:
comment { ingress direction }
set interface feature loop0 ip4-lookup arc ip4-unicast disable
comment { egress direction }
set interface feature loop0 arp-reply arc arp disable
On Wed, Jan 22, 2020 at 12:16 PM Neale Ranns via
Lists.Fd.Io
mailto:cisco@lists.fd.io>> wrote:
hi,
to enables IP4 forwarding on an interface, either apply an address or make it
unnumberered to another interface (that has an address);
set int ip addr
set int unnumbered use
to enables IP4 forwarding on an interface, either apply an address or enable
ip6 on it.
set int ip addr
enable ip6
/neale
From: mailto:vpp-dev@lists.fd.io>> on behalf of "Gigo
Thomas via Lists.Fd.Io"
mailto:thinkpalm@lists.fd.io>>
Reply to: "gig...@thinkpalm.com"
mailto:gig...@thinkpalm.com>>
Date: Wednesday 22 January 2020 at 23:38
To: "vpp-dev@lists.fd.io"
mailto:vpp-dev@lists.fd.io>>
Cc: "vpp-dev@lists.fd.io"
mailto:vpp-dev@lists.fd.io>>
Subject: [vpp-dev] #vnet Any command to individually enable and disable IP
forwarding per interface level
May I know if VPP has any command to individually enable/disable ip forwarding
per interface level.
Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15241): https://lists.fd.io/g/vpp-dev/message/15241
Mute This Topic: https://lists.fd.io/mt/69978408/21656
Mute #vnet: https://lists.fd.io/mk?hashtag=vnet&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[vpp-dev] issue with ARP and classify packet forwarding #classify
Hi, I would like to classify the packet and forward to desired destination - Classify hits the rules - ARP proxy enabled Expect the acl-hits goes to [ip4-arp] then hand over to [memif0/3-output], but end up packet dropped with ip4-arp: no source address for ARP request Any expert may share the what is missing from the debug CLI? Thank you. Po *Topology* *Commands :* vpp# create interface memif id 2 slave vpp# create interface memif id 3 slave vpp# set interface state memif0/2 up vpp# set interface state memif0/3 up vpp# classify table mask hex 00ff buckets 16 skip 1 vpp# classify session opaque-index 0 table-index 0 match hex 00060a0a02010a0a0202 action set-ip4-fib-id 100 vpp# classify session opaque-index 1 table-index 0 match hex 00060a0a02010a0a0203 action set-ip4-fib-id 200 vpp# ip route add 10.10.2.2/32 table 100 via memif0/3 vpp# ip route add 10.10.2.0/24 table 100 via memif0/2 vpp# ip route add 10.10.2.0/24 via memif0/2 vpp# set int input acl intfc memif0/2 ip4-table 0 vpp# set int ip address memif0/2 10.10.2.0/24 vpp# set ip arp proxy 10.10.2.1 - 10.10.2.11 vpp# set ip arp fib-id 100 proxy 10.10.2.1 - 10.10.2.11 vpp# set interface proxy-arp memif0/2 enable vpp# set interface proxy-arp memif0/3 enable vpp# ** *vpp# show classify table* [6]: heap offset 1200, elts 2, normal 0: [1200]: next_index -1 advance 0 opaque 0 action 1 metadata 1 k: 00060a0a02010a0a0202 *hits 3* , last_heard 494.07 vpp# show vlib graph ip4-arp Name Next Previous ip4-arp error-drop [0] nsh-adj-incomplete memif0/3-output [1] lookup-ip4-src lookup-ip4-dst-itf lookup-ip4-dst mpls-adj-incomplete tcp4-output bfd-udp-echo4-input bfd-udp4-input ip4-punt-redirect ip4-load-balance ip4-lookup ip4-classify *vpp# show ip fib index 1* ipv4-VRF:100, fib_index:1, flow hash:[src dst sport dport proto ] locks:[src:classify:1, ] 0.0.0.0/0 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:9 buckets:1 uRPF:7 to:[0:0]] [0] [@0]: dpo-drop ip4 0.0.0.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:10 buckets:1 uRPF:8 to:[0:0]] [0] [@0]: dpo-drop ip4 10.10.2.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:20 buckets:1 uRPF:18 to:[0:0]] [0] [@4]: ipv4-glean: memif0/2: mtu:9000 02fea803ab310806 10.10.2.0/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:24 buckets:1 uRPF:22 to:[0:0]] [0] [@2]: dpo-receive 10.10.2.2/32 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:19 buckets:1 uRPF:17 to:[3:180]] [0] [@3]: arp-ipv4: via 10.10.2.2 memif0/3 224.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:12 buckets:1 uRPF:10 to:[0:0]] [0] [@0]: dpo-drop ip4 240.0.0.0/4 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:11 buckets:1 uRPF:9 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:11 to:[0:0]] [0] [@0]: dpo-drop ip4 * Trace* Packet 12 00:08:13:344609: memif-input memif: hw_if_index 1 next-index 4 slot: ring 0 00:08:13:344620: ethernet-input IP4: b2:5f:84:5e:0b:43 -> 02:fe:a8:03:ab:31 00:08:13:344628: ip4-input TCP: 10.10.2.1 -> 10.10.2.2 tos 0x00, ttl 64, length 60, checksum 0xbb1c fragment id 0x6789, flags DONT_FRAGMENT TCP: 59057 -> 12345 seq. 0x692e832e ack 0x flags 0x02 SYN, tcp header: 40 bytes window 29200, checksum 0xf2cc 00:08:13:344634: ip4-inacl INACL: sw_if_index 1, next_index 1, table 0, offset 1200 00:08:13:344639: ip4-lookup *fib 1* dpo-idx 0 flow hash: 0x TCP: 10.10.2.1 -> 10.10.2.2 tos 0x00, ttl 64, length 60, checksum 0xbb1c fragment id 0x6789, flags DONT_FRAGMENT TCP: 59057 -> 12345 seq. 0x692e832e ack 0x flags 0x02 SYN, tcp header: 40 bytes window 29200, checksum 0xf2cc *00:08:13:344643: ip4-arp* TCP: 10.10.2.1 -> 10.10.2.2 tos 0x00, ttl 64, length 60, checksum 0xbb1c fragment id 0x6789, flags DONT_FRAGMENT TCP: 59057 -> 12345 seq. 0x692e832e ack 0x flags 0x02 SYN, tcp header: 40 bytes window 29200, checksum 0xf2cc *00:08:13:344647: error-drop* rx:memif0/2 00:08:13:344649: drop *ip4-arp: no source address for ARP request* -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15242): https://lists.fd.io/g/vpp-dev/message/15242 Mute This Topic: https://lists.fd.io/mt/70065120/21656 Mute #classify: https://lists.fd.io/mk?hashtag=classify&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
