You mean that *ip4-udp-punt *node will directly write to tuntap interface for sending the packet to Kernel.
On Fri, Nov 18, 2016 at 5:54 PM, Dave Barach (dbarach) <dbar...@cisco.com> wrote: > Expected behavior. > > > > *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On > Behalf Of *Prerit Jain > *Sent:* Friday, November 18, 2016 5:33 AM > *To:* vpp-dev@lists.fd.io > *Subject:* [vpp-dev] Fwd: Punting UDP packets to Kernel > > > > > > > > Thanks Dave. > > > > After adding below code in /etc/vpp/startup.conf > > tuntap { > > enable > > } > > > > I am able to capture the packets in kernel using tcpdump. However still > the packet flow is terminating in *error-punt *in trace > > *...* > > *00:06:52:855592: ip4-local* > > * UDP: 70.1.1.58 -> 70.1.1.51* > > * tos 0x00, ttl 64, length 1028, checksum 0xcf79* > > * fragment id 0x1901* > > * UDP: 5000 -> 4500* > > * length 1008, checksum 0x8d26* > > *00:06:52:855592: ip4-udp-lookup* > > * UDP: src-port 5000 dst-port 4500* > > *00:06:52:855593: error-punt* > > * ip4-udp-punt: udp port punt* > > > > I do not see the node "tuntap-tx" in trace. While punting packet to > kernel, the packet will not pass through "tuntap-tx" ?? > > > > > > > > On Thu, Nov 17, 2016 at 11:30 PM, Dave Barach (dbarach) <dbar...@cisco.com> > wrote: > > See .../vnet/vnet/unix/tuntap.c vs. .../vnet/vnet/unix/tapcli.c. > > > > Only the tuntap device is capable of punting packets to the linux stack > through a tun interface. You picked the wrong one. > > > > Note that tuntap must be enabled explicitly from the vpp command line. > > > > Thanks… Dave > > > > *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On > Behalf Of *Prerit Jain > *Sent:* Thursday, November 17, 2016 7:08 AM > *To:* vpp-dev@lists.fd.io > *Subject:* [vpp-dev] Punting UDP packets to Kernel > > > > > > I want to send UDP packets with port 4500 to Kernel. > > > > For that I send UDP packets from external interface (70.1.1.58:port 5000) > to VPP host (70.1.1.51: 4500) and did below configuration. > > > > Set up the punt environment- > > * set punt udp 4500* > > Created the tap interface - > > * tap connect tap-0* > > > > *In the below capture VPP trace, the packet are not going beyond the node > (**ip4-udp-punt) **to kernel.* > > > > *00:06:52:855590: dpdk-input* > > * GigabitEthernet1/0/2 rx queue 0* > > * buffer 0x174fcf: current data 14, length 1028, free-list 0, totlen-nifb > 0, trace 0x9* > > * PKT MBUF: port 0, nb_segs 1, pkt_len 1042* > > * buf_len 2176, data_len 1042, ol_flags 0x0, data_off 128, phys_addr > 0xd753b2c0* > > * packet_type 0x211* > > * Packet Types* > > * RTE_PTYPE_L2_ETHER (0x0001) Ethernet packet* > > * RTE_PTYPE_L3_IPV4 (0x0010) IPv4 packet without extension headers* > > * RTE_PTYPE_L4_UDP (0x0200) UDP packet* > > * IP4: ec:f4:bb:d5:68:a6 -> ec:f4:bb:c4:4d:46* > > * UDP: 70.1.1.58 -> 70.1.1.51* > > * tos 0x00, ttl 64, length 1028, checksum 0xcf79* > > * fragment id 0x1901* > > * UDP: 5000 -> 4500* > > * length 1008, checksum 0x8d26* > > *00:06:52:855591: ip4-input-no-checksum* > > * UDP: 70.1.1.58 -> 70.1.1.51* > > * tos 0x00, ttl 64, length 1028, checksum 0xcf79* > > * fragment id 0x1901* > > * UDP: 5000 -> 4500* > > * length 1008, checksum 0x8d26* > > *00:06:52:855592: ip4-lookup* > > * fib 0 dpo-idx 5 flow hash: 0x00000000* > > * UDP: 70.1.1.58 -> 70.1.1.51* > > * tos 0x00, ttl 64, length 1028, checksum 0xcf79* > > * fragment id 0x1901* > > * UDP: 5000 -> 4500* > > * length 1008, checksum 0x8d26* > > *00:06:52:855592: ip4-local* > > * UDP: 70.1.1.58 -> 70.1.1.51* > > * tos 0x00, ttl 64, length 1028, checksum 0xcf79* > > * fragment id 0x1901* > > * UDP: 5000 -> 4500* > > * length 1008, checksum 0x8d26* > > *00:06:52:855592: ip4-udp-lookup* > > * UDP: src-port 5000 dst-port 4500* > > *00:06:52:855593: error-punt* > > * ip4-udp-punt: udp port punt* > > > > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
