[dpdk-users] Why packet_type is zero?
arseniy.zaostrovnykh at epfl.ch
Fri Nov 6 16:05:58 CET 2015
Forgot to mention:
I tried KNI (first detaching eth1 and eth2 from the kernel) and pcap PMD
dpdk-node $ sudo examples/l3fwd/build/app/l3fwd -c 0x01 -n 2
--vdev=eth_pcap0,iface=eth2 --vdev=eth_pcap1,iface=eth1 -p 0x03
The sysptoms are identical.
On 06.11.2015 15:57, Arseniy Zaostrovnykh wrote:
> I have the following setup of VirtualBox machines on a single host:
> eth0: VBox NAT, connecting to the host internet
> eth1: 192.168.1.12/24
> and additional route for 192.168.0.0/16 -> gateway 192.168.1.11
> eth0: VBox NaT, connecting to the host internet
> eth1: 192.168.1.11/24
> eth2: 192.168.2.11/24
> Now I run
> node2 $ ping 192.168.2.13
> so, following the route, it sends the ping ICMP messages to
> 192.168.1.11 (dpdk-node).
> On the dpdk-node I run l3fwd:
> dpdk-node $ sudo examples/l3fwd/build/app/l3fwd -c 0x01 -n 2 -- -p
> 0x03 --config="(0,0,0),(1,0,0)"
> with APP_LOOKUP_METHOD = APP_LOOKUP_EXACT_MATCH, and with some
> debug-printfs. In particular I printf
> m->packet_type in the beginning of the l3fwd_simple_forward function.
> Why does it prints 0? What is a possible causes?
> P.S. my DPDK version is 2.1.0; The printf is executed on each ping
> message; tcpdump shows no other traffic in this internal network.
More information about the users