Could you retry udp and see if it reports an error?

Thanks, 
Florin

> On Mar 29, 2018, at 3:25 PM, Satish <[email protected]> wrote:
> 
> Hi Florin,
> 
> Looks like server is not successfully UP when we use UDP APP. But on TCP it 
> is successful. Below is the app server details.
> 
> UDP:
> vpp# show app server
> Connection                              App                 
> vpp# 
> 
> 
> TCP:
> vpp# show app server
> Connection                              App                 
> [#0][T] 172.28.128.3:7891->0.0.0.0:0 <http://0.0.0.0:0/>    ldp-2519-app     
> 
> 
> Thanks,
> Satish.
> 
> 
> On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi Satish, 
> 
> What does “show app server” report?
> 
> Thanks,
> Florin
> 
> 
> 
>> On Mar 29, 2018, at 3:14 PM, Satish <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi,
>> 
>> I am trying to use Host stack of VPP for UDP connection through VCL library. 
>> Server application listen on port 7891.
>> 
>> But when i try to connect to this server, the connection is not successful 
>> saying (no listener).
>> 
>> But the same app when i change to use TCP it works fine.
>> 
>> Below is the trace info and VPP version information. Could some one please 
>> let me know what is
>> the issue in this? Does any one tried with VCL for UDP before and succeeded?
>> 
>> Thanks & Regards,
>> Satish.
>> 
>> 
>> vpp# show trace 
>> ------------------- Start of thread 0 vpp_main -------------------
>> Packet 1
>> 
>> 00:52:47:772356: dpdk-input
>>   GigabitEthernet0/8/0 rx queue 0
>>   buffer 0x3333: current data 14, length 46, free-list 0, clone-count 0, 
>> totlen-nifb 0, trace 0x0
>>                  ext-hdr-valid 
>>                  l4-cksum-computed l4-cksum-correct l2-hdr-offset 0 
>> l3-hdr-offset 14 
>>   PKT MBUF: port 0, nb_segs 1, pkt_len 60
>>     buf_len 2176, data_len 60, ol_flags 0x0, data_off 128, phys_addr 
>> 0x1f8ccd40
>>     packet_type 0x0 l2_len 0 l3_len 0 outer_l2_len 0 outer_l3_len 0
>>   IP4: 08:00:27:02:dd:ad -> 08:00:27:f9:67:0c
>>   UDP: 172.28.128.5 -> 172.28.128.3
>>     tos 0x00, ttl 64, length 37, checksum 0x38e9
>>     fragment id 0xa99d, flags DONT_FRAGMENT
>>   UDP: 37797 -> 7891
>>     length 17, checksum 0x63da
>> 00:52:47:772392: ip4-input
>>   UDP: 172.28.128.5 -> 172.28.128.3
>>     tos 0x00, ttl 64, length 37, checksum 0x38e9
>>     fragment id 0xa99d, flags DONT_FRAGMENT
>>   UDP: 37797 -> 7891
>>     length 17, checksum 0x63da
>> 00:52:47:772396: ip4-lookup
>>   fib 0 dpo-idx 7 flow hash: 0x00000000
>>   UDP: 172.28.128.5 -> 172.28.128.3
>>     tos 0x00, ttl 64, length 37, checksum 0x38e9
>>     fragment id 0xa99d, flags DONT_FRAGMENT
>>   UDP: 37797 -> 7891
>>     length 17, checksum 0x63da
>> 00:52:47:772398: ip4-local
>>     UDP: 172.28.128.5 -> 172.28.128.3
>>       tos 0x00, ttl 64, length 37, checksum 0x38e9
>>       fragment id 0xa99d, flags DONT_FRAGMENT
>>     UDP: 37797 -> 7891
>>       length 17, checksum 0x63da
>> 00:52:47:772401: ip4-udp-lookup
>>   UDP: src-port 37797 dst-port 7891 (no listener)
>> 00:52:47:772406: ip4-icmp-error
>>   UDP: 172.28.128.5 -> 172.28.128.3
>>     tos 0x00, ttl 64, length 37, checksum 0x38e9
>>     fragment id 0xa99d, flags DONT_FRAGMENT
>>   UDP: 37797 -> 7891
>>     length 17, checksum 0x63da
>> 
>> 
>> 
>> vpp# show version 
>> vpp v18.04-rc0~482-gf6647e0 built by vagrant on localhost at Mon Mar 26 
>> 23:54:12 PDT 2018
>> 
>> 
>> 
> 
> 
> 

Reply via email to