[vpp-dev] IPv4 packet is dropped

Hi everyone, I try to send pcap file to host-interface in vpp with tcpreplay . When I try to send pcap file, ipv4 packets dropped. When I try to ping host-interface, It doens't drop. Why ipv4 packets drop in vpp? How can I fix this? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to t

[vpp-dev] timer wheel usage queries

Hello I am trying to use timer_wheel framework to start a timer. I followed the examples given in fdio, but the expiry_callback function never being called back. I am not sure if timer failed to expire or my usage has problems. I used the below functions: Timer wheel Init: { tw_timer_wheel_1t_1

Re: [vpp-dev] IPv4 packet is dropped

If I had to bet: the FIB is not programmed correctly for the traffic that you're sending. "show error" or "trace add dpdk-input 100" - start pcap replay - "show trace". Please take a look at https://fdio-vpp.readthedocs.io/en/latest/troubleshooting/reportingissues/reportingissues.html. ___

Re: [vpp-dev] timer wheel usage queries

You didn't mention calling tw_timer_expire_timers_xxx(tw, now), which is the only force of physics which will actually cause a timer to expire. See also .../src/vppinfra/test_tw_timer.c, src/vlib/main.c or src/vnet/tcp/tcp.c for usage examples. The timer wheel code has been tested to N=60 milli

Re: [vpp-dev] IPv4 packet is dropped

Identify the input interface – “show interface” – identify the corresponding input node – “show run” - and then s/dpdk-input/actual-input-node-sourcing-traffic/ in the packet tracer “trace add” command. Please take the time to study available tools. D. From: Esin Erenoğlu Sent: Wednesday, Ju

Re: [vpp-dev] Re-connect to vpp will make client CPU high. (I have solved it).

Hi, Sorry, I made a mistake in last mail, if “vac_disconnect” called “unset_timeout” instead of “set_timeout", which would make client never ever connect to vpp. I found the correct solution and tested, in “vac_connect” function, it should call “timeout_in_progress=false” to unset the glob

[vpp-dev] MAINTAINERS update

Dear all, After the yesterday discussion, I submitted update for MAINTAINERS file. https://gerrit.fd.io/r/20089 I kindly ask all folks who maintain parts of the code to take a look and add missing/update existing entries… Thanks, Damjan-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] timer wheel usage queries

Additionally to Dave's answer, you also have to be very careful with the expected precision of the timers. When you're inserting a timer with a interval on N into a timer with a period of P, you timeout is not guaranteed to be N * P, it is more something like (N-1)*P < timeout < N*P. The reason fo

[vpp-dev] Active close case with outstanding data case issue of version 19.04 #vnet

>From the code, when active close in tcp_connection_close, the TCP state will >change to FIN_WAIT_1 and if there is TX data meanwhile, it will set TCP flag >TCP_CONN_FINPNDG also, but there is no method in the stack for this TCP to step into the FIN_WAIT_2 state, the only thing this TCP can happ

[vpp-dev] setsockopt with TCP_NODELAY

Hi, I was trying to use TCP_NODELAY socket option in my application. But I see that relevant code is "VPP-TBD" in vppcom.c. I see same comment for most of socket options.  Is there any other branch where code is available? If not, are there any plans to support setsockopt that involve communica

Re: [vpp-dev] setsockopt with TCP_NODELAY

Hi Nataraj, TCP defaults to TCP_NODELAY behavior, unless you need Nagle’s algorithm on, you should be fine. As for the socket options, no. At this time, ldp cannot change properties for established tcp connections. What sort of things are you missing? Thanks, Florin > On Jun 12, 2019, at 1

Re: [vpp-dev] setsockopt with TCP_NODELAY

Hi Florin, Thanks for reply. My question is setsockopt() for not yet established sessions i.e before connect(). I was trying to clearing TCP_NODELAY, setting TCP_MAXSEG(to much lower than interface MTU) and TCP_KEEPINTVL. These options need to be communicating to the vnet right? I was looking for

Re: [vpp-dev] setsockopt with TCP_NODELAY

Unfortunately, we don’t support any of those options at this time. In particular, the stack won’t delay segments and tcp doesn’t do keepalives. Do you really need those? If you need to constrain tcp mss, you can indirectly do it by configuring the tcp mtu as a vpp startup parameter. You can’t d

Re: [vpp-dev] some questions about LACP(link bonding mode 4)

There is no limit on the number of slaves in a bonding group in VPP’s implementation. I don’t know/remember how to select one port over another from the spec without reading it carefully again. Steven From: "Yang, Zhiyong" Date: Tuesday, June 11, 2019 at 11:09 PM To: "vpp-dev@lists.fd.io" , "S

Re: [vpp-dev] some questions about LACP(link bonding mode 4)

Thanks a lot, Steven. Does it mean that all linkings(active-slaves in the same bonding group) of negotiating successfully can join loading balance for TX in VPP , right? Thanks Zhiyong From: Steven Luong (sluong) [mailto:slu...@cisco.com] Sent: Thursday, June 13, 2019 12:10 PM To: Yang, Zhiyong

Re: [vpp-dev] some questions about LACP(link bonding mode 4)

I mean, Is there no limit on the number of active-slaves as well? From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Zhiyong Yang Sent: Thursday, June 13, 2019 1:30 PM To: Steven Luong (sluong) ; vpp-dev@lists.fd.io; Carter, Thomas N Cc: Kinsella, Ray Subject: Re: [vpp-dev] so