Re: [vpp-dev] VCL UDP connection failure

[Satish]

OK Thanks Florin will try as you suggested.

On Thu, Mar 29, 2018 at 6:58 PM, Florin Coras 
wrote:

> It seems that the udpserver app is trying to read on a session that vcl
> hasn’t yet marked as open. Are you by chance calling read on a listen
> session (i.e., before accept returns?). As previously mentioned on the
> list, the session layer does not support connectionless transports so
> protocols like udp still need to accept connections and only afterwards
> read from the fifos. I guess you followed that approach for tcp and that’s
> why it worked. Either way, we’re aware of the issue and we’ll be looking
> into it. For the time being, you could just replicate the tcp server logic
> for the udp server.
>
> Regards,
> Florin
>
> On Mar 29, 2018, at 3:47 PM, satish karunanithi 
> wrote:
>
> Hi Florin,
>
> I get the below error reported in VPP when we start the app.
>
> vpp# 0: vl_mem_send_client_keepalive_w_reg:539: REAPER: binary API client
> 'ldp-2673-app' died
> 0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid
> 2673
> 0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid
> 2673
>
>
>
> When i tried to enable VCL_DEBUG to check the issue, VCL library
> crashing.  I think there is some issue in DEBUG log code but when i disable
> Debug it did not crash.
> Anyways below crash is not the reason for UDP connection failure because
> when i disable the VCL_DEBUG no crash but still no server APP.
>
>
> ocket:1158: LDP<2024>: : calling vppcom_session_create(): proto 1
> (VPPCOM_PROTO_UDP), is_nonblocking 0
> vppcom_session_create:2430: VCL<2024>: sid 0
> socket:1200: LDP<2024>: : returning fd 512 (0x200)
> bind:1317: LDP<2024>: fd 512 (0x200): calling vppcom_session_bind(): sid 0
> (0x0), addr 0x7fffdeb0, len 16
> vppcom_session_bind:2632: VCL<2024>: sid 0: binding to local IPv4 address
> 172.28.128.3 port 7891, proto UDP
> bind:1352: LDP<2024>: fd 512 (0x200): returning 0 (0x0)
>
> Thread 1 "udpserver" received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/x86_64/strlen.S:106
> 106 ../sysdeps/x86_64/strlen.S: No such file or directory.
> (gdb) bt
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> #1  0x77ab425b in do_percent (va=0x7fffdc58, fmt= out>, _s=) at /vpp/build-data/../src/vppinfr
> a/format.c:332
> #2  va_format (s=0x7fffe307b1b4 "vppcom_session_read_internal:3117:
> VCL<2024>: vpp handle 0x", 'f' , ", sid 0: ",
> fmt=fmt@entry=0x77ba2580 "VCL<%d>: vpp handle 0x%llx, sid %u: %s
> session is not open! state 0x%x (%s), returning %d (%s)", va=va@entry
> =0x7fffdc58)
> at /vpp/build-data/../src/vppinfra/format.c:404
> #3  0x77aaed31 in _clib_error (how_to_die=how_to_die@entry=4,
> function_name=function_name@entry=0x77b9fe70 <__FUNCTION__.63886>
> "vppcom_session_read_internal",
> line_number=line_number@entry=3117, fmt=fmt@entry=0x77ba2580
> "VCL<%d>: vpp handle 0x%llx, sid %u: %s session is not open! state 0x%x
> (%s), returning %d (%s)")
> at /vpp/build-data/../src/vppinfra/error.c:127
> #4  0x77a97f99 in vppcom_session_read_internal (peek=0 '\000',
> n=1024, buf=0x7fffdf40, session_index=0) at
> /vpp/build-data/../src/vcl/vppcom.c:3113
> #5  vppcom_session_read (session_index=session_index@entry=0,
> buf=buf@entry=0x7fffdf40, n=n@entry=1024) at
> /vpp/build-data/../src/vcl/vppcom.c:3185
> #6  0x77a9f1e3 in vppcom_session_recvfrom
> (session_index=session_index@entry=0, buffer=buffer@entry=0x7fffdf40,
> buflen=buflen@entry=1024, flags=flags@entry=0,
> ep=ep@entry=0x7fffde10) at /vpp/build-data/../src/vcl/vpp
> com.c:5602
> #7  0x77a7fc00 in recvfrom (fd=512, buf=0x7fffdf40, n=1024,
> flags=0, addr=0x7fffdec0, addr_len=0x7fffdea0) at
> /vpp/build-data/../src/vcl/ldp.c:2121
> #8  0x004009ab in main () at udpserver.c:36
>
>
>
>
>
>
>
> On Thu, Mar 29, 2018 at 6:00 PM, Florin Coras 
> wrote:
>
>> Could you retry udp and see if it reports an error?
>>
>> Thanks,
>> Florin
>>
>> On Mar 29, 2018, at 3:25 PM, Satish  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:0ldp-2519-app
>>
>>
>> Thanks,
>> Satish.
>>
>>
>> On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras 
>> wrote:
>>
>>> Hi Satish,
>>>
>>> What does “show app server” report?
>>>
>>> Thanks,
>>> Florin
>>>
>>>
>>>
>>> On Mar 29, 2018, at 3:14 PM, Satish  wrote:
>>>
>>> Hi,
>>>
>>> I am trying to use Host stack of VPP for UDP connection through VCL
>>> library.
>>> Server application listen on port 7891.
>>>
>>> But 

Re: [vpp-dev] Semantics of field 'link_speed' in 'sw_interface_details' API.

[Chris Luke]

That only really leaves us one order of magnitude of growth…! :)

Chris

From:  on behalf of Damjan Marion 
Date: Thursday, March 29, 2018 at 12:53
To: "vpp-dev@lists.fd.io" 
Cc: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] Semantics of field 'link_speed' in 
'sw_interface_details' API.


Yes, but too late for 18.04. We can do that change later after rc1 is out.
I personally prefer that we simply keep speed as numeric value in 1kbps steps.
That should be fine for up to 4Tbps.


On 27 Mar 2018, at 14:58, Dmitry Vakhrushev 
> wrote:

Hi,

Changes in commit: 03f47f1e738051db1412a93c2b90a7426f81f648

This commit provided new ethernet speeds which store as speed bit in a 
variable. And the current version of API for 'sw_interface_details' is not 
correct for that changes.
Current variable in sw_interface_details API interface doesn't support all 
speeds because it was limited to 8 bits (this field has type u8).

I'd like to change the type to u32.

Can I do that?
Or can we change the semantics of representation of speed?
For example, speed in Mb or enum of speeds.

Now we have:
1) link_speed (now is u8, but need at least u16):
1 = 10M,
2 = 100M,
4 = 1G,
8 = 2_5G,
16 = 5G,
32 = 10G, etc.

We can do it like (need u32):
a) 10 = 10M.
100 = 100M,
1000 = 1G,
2500 = 2_5G,
5000 = 5G, etc.
or like this (need u8 field without changes):
b) 1 = 10M.
2 = 100M,
3 = 1G,
4 = 2_5G,
5 = 5G, etc.

Thank you,
-dmitry

[vpp-dev] Some DS Lite Questions

[Jon Loeliger]

Matus, et al,

I am looking at the DS Lite CLI and API calls.  I have a few questions.

Is there no way to remove either the B4 or AFTR tunnel endpoint once it is
set?

It seems there is maybe a missing dslite_pool_addr_dump API call?

Is there a future for the ip4_addr fields on the "set B4" and "set AFTR"
API calls?

The CLI doesn't set them.  And while the Python API appears to be able to
set them, they are not used in any implementation anywhere.

Finally, is there any plan to make any of the NAT parameters (snat_config())
available via an API call?  I'm specifically thinking about the
"deterministic"
and "is_ce" flags.  It seems these, and perhaps others, could be set at
API handling time if we all agreed it mean flushing the current NAT state
and re-initializing things?

Thanks,
jdl

Re: [vpp-dev] Semantics of field 'link_speed' in 'sw_interface_details' API.

[Damjan Marion]

Yes, but too late for 18.04. We can do that change later after rc1 is out.
I personally prefer that we simply keep speed as numeric value in 1kbps steps.
That should be fine for up to 4Tbps.

> On 27 Mar 2018, at 14:58, Dmitry Vakhrushev  wrote:
> 
> Hi,
> 
> Changes in commit: 03f47f1e738051db1412a93c2b90a7426f81f648
> 
> This commit provided new ethernet speeds which store as speed bit in a 
> variable. And the current version of API for 'sw_interface_details' is not 
> correct for that changes.
> Current variable in sw_interface_details API interface doesn't support all 
> speeds because it was limited to 8 bits (this field has type u8). 
> 
> I'd like to change the type to u32. 
> 
> Can I do that? 
> Or can we change the semantics of representation of speed?
> For example, speed in Mb or enum of speeds.
> 
> Now we have:
> 1) link_speed (now is u8, but need at least u16):
> 1 = 10M, 
> 2 = 100M, 
> 4 = 1G, 
> 8 = 2_5G,
> 16 = 5G,
> 32 = 10G, etc.
> 
> We can do it like (need u32):
> a) 10 = 10M. 
> 100 = 100M, 
> 1000 = 1G,
> 2500 = 2_5G,
> 5000 = 5G, etc.
> or like this (need u8 field without changes):
> b) 1 = 10M. 
> 2 = 100M, 
> 3 = 1G,
> 4 = 2_5G,
> 5 = 5G, etc.
> 
> Thank you,
> -dmitry
> 

Re: [vpp-dev] virtio devices add to white list

[Damjan Marion]

Why you cannot use uio_pci_generic or even better vfio-pci in no-iommu mode
instead of igb_uio?

> On 29 Mar 2018, at 20:18, Yichen Wang  wrote:
> 
> This is a general questions of Linux. Proper way is (1) Install the kernel 
> modules; (2) Create /etc/modules-load.d/.conf so KO will automatically 
> being loaded
> 
> More practical way, or for development:
> (1) If you have a systemd managed VPP service, you can add these commands in 
> the systemd service file as ExecPre task;
> (2) Just put this two line in /etc/rc.local.
> 
> Normally for long term, you may want to deal with kernel update case for this 
> particular KO.
> 
> Thanks very much!
> 
> Regards,
> Yichen 
> 
> On 3/29/18, 5:11 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)" 
>  wrote:
> 
>Yichen
>Also do I have to insmod the igb_uio or this can be done auto by vpp ? 
> where to put it ?
>Regards
>Avi
> 
>> -Original Message-
>> From: Avi Cohen (A)
>> Sent: Thursday, 29 March, 2018 2:34 PM
>> To: 'Yichen Wang (yicwang)'; vpp-dev@lists.fd.io
>> Subject: RE: [vpp-dev] virtio devices add to white list
>> 
>> Great Yichen,
>> I see that the interfaces should be down before VPP  startup, otherwise it 
>> does
>> not acquire the interface
>> 
>> Best Regards
>> Avi
>> 
>> 
>>> -Original Message-
>>> From: Yichen Wang (yicwang) [mailto:yicw...@cisco.com]
>>> Sent: Thursday, 29 March, 2018 9:45 AM
>>> To: Avi Cohen (A); vpp-dev@lists.fd.io
>>> Subject: Re: [vpp-dev] virtio devices add to white list
>>> 
>>> Hi, Avu,
>>> 
>>> If I am understanding correctly, you want to run VPP in a VM, while
>>> the interface is a virtio interface.
>>> 
>>> If that is the case, there is no difference as you want to use with a
>>> physical NIC interface. You need to get the PCI address of your virtio
>>> interface by using "lspci" + "ip" command. Or just this "basename
>>> $(readlink /sys/class/net/ens3/device)". Once you have the pci
>>> address, put below in the startup.conf file for VPP to consume:
>>> dpdk {
>>>  dev {{PCI_ADDRESS_1}}
>>>  dev {{PCI_ADDRESS_2}}
>>>  uio-driver igb_uio
>>> }
>>> 
>>> For uio-driver, you have the choice of igb_uio or vfio-pci. Up to you.
>>> If you want igb_uio, you may need to compile it manually from dpdk if on
>> RedHat distro.
>>> 
>>> Thanks very much!
>>> 
>>> Regards,
>>> Yichen
>>> 
>>> On 3/28/18, 10:54 PM, "vpp-dev@lists.fd.io on behalf of Avi Cohen
>>> (A)"  wrote:
>>> 
>>>Thank you Steven
>>>My interfaces are not vhost-user.
>>>Just virtio interfaces created on the host and then assigned to the VM.
>>>In my VM is see them as ens3 , ens4 etc...
>>> 
>>>Regards
>>>Avu
>>> 
>>> 
 -Original Message-
 From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
>> steven
 luong
 Sent: Wednesday, 28 March, 2018 7:08 PM
 To: vpp-dev@lists.fd.io
 Subject: Re: [vpp-dev] virtio devices add to white list
 
 Avi,
 
 Yes, you can. As an example, I have it like this in my startup.conf
 
 dpdk {
 vdev virtio_user0,path=/tmp/sock0
 }
 
 Steven
 
 On 3/28/18, 8:09 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)"
>>> >>> d...@lists.fd.io on behalf of avi.co...@huawei.com> wrote:
 
Hi
In the startup.conf , in the dpdk part we can add pci devices to the
>> white-
>>> list .
Is there option to also add virtual interfaces to white-list - I'm 
 running
>>> VPP on
 virtual-machine and I have few virtio devices that I would
>>> automatically add to
 VPP
 
Best Regards
Avi
 
 
 
 
 
 
 
>>> 
>>> 
>>> 
>>> 
>>> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8735): https://lists.fd.io/g/vpp-dev/message/8735
View All Messages In Topic (9): https://lists.fd.io/g/vpp-dev/topic/16303673
Mute This Topic: https://lists.fd.io/mt/16303673/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] building on Alpine Linux, MUSL C Lib

[Damjan Marion]

I went that way few weeks ago, but seems that DPDK is not very friendly to MUSL 
so I stopped.

Is your use case without DPDK?

> On 29 Mar 2018, at 11:41, Andreas Schultz  
> wrote:
> 
> Hi,
> 
> Has anyone succeded in building VPP on Alpine Linux with the MUSL C Lib?
> 
> It seems that -D_GNU_SOURCE is required for almost anything, but there are 
> still plenty of missing prototypes.
> 
> Andreas
> -- 
> -- 
> Dipl.-Inform. Andreas Schultz
> 
> --- enabling your networks --
> Travelping GmbH Phone:  +49-391-81 90 99 0
> Roentgenstr. 13 Fax:+49-391-81 90 99 299
> 39108 Magdeburg Email:  i...@travelping.com 
> 
> GERMANY Web:http://www.travelping.com 
> 
> 
> Company Registration: Amtsgericht StendalReg No.:   HRB 10578
> Geschaeftsfuehrer: Holger Winkelmann  VAT ID No.: DE236673780
> -
> 

Re: [vpp-dev] virtio devices add to white list

[Yichen Wang]

This is a general questions of Linux. Proper way is (1) Install the kernel 
modules; (2) Create /etc/modules-load.d/.conf so KO will automatically 
being loaded

More practical way, or for development:
(1) If you have a systemd managed VPP service, you can add these commands in 
the systemd service file as ExecPre task;
(2) Just put this two line in /etc/rc.local.

Normally for long term, you may want to deal with kernel update case for this 
particular KO.

Thanks very much!

Regards,
Yichen 

On 3/29/18, 5:11 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)" 
 wrote:

Yichen
Also do I have to insmod the igb_uio or this can be done auto by vpp ? 
where to put it ?
Regards
Avi

> -Original Message-
> From: Avi Cohen (A)
> Sent: Thursday, 29 March, 2018 2:34 PM
> To: 'Yichen Wang (yicwang)'; vpp-dev@lists.fd.io
> Subject: RE: [vpp-dev] virtio devices add to white list
> 
> Great Yichen,
> I see that the interfaces should be down before VPP  startup, otherwise 
it does
> not acquire the interface
> 
> Best Regards
> Avi
> 
> 
> > -Original Message-
> > From: Yichen Wang (yicwang) [mailto:yicw...@cisco.com]
> > Sent: Thursday, 29 March, 2018 9:45 AM
> > To: Avi Cohen (A); vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] virtio devices add to white list
> >
> > Hi, Avu,
> >
> > If I am understanding correctly, you want to run VPP in a VM, while
> > the interface is a virtio interface.
> >
> > If that is the case, there is no difference as you want to use with a
> > physical NIC interface. You need to get the PCI address of your virtio
> > interface by using "lspci" + "ip" command. Or just this "basename
> > $(readlink /sys/class/net/ens3/device)". Once you have the pci
> > address, put below in the startup.conf file for VPP to consume:
> > dpdk {
> >   dev {{PCI_ADDRESS_1}}
> >   dev {{PCI_ADDRESS_2}}
> >   uio-driver igb_uio
> > }
> >
> > For uio-driver, you have the choice of igb_uio or vfio-pci. Up to you.
> > If you want igb_uio, you may need to compile it manually from dpdk if on
> RedHat distro.
> >
> > Thanks very much!
> >
> > Regards,
> > Yichen
> >
> > On 3/28/18, 10:54 PM, "vpp-dev@lists.fd.io on behalf of Avi Cohen
> > (A)"  wrote:
> >
> > Thank you Steven
> > My interfaces are not vhost-user.
> > Just virtio interfaces created on the host and then assigned to the 
VM.
> > In my VM is see them as ens3 , ens4 etc...
> >
> > Regards
> > Avu
> >
> >
> > > -Original Message-
> > > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf 
Of
> steven
> > > luong
> > > Sent: Wednesday, 28 March, 2018 7:08 PM
> > > To: vpp-dev@lists.fd.io
> > > Subject: Re: [vpp-dev] virtio devices add to white list
> > >
> > > Avi,
> > >
> > > Yes, you can. As an example, I have it like this in my 
startup.conf
> > >
> > > dpdk {
> > >  vdev virtio_user0,path=/tmp/sock0
> > > }
> > >
> > > Steven
> > >
> > > On 3/28/18, 8:09 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen 
(A)"
> >  > > d...@lists.fd.io on behalf of avi.co...@huawei.com> wrote:
> > >
> > > Hi
> > > In the startup.conf , in the dpdk part we can add pci devices 
to the
> white-
> > list .
> > > Is there option to also add virtual interfaces to white-list 
- I'm running
> > VPP on
> > > virtual-machine and I have few virtio devices that I would
> > automatically add to
> > > VPP
> > >
> > > Best Regards
> > > Avi
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > 
> >
> >







-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8733): https://lists.fd.io/g/vpp-dev/message/8733
View All Messages In Topic (8): https://lists.fd.io/g/vpp-dev/topic/16303673
Mute This Topic: https://lists.fd.io/mt/16303673/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] opensuse gerrit jobs failing

[Dave Barach]

This package changes roughly once per vpp release, and then only if the new 
DPDK release happens to need it. It would be well worth caching a copy…

D.

From: vpp-dev@lists.fd.io  On Behalf Of Ed Kern (ejk)
Sent: Thursday, March 29, 2018 10:53 AM
To: vpp-dev@lists.fd.io
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] opensuse gerrit jobs failing

Hey nitin,


All over last weekend and apparently whenever this job was run the nasm 
download site was to
put it technically….totally busted.


(7) Failed to connect to www.nasm.us port 80: Connection 
refused

And thats what you see in your logs as well.   Whats annoying to me is that 
nasm is already installed on the server
as you can see early in the log


09:30:45 nasm.x86_64  2.13.02-1.1   
installed

Albeit a newer version than what is expected (not that at first glance i think 
that should make a difference).   So what needs
to happen, by me if necessary, is someone who speaks Makefile well to either:

a. search for a local copy of the tar (and me as the owner of the base build 
system will make damn sure its there)
b. look and see if a copy of the software is already installed
c. a+b

Nasm isn’t the only piece of dep software that has this issue…but its the 
one/website thats just been totally fubar the last
eight days or so…

Ed

PS only seen on opensuse image because currently its the only one that tries to 
build dpdk from scratch


On Mar 29, 2018, at 6:54 AM, Nitin Saxena 
> wrote:

Hi,

In gerrit patch: https://gerrit.fd.io/r/#/c/10148/ I am seeing opensuse job 
failures in master branch. I tried rechecking multiple times. Errors I have 
been seeing are following:

https://jenkins.fd.io/job/vpp-verify-master-opensuse/2627/console

10:45:30 curl: (6) Could not resolve host: ${HTTP_HOST}
10:45:30 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
10:45:30 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 6
10:45:30 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'
10:45:30 error: Bad exit status from /var/tmp/rpm-tmp.YslJIa (%install)


https://jenkins.fd.io/job/vpp-verify-master-opensuse/2624/console

09:31:20
 0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0curl: (7) Failed to connect to www.nasm.us port 80: 
Connection refused
09:31:20 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
09:31:20 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 7
09:31:20 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'
09:31:20 error: Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20
09:31:20
09:31:20 RPM build errors:
09:31:20 Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20 Makefile:392: recipe for target 'vpp-dpdk-devel-18.02-vpp1.x86_64.rpm' 
failed
09:31:20 make[2]: *** [vpp-dpdk-devel-18.02-vpp1.x86_64.rpm] Error 1


Any help how to fix this?

Thanks,
Nitin

Re: [vpp-dev] opensuse gerrit jobs failing

[Ed Kern]

Hey nitin,


All over last weekend and apparently whenever this job was run the nasm 
download site was to
put it technically….totally busted.


(7) Failed to connect to www.nasm.us port 80: Connection 
refused

And thats what you see in your logs as well.   Whats annoying to me is that 
nasm is already installed on the server
as you can see early in the log


09:30:45 nasm.x86_64  2.13.02-1.1   
installed

Albeit a newer version than what is expected (not that at first glance i think 
that should make a difference).   So what needs
to happen, by me if necessary, is someone who speaks Makefile well to either:

a. search for a local copy of the tar (and me as the owner of the base build 
system will make damn sure its there)
b. look and see if a copy of the software is already installed
c. a+b

Nasm isn’t the only piece of dep software that has this issue…but its the 
one/website thats just been totally fubar the last
eight days or so…

Ed

PS only seen on opensuse image because currently its the only one that tries to 
build dpdk from scratch

On Mar 29, 2018, at 6:54 AM, Nitin Saxena 
> wrote:

Hi,

In gerrit patch: https://gerrit.fd.io/r/#/c/10148/ I am seeing opensuse job 
failures in master branch. I tried rechecking multiple times. Errors I have 
been seeing are following:

https://jenkins.fd.io/job/vpp-verify-master-opensuse/2627/console

10:45:30 curl: (6) Could not resolve host: ${HTTP_HOST}
10:45:30 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
10:45:30 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 6
10:45:30 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'
10:45:30 error: Bad exit status from /var/tmp/rpm-tmp.YslJIa (%install)


https://jenkins.fd.io/job/vpp-verify-master-opensuse/2624/console

09:31:20
 0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0curl: (7) Failed to connect to www.nasm.us port 80: Connection refused
09:31:20 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
09:31:20 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 7
09:31:20 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'
09:31:20 error: Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20
09:31:20
09:31:20 RPM build errors:
09:31:20 Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20 Makefile:392: recipe for target 'vpp-dpdk-devel-18.02-vpp1.x86_64.rpm' 
failed
09:31:20 make[2]: *** [vpp-dpdk-devel-18.02-vpp1.x86_64.rpm] Error 1


Any help how to fix this?

Thanks,
Nitin

[vpp-dev] opensuse gerrit jobs failing

[Nitin Saxena]

Hi,

In gerrit patch: https://gerrit.fd.io/r/#/c/10148/ I am seeing opensuse 
job failures in master branch. I tried rechecking multiple times. Errors 
I have been seeing are following:


https://jenkins.fd.io/job/vpp-verify-master-opensuse/2627/console

10:45:30 curl: (6) Could not resolve host: ${HTTP_HOST}
10:45:30 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
10:45:30 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 6
10:45:30 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'

10:45:30 error: Bad exit status from /var/tmp/rpm-tmp.YslJIa (%install)


https://jenkins.fd.io/job/vpp-verify-master-opensuse/2624/console

09:31:20
  0 00 00 0  0  0 --:--:-- --:--:-- 
--:--:-- 0curl: (7) Failed to connect to www.nasm.us port 80: 
Connection refused
09:31:20 Makefile:232: recipe for target 
'/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz' failed
09:31:20 make[3]: *** 
[/w/workspace/vpp-verify-master-opensuse/dpdk/nasm-2.13.01.tar.xz] Error 7
09:31:20 make[3]: Leaving directory 
'/w/workspace/vpp-verify-master-opensuse/dpdk'

09:31:20 error: Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20
09:31:20
09:31:20 RPM build errors:
09:31:20 Bad exit status from /var/tmp/rpm-tmp.JQL7uQ (%install)
09:31:20 Makefile:392: recipe for target 
'vpp-dpdk-devel-18.02-vpp1.x86_64.rpm' failed

09:31:20 make[2]: *** [vpp-dpdk-devel-18.02-vpp1.x86_64.rpm] Error 1


Any help how to fix this?

Thanks,
Nitin

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8730): https://lists.fd.io/g/vpp-dev/message/8730
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/16427705
Mute This Topic: https://lists.fd.io/mt/16427705/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VCL UDP connection failure

[Florin Coras]

It seems that the udpserver app is trying to read on a session that vcl hasn’t 
yet marked as open. Are you by chance calling read on a listen session (i.e., 
before accept returns?). As previously mentioned on the list, the session layer 
does not support connectionless transports so protocols like udp still need to 
accept connections and only afterwards read from the fifos. I guess you 
followed that approach for tcp and that’s why it worked. Either way, we’re 
aware of the issue and we’ll be looking into it. For the time being, you could 
just replicate the tcp server logic for the udp server.

Regards, 
Florin

> On Mar 29, 2018, at 3:47 PM, satish karunanithi  wrote:
> 
> Hi Florin,
> 
> I get the below error reported in VPP when we start the app.
> 
> vpp# 0: vl_mem_send_client_keepalive_w_reg:539: REAPER: binary API client 
> 'ldp-2673-app' died
> 0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid 2673
> 0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid 2673
> 
> 
> 
> When i tried to enable VCL_DEBUG to check the issue, VCL library crashing.  I 
> think there is some issue in DEBUG log code but when i disable Debug it did 
> not crash. 
> Anyways below crash is not the reason for UDP connection failure because when 
> i disable the VCL_DEBUG no crash but still no server APP.
> 
> 
> ocket:1158: LDP<2024>: : calling vppcom_session_create(): proto 1 
> (VPPCOM_PROTO_UDP), is_nonblocking 0
> vppcom_session_create:2430: VCL<2024>: sid 0
> socket:1200: LDP<2024>: : returning fd 512 (0x200)
> bind:1317: LDP<2024>: fd 512 (0x200): calling vppcom_session_bind(): sid 0 
> (0x0), addr 0x7fffdeb0, len 16
> vppcom_session_bind:2632: VCL<2024>: sid 0: binding to local IPv4 address 
> 172.28.128.3 port 7891, proto UDP
> bind:1352: LDP<2024>: fd 512 (0x200): returning 0 (0x0)
> 
> Thread 1 "udpserver" received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/x86_64/strlen.S:106
> 106   ../sysdeps/x86_64/strlen.S: No such file or directory.
> (gdb) bt
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> #1  0x77ab425b in do_percent (va=0x7fffdc58, fmt=, 
> _s=) at /vpp/build-data/../src/vppinfra/format.c:332
> #2  va_format (s=0x7fffe307b1b4 "vppcom_session_read_internal:3117: 
> VCL<2024>: vpp handle 0x", 'f' , ", sid 0: ", 
> fmt=fmt@entry=0x77ba2580 "VCL<%d>: vpp handle 0x%llx, sid %u: %s 
> session is not open! state 0x%x (%s), returning %d (%s)", 
> va=va@entry=0x7fffdc58)
> at /vpp/build-data/../src/vppinfra/format.c:404
> #3  0x77aaed31 in _clib_error (how_to_die=how_to_die@entry=4, 
> function_name=function_name@entry=0x77b9fe70 <__FUNCTION__.63886> 
> "vppcom_session_read_internal", 
> line_number=line_number@entry=3117, fmt=fmt@entry=0x77ba2580 
> "VCL<%d>: vpp handle 0x%llx, sid %u: %s session is not open! state 0x%x (%s), 
> returning %d (%s)")
> at /vpp/build-data/../src/vppinfra/error.c:127
> #4  0x77a97f99 in vppcom_session_read_internal (peek=0 '\000', 
> n=1024, buf=0x7fffdf40, session_index=0) at 
> /vpp/build-data/../src/vcl/vppcom.c:3113
> #5  vppcom_session_read (session_index=session_index@entry=0, 
> buf=buf@entry=0x7fffdf40, n=n@entry=1024) at 
> /vpp/build-data/../src/vcl/vppcom.c:3185
> #6  0x77a9f1e3 in vppcom_session_recvfrom 
> (session_index=session_index@entry=0, buffer=buffer@entry=0x7fffdf40, 
> buflen=buflen@entry=1024, flags=flags@entry=0, 
> ep=ep@entry=0x7fffde10) at /vpp/build-data/../src/vcl/vppcom.c:5602
> #7  0x77a7fc00 in recvfrom (fd=512, buf=0x7fffdf40, n=1024, 
> flags=0, addr=0x7fffdec0, addr_len=0x7fffdea0) at 
> /vpp/build-data/../src/vcl/ldp.c:2121
> #8  0x004009ab in main () at udpserver.c:36
> 
> 
> 
> 
> 
> 
> 
> On Thu, Mar 29, 2018 at 6:00 PM, Florin Coras  > wrote:
> Could you retry udp and see if it reports an error?
> 
> Thanks, 
> Florin
> 
>> On Mar 29, 2018, at 3:25 PM, Satish > > 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 ldp-2519-app 
>> 
>> 
>> Thanks,
>> Satish.
>> 
>> 
>> On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras > > wrote:
>> Hi Satish, 
>> 
>> What does “show app server” report?
>> 
>> Thanks,
>> Florin
>> 
>> 
>> 
>>> On Mar 29, 2018, at 3:14 PM, Satish >> > wrote:
>>> 
>>> Hi,
>>> 
>>> I am trying to use Host stack of VPP for UDP 

Re: [vpp-dev] VCL UDP connection failure

[Satish]

Hi Florin,

I get the below error reported in VPP when we start the app.

vpp# 0: vl_mem_send_client_keepalive_w_reg:539: REAPER: binary API client
'ldp-2673-app' died
0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid 2673
0: svm_client_scan_this_region_nolock:1247: /vpe-api: cleanup ghost pid 2673



When i tried to enable VCL_DEBUG to check the issue, VCL library crashing.
I think there is some issue in DEBUG log code but when i disable Debug it
did not crash.
Anyways below crash is not the reason for UDP connection failure because
when i disable the VCL_DEBUG no crash but still no server APP.


ocket:1158: LDP<2024>: : calling vppcom_session_create(): proto 1
(VPPCOM_PROTO_UDP), is_nonblocking 0
vppcom_session_create:2430: VCL<2024>: sid 0
socket:1200: LDP<2024>: : returning fd 512 (0x200)
bind:1317: LDP<2024>: fd 512 (0x200): calling vppcom_session_bind(): sid 0
(0x0), addr 0x7fffdeb0, len 16
vppcom_session_bind:2632: VCL<2024>: sid 0: binding to local IPv4 address
172.28.128.3 port 7891, proto UDP
bind:1352: LDP<2024>: fd 512 (0x200): returning 0 (0x0)

Thread 1 "udpserver" received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/x86_64/strlen.S:106
#1  0x77ab425b in do_percent (va=0x7fffdc58, fmt=, _s=) at /vpp/build-data/../src/
vppinfra/format.c:332
#2  va_format (s=0x7fffe307b1b4 "vppcom_session_read_internal:3117:
VCL<2024>: vpp handle 0x", 'f' , ", sid 0: ",
fmt=fmt@entry=0x77ba2580 "VCL<%d>: vpp handle 0x%llx, sid %u: %s
session is not open! state 0x%x (%s), returning %d (%s)", va=va@entry
=0x7fffdc58)
at /vpp/build-data/../src/vppinfra/format.c:404
#3  0x77aaed31 in _clib_error (how_to_die=how_to_die@entry=4,
function_name=function_name@entry=0x77b9fe70 <__FUNCTION__.63886>
"vppcom_session_read_internal",
line_number=line_number@entry=3117, fmt=fmt@entry=0x77ba2580
"VCL<%d>: vpp handle 0x%llx, sid %u: %s session is not open! state 0x%x
(%s), returning %d (%s)")
at /vpp/build-data/../src/vppinfra/error.c:127
#4  0x77a97f99 in vppcom_session_read_internal (peek=0 '\000',
n=1024, buf=0x7fffdf40, session_index=0) at /vpp/build-data/../src/vcl/
vppcom.c:3113
#5  vppcom_session_read (session_index=session_index@entry=0,
buf=buf@entry=0x7fffdf40,
n=n@entry=1024) at /vpp/build-data/../src/vcl/vppcom.c:3185
#6  0x77a9f1e3 in vppcom_session_recvfrom
(session_index=session_index@entry=0, buffer=buffer@entry=0x7fffdf40,
buflen=buflen@entry=1024, flags=flags@entry=0,
ep=ep@entry=0x7fffde10) at /vpp/build-data/../src/vcl/vppcom.c:5602
#7  0x77a7fc00 in recvfrom (fd=512, buf=0x7fffdf40, n=1024,
flags=0, addr=0x7fffdec0, addr_len=0x7fffdea0) at
/vpp/build-data/../src/vcl/ldp.c:2121
#8  0x004009ab in main () at udpserver.c:36







On Thu, Mar 29, 2018 at 6:00 PM, Florin Coras 
wrote:

> Could you retry udp and see if it reports an error?
>
> Thanks,
> Florin
>
> On Mar 29, 2018, at 3:25 PM, Satish  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:0ldp-2519-app
>
>
> Thanks,
> Satish.
>
>
> On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras 
> wrote:
>
>> Hi Satish,
>>
>> What does “show app server” report?
>>
>> Thanks,
>> Florin
>>
>>
>>
>> On Mar 29, 2018, at 3:14 PM, Satish  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 0x: 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 -> 

Re: [vpp-dev] VCL UDP connection failure

[Florin Coras]

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

Thanks, 
Florin

> On Mar 29, 2018, at 3:25 PM, Satish  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 ldp-2519-app 
> 
> 
> Thanks,
> Satish.
> 
> 
> On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras  > wrote:
> Hi Satish, 
> 
> What does “show app server” report?
> 
> Thanks,
> Florin
> 
> 
> 
>> On Mar 29, 2018, at 3:14 PM, Satish > > 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 0x: 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: 0x
>>   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
>> 
>> 
>> 
> 
> 
> 

Re: [vpp-dev] VCL UDP connection failure

[Satish]

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:0ldp-2519-app


Thanks,
Satish.


On Thu, Mar 29, 2018 at 5:49 PM, Florin Coras 
wrote:

> Hi Satish,
>
> What does “show app server” report?
>
> Thanks,
> Florin
>
>
>
> On Mar 29, 2018, at 3:14 PM, Satish  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 0x: 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: 0x
>   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
>
>
>
> 
>
>
>

Re: [vpp-dev] VCL UDP connection failure

[Florin Coras]

Hi Satish, 

What does “show app server” report?

Thanks,
Florin



> On Mar 29, 2018, at 3:14 PM, Satish  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 0x: 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: 0x
>   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
> 
> 
> 
> 

[vpp-dev] VCL UDP connection failure

[Satish]

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 0x: 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: 0x
  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

Re: [vpp-dev] virtio devices add to white list

[Avi Cohen (A)]

Yichen
Also do I have to insmod the igb_uio or this can be done auto by vpp ? where to 
put it ?
Regards
Avi

> -Original Message-
> From: Avi Cohen (A)
> Sent: Thursday, 29 March, 2018 2:34 PM
> To: 'Yichen Wang (yicwang)'; vpp-dev@lists.fd.io
> Subject: RE: [vpp-dev] virtio devices add to white list
> 
> Great Yichen,
> I see that the interfaces should be down before VPP  startup, otherwise it 
> does
> not acquire the interface
> 
> Best Regards
> Avi
> 
> 
> > -Original Message-
> > From: Yichen Wang (yicwang) [mailto:yicw...@cisco.com]
> > Sent: Thursday, 29 March, 2018 9:45 AM
> > To: Avi Cohen (A); vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] virtio devices add to white list
> >
> > Hi, Avu,
> >
> > If I am understanding correctly, you want to run VPP in a VM, while
> > the interface is a virtio interface.
> >
> > If that is the case, there is no difference as you want to use with a
> > physical NIC interface. You need to get the PCI address of your virtio
> > interface by using "lspci" + "ip" command. Or just this "basename
> > $(readlink /sys/class/net/ens3/device)". Once you have the pci
> > address, put below in the startup.conf file for VPP to consume:
> > dpdk {
> >   dev {{PCI_ADDRESS_1}}
> >   dev {{PCI_ADDRESS_2}}
> >   uio-driver igb_uio
> > }
> >
> > For uio-driver, you have the choice of igb_uio or vfio-pci. Up to you.
> > If you want igb_uio, you may need to compile it manually from dpdk if on
> RedHat distro.
> >
> > Thanks very much!
> >
> > Regards,
> > Yichen
> >
> > On 3/28/18, 10:54 PM, "vpp-dev@lists.fd.io on behalf of Avi Cohen
> > (A)"  wrote:
> >
> > Thank you Steven
> > My interfaces are not vhost-user.
> > Just virtio interfaces created on the host and then assigned to the VM.
> > In my VM is see them as ens3 , ens4 etc...
> >
> > Regards
> > Avu
> >
> >
> > > -Original Message-
> > > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
> steven
> > > luong
> > > Sent: Wednesday, 28 March, 2018 7:08 PM
> > > To: vpp-dev@lists.fd.io
> > > Subject: Re: [vpp-dev] virtio devices add to white list
> > >
> > > Avi,
> > >
> > > Yes, you can. As an example, I have it like this in my startup.conf
> > >
> > > dpdk {
> > >  vdev virtio_user0,path=/tmp/sock0
> > > }
> > >
> > > Steven
> > >
> > > On 3/28/18, 8:09 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)"
> >  > > d...@lists.fd.io on behalf of avi.co...@huawei.com> wrote:
> > >
> > > Hi
> > > In the startup.conf , in the dpdk part we can add pci devices to 
> > the
> white-
> > list .
> > > Is there option to also add virtual interfaces to white-list - 
> > I'm running
> > VPP on
> > > virtual-machine and I have few virtio devices that I would
> > automatically add to
> > > VPP
> > >
> > > Best Regards
> > > Avi
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > 
> >
> >


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8723): https://lists.fd.io/g/vpp-dev/message/8723
View All Messages In Topic (7): https://lists.fd.io/g/vpp-dev/topic/16303673
Mute This Topic: https://lists.fd.io/mt/16303673/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] virtio devices add to white list

[Avi Cohen (A)]

Great Yichen,
I see that the interfaces should be down before VPP  startup, otherwise it does 
not acquire the interface 

Best Regards
Avi


> -Original Message-
> From: Yichen Wang (yicwang) [mailto:yicw...@cisco.com]
> Sent: Thursday, 29 March, 2018 9:45 AM
> To: Avi Cohen (A); vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] virtio devices add to white list
> 
> Hi, Avu,
> 
> If I am understanding correctly, you want to run VPP in a VM, while the
> interface is a virtio interface.
> 
> If that is the case, there is no difference as you want to use with a 
> physical NIC
> interface. You need to get the PCI address of your virtio interface by using
> "lspci" + "ip" command. Or just this "basename $(readlink
> /sys/class/net/ens3/device)". Once you have the pci address, put below in the
> startup.conf file for VPP to consume:
> dpdk {
>   dev {{PCI_ADDRESS_1}}
>   dev {{PCI_ADDRESS_2}}
>   uio-driver igb_uio
> }
> 
> For uio-driver, you have the choice of igb_uio or vfio-pci. Up to you. If you 
> want
> igb_uio, you may need to compile it manually from dpdk if on RedHat distro.
> 
> Thanks very much!
> 
> Regards,
> Yichen
> 
> On 3/28/18, 10:54 PM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)"  d...@lists.fd.io on behalf of avi.co...@huawei.com> wrote:
> 
> Thank you Steven
> My interfaces are not vhost-user.
> Just virtio interfaces created on the host and then assigned to the VM.
> In my VM is see them as ens3 , ens4 etc...
> 
> Regards
> Avu
> 
> 
> > -Original Message-
> > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
> steven
> > luong
> > Sent: Wednesday, 28 March, 2018 7:08 PM
> > To: vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] virtio devices add to white list
> >
> > Avi,
> >
> > Yes, you can. As an example, I have it like this in my startup.conf
> >
> > dpdk {
> >  vdev virtio_user0,path=/tmp/sock0
> > }
> >
> > Steven
> >
> > On 3/28/18, 8:09 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)"
>  > d...@lists.fd.io on behalf of avi.co...@huawei.com> wrote:
> >
> > Hi
> > In the startup.conf , in the dpdk part we can add pci devices to 
> the white-
> list .
> > Is there option to also add virtual interfaces to white-list - I'm 
> running
> VPP on
> > virtual-machine and I have few virtio devices that I would automatically
> add to
> > VPP
> >
> > Best Regards
> > Avi
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8722): https://lists.fd.io/g/vpp-dev/message/8722
View All Messages In Topic (6): https://lists.fd.io/g/vpp-dev/topic/16303673
Mute This Topic: https://lists.fd.io/mt/16303673/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] building on Alpine Linux, MUSL C Lib

[Andreas Schultz]

Hi,

Has anyone succeded in building VPP on Alpine Linux with the MUSL C Lib?

It seems that -D_GNU_SOURCE is required for almost anything, but there are
still plenty of missing prototypes.

Andreas
-- 
-- 
Dipl.-Inform. Andreas Schultz

--- enabling your networks --
Travelping GmbH Phone:  +49-391-81 90 99 0
Roentgenstr. 13 Fax:+49-391-81 90 99 299
39108 Magdeburg Email:  i...@travelping.com
GERMANY Web:http://www.travelping.com

Company Registration: Amtsgericht StendalReg No.:   HRB 10578
Geschaeftsfuehrer: Holger Winkelmann  VAT ID No.: DE236673780
-

Re: [vpp-dev] virtio devices add to white list

[Avi Cohen (A)]

Or maybe this is impossible to acquire theses linux interfaces in the VPP.
Should I  create a host-interface (af-packet) to connect this interface ?

For example to connect ens3 interface 
vppctl create host-interface name ens3   ?

Regards
Avi

> -Original Message-
> From: Avi Cohen (A)
> Sent: Thursday, 29 March, 2018 8:54 AM
> To: 'steven luong'; vpp-dev@lists.fd.io
> Subject: RE: [vpp-dev] virtio devices add to white list
> 
> Thank you Steven
> My interfaces are not vhost-user.
> Just virtio interfaces created on the host and then assigned to the VM.
> In my VM is see them as ens3 , ens4 etc...
> 
> Regards
> Avu
> 
> 
> > -Original Message-
> > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
> > steven luong
> > Sent: Wednesday, 28 March, 2018 7:08 PM
> > To: vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] virtio devices add to white list
> >
> > Avi,
> >
> > Yes, you can. As an example, I have it like this in my startup.conf
> >
> > dpdk {
> >  vdev virtio_user0,path=/tmp/sock0
> > }
> >
> > Steven
> >
> > On 3/28/18, 8:09 AM, "vpp-dev@lists.fd.io on behalf of Avi Cohen (A)"
> >  wrote:
> >
> > Hi
> > In the startup.conf , in the dpdk part we can add pci devices to the 
> > white-
> list .
> > Is there option to also add virtual interfaces to white-list - I'm
> > running VPP on virtual-machine and I have few virtio devices that I
> > would automatically add to VPP
> >
> > Best Regards
> > Avi
> >
> >
> >
> >
> >
> >
> > 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8719): https://lists.fd.io/g/vpp-dev/message/8719
View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/16303673
Mute This Topic: https://lists.fd.io/mt/16303673/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-