Re: [vpp-dev] IP probe failure but ping from Host works!

[wenxian li]

Hi Andrew,

I failed to try the vpp ping today. Is it broken?

My testbed is quite simple:
vpp < --- > host

I can ping vpp from host.
However, I failed to ping host from vpp.

And I captured the echo request packets sent by vpp, looks like they are
malformed.
The data filed of ICMP Data is filled with 0, where we should have valid
icmp id/seq, etc.
I attached the pcap in the mail.

Any clues?

Thanks,
Wenxian


On Wed, Nov 2, 2016 at 5:06 AM, Andrew 👽 Yourtchenko 
wrote:

> Hi,
>
> When I was writing the ping code I had  noticed ip probe was already
> broken because its registration of the ICMP code via the magic
> initialization function happens before the magic initialization function of
> the ICMP module is called which then zeroizes all the registrations.
>
> So I just proceeded to implement the ping which happens to not have the
> same problem (maybe due to alphabet order!), and simultaneously keep an eye
> if anyone actually uses the ip probe function at all (it's IPv4 only)
>
> So for troubleshooting purpose please use ping rather than IP probe - but
> if you need ip probe function, please nudge me back! :)
>
> Hope this helps !
>
> --a
>
> On 28 Oct 2016, at 19:12, Shravan Ambati  wrote:
>
> Hi,
>
>
>
> I am new to vpp. I was following this tutorial -
> https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP
>
> I was able to ping from the host to the Vpp VM as per the tutorial.
>
> I can see the echo request/reply packets in the dpdk-input trace as well.
>
> But when I do ip probe on vpp command line to the host IP it fails –
>
>
>
> vpp# ip probe 172.29.X.XXX GigabitEthernet0/8/0
>
> ip probe-neighbor: Resolution failed for 172.29.X.XXX
>
>
>
>
>
> fib table shows packets for only two entries –
>
>
>
> vpp# show ip fib
>
> Table 0, fib_index 0, flow hash: src dst sport dport proto
>
>  Destination Packets  Bytes Adjacency
>
> 172.29.0.0/22   1248  116694 weight 1, index 3
>
>  arp
> GigabitEthernet0/8/0 172.29.X.XXX/22
>
>
>
>
>
>
>
>
>
> 172.29.X.XXX(Ip of GigabitEthernet0/8/0 )/32
> 443256 weight 1, index 4
>
>  local 172.29.3.164/22
>
>
>
>
>
>
>
> Any pointers on why the ip probe on Vpp fails?
>
>
>
> Thanks
>
> Shravan
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>


echo_req.pcap
Description: Binary data
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] IKEV2 Negotiation Failed

[薛欣颖]

Hi guys,

We are testing IKEV2. Something run unsuccessfully.The configuration and the 
information is shown below:

configuration:
create host-interface name eth0 hw-addr 02:fe:a0:d5:26:62
create host-interface name eth1 hw-addr 02:fe:63:d4:c1:df
set interface ip addr host-eth0 192.168.155.11/24
set interface ip addr host-eth1 14.1.1.1/24
set interface state host-eth0 up
set interface state host-eth1 up
ikev2 profile add pr1
ikev2 profile set pr1 auth shared-key-mic string Vpp123
ikev2 profile set pr1 id local fqdn vpp.home
ikev2 profile set pr1 id remote fqdn roadwarrior.vpn.example.com
ikev2 profile set pr1 traffic-selector local ip-range 14.1.1.0 - 14.1.1.255 
port-range 0 - 65535 protocol 0
ikev2 profile set pr1 traffic-selector remote ip-range 21.1.1.0 - 21.1.1.255 
port-range 0 - 65535 protocol 0 

Is there anything wrong in my configuration?

Failed information:
DBGvpp# 0: ikev2_process_sa_init_req:566: ispi 18ee23578923e6c1 rspi 0 
nextpayload 21 version 20 exchange 22 flags 8 msgid 0 length 456
0: ikev2_parse_sa_payload:364: proposal num 1 len 44 last_or_more 0 id 1 
spi_size 0 num_transforms 4
0: ikev2_parse_sa_payload:406: transform num 0 len 12 last_or_more 3 type 
encr:aes-cbc-256 id 12 attrs 800e0100
0: ikev2_parse_sa_payload:406: transform num 1 len 8 last_or_more 3 type 
integ:sha1-96 id 2
0: ikev2_parse_sa_payload:406: transform num 2 len 8 last_or_more 3 type 
prf:hmac-sha1 id 2
0: ikev2_parse_sa_payload:406: transform num 3 len 8 last_or_more 0 type 
dh-group:modp-2048 id 14
0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_SOURCE_IP len 28 data 
60123943d9d1f5645386b64452702ac2c38eab1b
0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_DESTINATION_IP len 28 
data 36f531a2cf407b56600a5707b42179300aab3660
0: ikev2_parse_notify_payload:464: msg_type SIGNATURE_HASH_ALGORITHMS len 16 
data 0001000200030004
0: ikev2_parse_notify_payload:464: msg_type REDIRECT_SUPPORTED len 8
0: ikev2_process_sa_init_req:624: sa state changed to IKEV2_STATE_SA_INIT
0: ikev2_select_proposal:167: bitmap is 1e mandatory is 1e optional is 1e
Aborted

CAll stack:
Program received signal SIGFPE, Arithmetic exception.
0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0
(gdb) bt
#0  0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0
#1  0x2b4d8d24 in BN_div () from /lib/libcrypto.so.1.0.0
#2  0x2b4dfd18 in BN_nnmod () from /lib/libcrypto.so.1.0.0
#3  0x2b4e4770 in BN_mod_inverse () from /lib/libcrypto.so.1.0.0
#4  0x2b4eab60 in BN_MONT_CTX_set () from /lib/libcrypto.so.1.0.0
#5  0x2b4eae98 in BN_MONT_CTX_set_locked () from /lib/libcrypto.so.1.0.0
#6  0x2b5191ac in generate_key () from /lib/libcrypto.so.1.0.0
#7  0x2ae26674 in ikev2_generate_dh (sa=0x2b82bb94, t=0x2be390a8)
at /home/vpp/build-data/../src/vnet/ipsec/ikev2_crypto.c:410
#8  0x2ae10268 in ikev2_generate_sa_init_data (sa=0x2b82bb94)
at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:368
#9  0x2ae1a28c in ikev2_node_fn (vm=0x2aba0e40, node=0x2bc75340, 
frame=0x2bf1a500) at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:2128
#10 0x2ab1d554 in dispatch_node (vm=0x2aba0e40, node=0x2bc75340, 
type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, 
frame=0x2bf1a500, last_time_stamp=1320020664777)
at /home/vpp/build-data/../src/vlib/main.c:1016
#11 0x2ab1cfa4 in dispatch_pending_node (vm=0x2aba0e40, p=0x2bea84b4, 
last_time_stamp=1320020664777)
at /home/vpp/build-data/../src/vlib/main.c:1162
#12 0x2ab20a94 in vlib_main_or_worker_loop (vm=0x2aba0e40, is_main=1)
at /home/vpp/build-data/../src/vlib/main.c:1618
#13 0x2ab1f8cc in vlib_main_loop (vm=0x2aba0e40)
at /home/vpp/build-data/../src/vlib/main.c:1638
#14 0x2ab21fc8 in vlib_main (vm=0x2aba0e40, input=0x2b82bfdc)
at /home/vpp/build-data/../src/vlib/main.c:1774
#15 0x2ab71688 in thread0 (arg=716836416)
at /home/vpp/build-data/../src/vlib/unix/main.c:507
#16 0x2b2c7e18 in clib_calljmp (func=0x2ab7161c , 
func_arg=716836416, stack=0x2b82c000)
at /home/vpp/build-data/../src/vppinfra/mips32_clib_jump.c:24
Backtrace stopped: frame did not save the PC
(gdb) 

In addtion,my vpp version:
DBGvpp# show version
vpp v17.07-rc0~226-gb5c13fd built by root on ubuntu at Fri May 26 18:07:52 PDT 
2017

What should I do to solve the problem?

Thanks,
xyxue




___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] State of the verify jobs

[Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)]

Hmm, system-wide modules will probably have no effect, as we use
virtualenv to install our own modules as needed as part of make test.

I wonder why this suddenly fails, when it worked before?

Quoting Ed Warnicke (2017-06-01 05:15:55)
>A brief probe patch indicates that we already have the latest python 'six'
>module installed:
>[1]https://gerrit.fd.io/r/#/c/6966/
>
> [2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubuntu1604/581/console
> 
>  02:59:03 python-six is already the newest version (1.10.0-3).
> 
>  Ed
> 
>On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <[3]hagb...@gmail.com> wrote:
> 
>  We've had some turbulence in the last couple of days.
>  We are back to triggering jobs correctly, but we appear to be having an
>  issue with a missing python module that is causing issues for make test:
>  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console
>  We are missing a module named '[5]six' that provides python2 and python
>  3 compatibility. As a result several python module installs are failing:
>  19:31:29   Copying subprocess32.egg-info to
>  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
>  19:31:29   running install_scripts
>  19:31:29   Traceback (most recent call last):
>  19:31:29     File "", line 1, in 
>  19:31:29     File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  60, in 
>  19:31:29       main()
>  19:31:29     File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  54, in main
>  19:31:29       'Programming Language :: Python :: Implementation ::
>  CPython',
>  19:31:29     File "/usr/lib/python2.7/distutils/core.py", line 151, in
>  setup
>  19:31:29       dist.run_commands()
>  19:31:29     File "/usr/lib/python2.7/distutils/dist.py", line 953, in
>  run_commands
>  19:31:29       self.run_command(cmd)
>  19:31:29     File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29       cmd_obj.run()
>  19:31:29     File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
>  line 235, in run
>  19:31:29       self.run_command('install')
>  19:31:29     File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29       self.distribution.run_command(command)
>  19:31:29     File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29       cmd_obj.run()
>  19:31:29     File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/install.py",
>  line 61, in run
>  19:31:29       return orig.install.run(self)
>  19:31:29     File "/usr/lib/python2.7/distutils/command/install.py",
>  line 613, in run
>  19:31:29       self.run_command(cmd_name)
>  19:31:29     File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29       self.distribution.run_command(command)
>  19:31:29     File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29       cmd_obj.run()
>  19:31:29     File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/install_scripts.py",
>  line 17, in run
>  19:31:29       import setuptools.command.easy_install as ei
>  19:31:29     File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/easy_install.py",
>  line 49, in 
>  19:31:29       from setuptools.py27compat import rmtree_safe
>  19:31:29     File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/py27compat.py",
>  line 7, in 
>  19:31:29       import six
>  19:31:29   ImportError: No module named six
> 
> References
> 
>Visible links
>1. https://gerrit.fd.io/r/#/c/6966/
>2. 
> http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubuntu1604/581/console
>3. mailto:hagb...@gmail.com
>4. https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console
>5. https://pypi.python.org/pypi/six
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] How to send stats or information to control plane

[王鹏]

Hi,
   we need to send information to control plane at any time in our vpp 
application. Which way can we use ? The Events API ? How to use ? Can anyone 
explain this or provide a sample ? Thank you !___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP/How To Build The Sample Plugin

[Kinsella, Ray]

Its conservative - makes fewer changes and preserves the separate 
packaging for the sample plugin, so its a good approach.


My only piece of feedback on it, is that we are starting to end up with 
build 'config' divided across 'build-data' and environment variables, 
which is something we may need to make consistent over time.


I don't know if the sample plugin is important enough to pollute the 
'make help' with detail of how to build it. I thought the 'build-data' 
config and markdown document describing the plugin and how to build it 
was a better approach.


In anycase (env var or build-data config), I am happy to excise from my 
original patch, the markdown doc, update it with the new build details 
and doxygen comments etc and submit those seperately. Once this patch 
goes through.


Ray K

On 31/05/2017 18:28, Damjan Marion (damarion) wrote:


Something like:

https://gerrit.fd.io/r/#/c/6962/



On 31 May 2017, at 18:50, Damjan Marion (damarion)  wrote:

What about:

export VPP_WITH_SAMPLE_PLUGIN=yes
make build
make run

Does this work for you?


On 31 May 2017, at 18:45, Kinsella, Ray  wrote:

I think the idea that a user needs to go all the effort to install VPP and then 
Sample plugin, in order to run trivial sample code as way too much work.

This is something we expect, they are going to copy and base a new plugin off. 
So why we would bother making them go to all the effort to install it on their 
system just to play with it.

Either way, I don't see this being reconciled, so I consigned the patch to 
/dev/null.

Ray K

On 31/05/2017 17:31, Damjan Marion (damarion) wrote:


On 31 May 2017, at 18:18, Kinsella, Ray  wrote:


Ok - but that doesn't get us any closer to helping newbies use the sample 
plugin with 'make build' and 'make run', right? They still need to install vpp, 
then the sample-plugin - lots of hoops.


make run is not built for running out-of-tree plugins but this should work:

make bootstrap
make pkg-deb
dpkg -i build-root/*.deb
cd src/examples/sample-plugin
autoreconf -fis
./configure
make
sudo make install



I disagree with a documentation heavy approach in principle, the wiki suggests, 
that it similarly goes 'out of sync' quiet quickly.

BTW - I wasn't advocating PLUGIN_DISABLED, I provided build-data configs in the 
same way we do enabling/disabling dpdk features.


ok



The updated patch provides the separation between example/sample plugins and 
plugins that was asked for. It re-uses all the same autotools configs as 
src/plugins, so shouldn't go out of sync.


i still disagree, sample-plugin should be stand-alone autotools project, you 
are removing configure.ac so for me it is no-go.



Ray K


On 31/05/2017 17:05, Damjan Marion (damarion) wrote:


I do not agree with that proposal, I think we need to have one sample of 
out-of-tree plugin as it is today.

Still, I agree that we need to help newbies and my proposal is that we just 
document build process for out-of-tree plugins with simple README.md inside 
src/examples/sample-plugin.

btw I consider use of PLUGIN_DISABLED (as default choice) as evil, as it mens 
that plugin will go out of sync sooner or later.



On 31 May 2017, at 17:37, Kinsella, Ray  wrote:


Ok, typically example/sample code is intended to be used by the newest of the 
new, newbies. So the sample plugin should work with 'make build' and 'make run' 
with the minimum of hoops to enable. Asking these users to install and 
configure VPP, then do the same for the sample plugin is too much. I think that 
this thread exists, is testament that the UX could be better - too many hoops.

So here I what I suggest to fix.

We create src/examples/plugins, put the sample plugin in here.

The examples plugins (src/examples/plugins) are in-tree plugins and build in 
exactly the same way as src/plugins from a build PoV (PLUGIN_ENABLED etc), with 
the exception that the examples plugins are disabled by default. They also live 
in the sample directory with no symlinks etc to src/plugin. We then provide a 
way to explicitly enable them with a build-data config.

I reworked the patch along these lines, does it make sense?

Ray K

On 31/05/2017 10:15, Damjan Marion (damarion) wrote:


The idea of sample plugin is to show people how to build out-of-tree plugin. As 
that plugin was broken several times due to changes we made I created special 
ebuild package which builds sample plugin as part of verify job to ensure that 
plugin will not be broken again due to changes in vpp.

Saying that, I strongly disagree that we move sample plugin into src/plugins, 
as that is place for in-tree plugins which actually do something useful.
If people want to create additional in-tree plugin, there is many samples 
already in src/plugins so I don't see an need for additional one.

So to continue discussion on this particular change, what do you think that it 
is broken?

For me sequence:

autoreconf -fis
./configure
make
make install

Works perfectly fine. Off-course you need to hav

Re: [vpp-dev] IP probe failure but ping from Host works!

[wenxian li]

Previously, I tried stable.1704 branch (
https://nexus.fd.io/content/repositories/fd.io.stable.1704.ubuntu.xenial.main/)
and fails to ping.
Now I migrate to master branch (
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/) ,
and it works.

So some recent change might have fixed this issue, I think.

Thanks,
Wenxian

On Thu, Jun 1, 2017 at 3:06 PM, wenxian li  wrote:

> Hi Andrew,
>
> I failed to try the vpp ping today. Is it broken?
>
> My testbed is quite simple:
> vpp < --- > host
>
> I can ping vpp from host.
> However, I failed to ping host from vpp.
>
> And I captured the echo request packets sent by vpp, looks like they are
> malformed.
> The data filed of ICMP Data is filled with 0, where we should have valid
> icmp id/seq, etc.
> I attached the pcap in the mail.
>
> Any clues?
>
> Thanks,
> Wenxian
>
>
> On Wed, Nov 2, 2016 at 5:06 AM, Andrew 👽 Yourtchenko 
> wrote:
>
>> Hi,
>>
>> When I was writing the ping code I had  noticed ip probe was already
>> broken because its registration of the ICMP code via the magic
>> initialization function happens before the magic initialization function of
>> the ICMP module is called which then zeroizes all the registrations.
>>
>> So I just proceeded to implement the ping which happens to not have the
>> same problem (maybe due to alphabet order!), and simultaneously keep an eye
>> if anyone actually uses the ip probe function at all (it's IPv4 only)
>>
>> So for troubleshooting purpose please use ping rather than IP probe - but
>> if you need ip probe function, please nudge me back! :)
>>
>> Hope this helps !
>>
>> --a
>>
>> On 28 Oct 2016, at 19:12, Shravan Ambati 
>> wrote:
>>
>> Hi,
>>
>>
>>
>> I am new to vpp. I was following this tutorial -
>> https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP
>>
>> I was able to ping from the host to the Vpp VM as per the tutorial.
>>
>> I can see the echo request/reply packets in the dpdk-input trace as well.
>>
>> But when I do ip probe on vpp command line to the host IP it fails –
>>
>>
>>
>> vpp# ip probe 172.29.X.XXX GigabitEthernet0/8/0
>>
>> ip probe-neighbor: Resolution failed for 172.29.X.XXX
>>
>>
>>
>>
>>
>> fib table shows packets for only two entries –
>>
>>
>>
>> vpp# show ip fib
>>
>> Table 0, fib_index 0, flow hash: src dst sport dport proto
>>
>>  Destination Packets  Bytes Adjacency
>>
>> 172.29.0.0/22   1248  116694 weight 1, index 3
>>
>>  arp
>> GigabitEthernet0/8/0 172.29.X.XXX/22
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> 172.29.X.XXX(Ip of GigabitEthernet0/8/0 )/32
>> 443256 weight 1, index 4
>>
>>  local
>> 172.29.3.164/22
>>
>>
>>
>>
>>
>>
>>
>> Any pointers on why the ip probe on Vpp fails?
>>
>>
>>
>> Thanks
>>
>> Shravan
>>
>> ___
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>
>>
>> ___
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Invalid pool element access in vnet_add_del_ip4_arp_change_event function..?

[Nagaprabhanjan Bellari]

Hi,

Just wanted to confirm if this Is an issue - so I can file a jira ticket.

Thanks,
-nagp

On Tue, May 30, 2017 at 1:19 PM, Nagaprabhanjan Bellaru <
nagp.li...@gmail.com> wrote:

> Hi,
>
> In the recent change made to the above function to register for ARP
> events, it looks like there is an access to the pool elements using
> pointers across a pool_get call.
>
> --
>   while (p && *p != ~0)
> {
>   mc = pool_elt_at_index (am->mac_changes, *p);
>   if (mc->node_index == node_index && mc->type_opaque == type_opaque
>   && mc->pid == pid)
> break;
>   p = &mc->next_index;
> }
> --
>
> Above, p is pointing to a field inside a pool element. Then a pool
> allocation happens:
> --
>   pool_get (am->mac_changes, mc);
> --
>
> And later the old p is used to set the new_idx - which is an issue because
> pool_get above would have re-allocated the pool memory.
> --
>   if (p) {
> p[0] = new_idx;
>   }
> --
>
> Please let me know if my understanding is correct, so I can file a jira
> ticket.
>
> Thanks,
> -nagp
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Build failures on master

[Tomas Brännström]

Hi
I'm getting build errors when trying to build a recent commit on the master
branch:

/home/ubuntu/git/vpp/build-data/../src/vnet/tcp/builtin_client.c:25:29:
fatal error: vpp/app/version.h: No such file or directory
 #include 
 ^
compilation terminated.

I'm building using the "extras/vagrant/build.sh" script (or
"build-root/vagrant/build.sh" in slightly earlier versions). What's strange
here is that I built it successfully on the exact same commit yesterday on
another machine. The commit in question
is 79ea7ec3b3c04d334a21107818c64d70c42b99ae but I tried on the latest
master as well.

Also, I tried to build an earlier version (git tag v17.07-rc0) and got
another error, where the .deb files could not be built  because the
"version" was missing. I don't have the exact printout though.

Am I missing something here? I'm trying to build in an ubuntu trusty server
install, and it has worked before.

/Tomas
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] State of the verify jobs

[Ed Warnicke]

Klement,

It is an interesting question.  I presume however as we are installing
things via pip that it could be an upstream change.

Ed

On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> Hmm, system-wide modules will probably have no effect, as we use
> virtualenv to install our own modules as needed as part of make test.
>
> I wonder why this suddenly fails, when it worked before?
>
> Quoting Ed Warnicke (2017-06-01 05:15:55)
> >A brief probe patch indicates that we already have the latest
> python 'six'
> >module installed:
> >[1]https://gerrit.fd.io/r/#/c/6966/
> >[2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-
> ubuntu1604/581/console
> >
> >  02:59:03 python-six is already the newest version (1.10.0-3).
> >
> >  Ed
> >
> >On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <[3]hagb...@gmail.com>
> wrote:
> >
> >  We've had some turbulence in the last couple of days.
> >  We are back to triggering jobs correctly, but we appear to be
> having an
> >  issue with a missing python module that is causing issues for make
> test:
> >  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/
> 5699/console
> >  We are missing a module named '[5]six' that provides python2 and
> python
> >  3 compatibility. As a result several python module installs are
> failing:
> >  19:31:29   Copying subprocess32.egg-info to
> >  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
> >  19:31:29   running install_scripts
> >  19:31:29   Traceback (most recent call last):
> >  19:31:29 File "", line 1, in 
> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
> line
> >  60, in 
> >  19:31:29   main()
> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
> line
> >  54, in main
> >  19:31:29   'Programming Language :: Python :: Implementation ::
> >  CPython',
> >  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line
> 151, in
> >  setup
> >  19:31:29   dist.run_commands()
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 953, in
> >  run_commands
> >  19:31:29   self.run_command(cmd)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
> >  line 235, in run
> >  19:31:29   self.run_command('install')
> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326,
> in
> >  run_command
> >  19:31:29   self.distribution.run_command(command)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install.py",
> >  line 61, in run
> >  19:31:29   return orig.install.run(self)
> >  19:31:29 File "/usr/lib/python2.7/distutils/
> command/install.py",
> >  line 613, in run
> >  19:31:29   self.run_command(cmd_name)
> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326,
> in
> >  run_command
> >  19:31:29   self.distribution.run_command(command)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install_scripts.py",
> >  line 17, in run
> >  19:31:29   import setuptools.command.easy_install as ei
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/easy_install.py",
> >  line 49, in 
> >  19:31:29   from setuptools.py27compat import rmtree_safe
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/py27compat.py",
> >  line 7, in 
> >  19:31:29   import six
> >  19:31:29   ImportError: No module named six
> >
> > References
> >
> >Visible links
> >1. https://gerrit.fd.io/r/#/c/6966/
> >2. http://jenkins.ejkern.net:8080/job/vpp-verify-master-
> ubuntu1604/581/console
> >3. mailto:hagb...@gmail.com
> >4. https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/
> console
> >5. https://pypi.python.org/pypi/six
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] IKEV2 Negotiation Failed

[Nicolau, Radu]

Hi,

Can you check if the parameter passed to the DH_generate_key have both p and g 
members set?
Can you try a different DH group? Like modp-1024?
What is on the other side? VPP as well? Can you post the configuration of the 
initiatior?

Regards,
Radu

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Thursday, June 1, 2017 8:09 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] IKEV2 Negotiation Failed


Hi guys,

We are testing IKEV2. Something run unsuccessfully.The configuration and the 
information is shown below:

configuration:
create host-interface name eth0 hw-addr 02:fe:a0:d5:26:62
create host-interface name eth1 hw-addr 02:fe:63:d4:c1:df
set interface ip addr host-eth0 192.168.155.11/24
set interface ip addr host-eth1 14.1.1.1/24
set interface state host-eth0 up
set interface state host-eth1 up
ikev2 profile add pr1
ikev2 profile set pr1 auth shared-key-mic string Vpp123
ikev2 profile set pr1 id local fqdn vpp.home
ikev2 profile set pr1 id remote fqdn roadwarrior.vpn.example.com
ikev2 profile set pr1 traffic-selector local ip-range 14.1.1.0 - 14.1.1.255 
port-range 0 - 65535 protocol 0
ikev2 profile set pr1 traffic-selector remote ip-range 21.1.1.0 - 21.1.1.255 
port-range 0 - 65535 protocol 0 

Is there anything wrong in my configuration?

Failed information:
DBGvpp# 0: ikev2_process_sa_init_req:566: ispi 18ee23578923e6c1 rspi 0 
nextpayload 21 version 20 exchange 22 flags 8 msgid 0 length 456
0: ikev2_parse_sa_payload:364: proposal num 1 len 44 last_or_more 0 id 1 
spi_size 0 num_transforms 4
0: ikev2_parse_sa_payload:406: transform num 0 len 12 last_or_more 3 type 
encr:aes-cbc-256 id 12 attrs 800e0100
0: ikev2_parse_sa_payload:406: transform num 1 len 8 last_or_more 3 type 
integ:sha1-96 id 2
0: ikev2_parse_sa_payload:406: transform num 2 len 8 last_or_more 3 type 
prf:hmac-sha1 id 2
0: ikev2_parse_sa_payload:406: transform num 3 len 8 last_or_more 0 type 
dh-group:modp-2048 id 14
0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_SOURCE_IP len 28 data 
60123943d9d1f5645386b64452702ac2c38eab1b
0: ikev2_parse_notify_payload:464: msg_type NAT_DETECTION_DESTINATION_IP len 28 
data 36f531a2cf407b56600a5707b42179300aab3660
0: ikev2_parse_notify_payload:464: msg_type SIGNATURE_HASH_ALGORITHMS len 16 
data 0001000200030004
0: ikev2_parse_notify_payload:464: msg_type REDIRECT_SUPPORTED len 8
0: ikev2_process_sa_init_req:624: sa state changed to IKEV2_STATE_SA_INIT
0: ikev2_select_proposal:167: bitmap is 1e mandatory is 1e optional is 1e
Aborted

CAll stack:
Program received signal SIGFPE, Arithmetic exception.
0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0
(gdb) bt
#0  0x2b4e9f80 in bn_div_words () from /lib/libcrypto.so.1.0.0
#1  0x2b4d8d24 in BN_div () from /lib/libcrypto.so.1.0.0
#2  0x2b4dfd18 in BN_nnmod () from /lib/libcrypto.so.1.0.0
#3  0x2b4e4770 in BN_mod_inverse () from /lib/libcrypto.so.1.0.0
#4  0x2b4eab60 in BN_MONT_CTX_set () from /lib/libcrypto.so.1.0.0
#5  0x2b4eae98 in BN_MONT_CTX_set_locked () from /lib/libcrypto.so.1.0.0
#6  0x2b5191ac in generate_key () from /lib/libcrypto.so.1.0.0
#7  0x2ae26674 in ikev2_generate_dh (sa=0x2b82bb94, t=0x2be390a8)
at /home/vpp/build-data/../src/vnet/ipsec/ikev2_crypto.c:410
#8  0x2ae10268 in ikev2_generate_sa_init_data (sa=0x2b82bb94)
at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:368
#9  0x2ae1a28c in ikev2_node_fn (vm=0x2aba0e40, node=0x2bc75340, 
frame=0x2bf1a500) at /home/vpp/build-data/../src/vnet/ipsec/ikev2.c:2128
#10 0x2ab1d554 in dispatch_node (vm=0x2aba0e40, node=0x2bc75340, 
type=VLIB_NODE_TYPE_INTERNAL, dispatch_state=VLIB_NODE_STATE_POLLING, 
frame=0x2bf1a500, last_time_stamp=1320020664777)
at /home/vpp/build-data/../src/vlib/main.c:1016
#11 0x2ab1cfa4 in dispatch_pending_node (vm=0x2aba0e40, p=0x2bea84b4, 
last_time_stamp=1320020664777)
at /home/vpp/build-data/../src/vlib/main.c:1162
#12 0x2ab20a94 in vlib_main_or_worker_loop (vm=0x2aba0e40, is_main=1)
at /home/vpp/build-data/../src/vlib/main.c:1618
#13 0x2ab1f8cc in vlib_main_loop (vm=0x2aba0e40)
at /home/vpp/build-data/../src/vlib/main.c:1638
#14 0x2ab21fc8 in vlib_main (vm=0x2aba0e40, input=0x2b82bfdc)
at /home/vpp/build-data/../src/vlib/main.c:1774
#15 0x2ab71688 in thread0 (arg=716836416)
at /home/vpp/build-data/../src/vlib/unix/main.c:507
#16 0x2b2c7e18 in clib_calljmp (func=0x2ab7161c , 
func_arg=716836416, stack=0x2b82c000)
at /home/vpp/build-data/../src/vppinfra/mips32_clib_jump.c:24
Backtrace stopped: frame did not save the PC
(gdb) 

In addtion,my vpp version:
DBGvpp# show version
vpp v17.07-rc0~226-gb5c13fd built by root on ubuntu at Fri May 26 18:07:52 PDT 
2017


What should I do to solve the problem?


Thanks,
xyxue



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] State of the verify jobs

[Ed Kern (ejk)]

well as quickly as it came I no longer see this error on any build in the last 
three hours..

One comment though Ed its not clear if its what WAS biting us here..

I have a long history with deb/apt installed python packages (in this case 
python-six) ‘fighting’ with pip installed versions of packages
over the last couple years alone (and varying wildly with the version of pip) 
this can manifest itself in any number of ways:
a. pip not installing newer or prerequisite versions of a package because it 
refuses to ‘touch’ (aka remove) apt version of a package
b. pip installing newer version but software still pointed at or favoring the 
older version.
c. pip trying and failing (but thinking it succeeded) in removing deb installed 
version..

imho.. take one ‘boat’ or the other and don’t straddle otherwise your bound to 
get wet.

Ed



On Jun 1, 2017, at 7:20 AM, Ed Warnicke 
mailto:hagb...@gmail.com>> wrote:

Klement,

It is an interesting question.  I presume however as we are installing things 
via pip that it could be an upstream change.

Ed

On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON 
TECHNOLOGIES at Cisco) mailto:ksek...@cisco.com>> wrote:
Hmm, system-wide modules will probably have no effect, as we use
virtualenv to install our own modules as needed as part of make test.

I wonder why this suddenly fails, when it worked before?

Quoting Ed Warnicke (2017-06-01 05:15:55)
>A brief probe patch indicates that we already have the latest python 'six'
>module installed:
>[1]https://gerrit.fd.io/r/#/c/6966/
>
> [2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubuntu1604/581/console
>
>  02:59:03 python-six is already the newest version (1.10.0-3).
>
>  Ed
>
>On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke 
> <[3]hagb...@gmail.com> wrote:
>
>  We've had some turbulence in the last couple of days.
>  We are back to triggering jobs correctly, but we appear to be having an
>  issue with a missing python module that is causing issues for make test:
>  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console
>  We are missing a module named '[5]six' that provides python2 and python
>  3 compatibility. As a result several python module installs are failing:
>  19:31:29   Copying subprocess32.egg-info to
>  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
>  19:31:29   running install_scripts
>  19:31:29   Traceback (most recent call last):
>  19:31:29 File "", line 1, in 
>  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  60, in 
>  19:31:29   main()
>  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  54, in main
>  19:31:29   'Programming Language :: Python :: Implementation ::
>  CPython',
>  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line 151, in
>  setup
>  19:31:29   dist.run_commands()
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 953, in
>  run_commands
>  19:31:29   self.run_command(cmd)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
>  line 235, in run
>  19:31:29   self.run_command('install')
>  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29   self.distribution.run_command(command)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/install.py",
>  line 61, in run
>  19:31:29   return orig.install.run(self)
>  19:31:29 File "/usr/lib/python2.7/distutils/command/install.py",
>  line 613, in run
>  19:31:29   self.run_command(cmd_name)
>  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29   self.distribution.run_command(command)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/install_scripts.py",
>  line 17, in run
>  19:31:29   import setuptools.command.easy_install as ei
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/easy_install.py",
>  line 49, in 
>  19:31:29   from setuptoo

Re: [vpp-dev] State of the verify jobs

[Ed Warnicke]

We are still seeing the 'six' issue as of a few minutes ago:

https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console

Ed

On Thu, Jun 1, 2017 at 7:26 AM, Ed Kern (ejk)  wrote:

> well as quickly as it came I no longer see this error on any build in the
> last three hours..
>
> One comment though Ed its not clear if its what WAS biting us here..
>
> I have a long history with deb/apt installed python packages (in this case
> python-six) ‘fighting’ with pip installed versions of packages
> over the last couple years alone (and varying wildly with the version of
> pip) this can manifest itself in any number of ways:
> a. pip not installing newer or prerequisite versions of a package because
> it refuses to ‘touch’ (aka remove) apt version of a package
> b. pip installing newer version but software still pointed at or favoring
> the older version.
> c. pip trying and failing (but thinking it succeeded) in removing deb
> installed version..
>
> imho.. take one ‘boat’ or the other and don’t straddle otherwise your
> bound to get wet.
>
> Ed
>
>
>
> On Jun 1, 2017, at 7:20 AM, Ed Warnicke  wrote:
>
> Klement,
>
> It is an interesting question.  I presume however as we are installing
> things via pip that it could be an upstream change.
>
> Ed
>
> On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON
> TECHNOLOGIES at Cisco)  wrote:
>
>> Hmm, system-wide modules will probably have no effect, as we use
>> virtualenv to install our own modules as needed as part of make test.
>>
>> I wonder why this suddenly fails, when it worked before?
>>
>> Quoting Ed Warnicke (2017-06-01 05:15:55)
>> >A brief probe patch indicates that we already have the latest
>> python 'six'
>> >module installed:
>> >[1]https://gerrit.fd.io/r/#/c/6966/
>> >[2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubun
>> tu1604/581/console
>> >
>> >  02:59:03 python-six is already the newest version (1.10.0-3).
>> >
>> >  Ed
>> >
>> >On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <[3]hagb...@gmail.com>
>> wrote:
>> >
>> >  We've had some turbulence in the last couple of days.
>> >  We are back to triggering jobs correctly, but we appear to be
>> having an
>> >  issue with a missing python module that is causing issues for make
>> test:
>> >  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/56
>> 99/console
>> >  We are missing a module named '[5]six' that provides python2 and
>> python
>> >  3 compatibility. As a result several python module installs are
>> failing:
>> >  19:31:29   Copying subprocess32.egg-info to
>> >  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
>> >  19:31:29   running install_scripts
>> >  19:31:29   Traceback (most recent call last):
>> >  19:31:29 File "", line 1, in 
>> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
>> line
>> >  60, in 
>> >  19:31:29   main()
>> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
>> line
>> >  54, in main
>> >  19:31:29   'Programming Language :: Python :: Implementation ::
>> >  CPython',
>> >  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line
>> 151, in
>> >  setup
>> >  19:31:29   dist.run_commands()
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 953, in
>> >  run_commands
>> >  19:31:29   self.run_command(cmd)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 972, in
>> >  run_command
>> >  19:31:29   cmd_obj.run()
>> >  19:31:29 File
>> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python
>> /virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
>> >  line 235, in run
>> >  19:31:29   self.run_command('install')
>> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line
>> 326, in
>> >  run_command
>> >  19:31:29   self.distribution.run_command(command)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 972, in
>> >  run_command
>> >  19:31:29   cmd_obj.run()
>> >  19:31:29 File
>> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python
>> /virtualenv/local/lib/python2.7/site-packages/setuptools/
>> command/install.py",
>> >  line 61, in run
>> >  19:31:29   return orig.install.run(self)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/
>> command/install.py",
>> >  line 613, in run
>> >  19:31:29   self.run_command(cmd_name)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line
>> 326, in
>> >  run_command
>> >  19:31:29   self.distribution.run_command(command)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 972, in
>> >  run_command
>> >  19:31:29   cmd_obj.run()
>> >  19:31:29 File
>> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-

[vpp-dev] VPP Node Debug

[Alessio Silvestro]

Hi all,

I am using this code "https://gerrit.fd.io/r/#/c/6721/"; to in order to
enable an external process to receive UDP packets.

I tried to use printk -- including module.h in the c file.

When I compile VPP with:

TOPDIR/vpp make build-release

I got the following error

fatal error: linux/module.h: No such file or directory
compilation terminated.

Do you have any idea why?

Is there a better way to debug the code of a node in VPP?

Thanks,
Alessio
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Need some help on VPP

[Mahesh Ishwar Mathad]

Thanks for the great support.

The VPP platform grabs all available packets from RX rings to form a 
vector of packets. These vector of packets who will classify these 
packets either DPDK or VPP ?. If it is VPP how VPP will classify packet 
because what I am thinking for every packet VPP is decapsulating to know 
which packet actually it is, that particular packet is sent to the 
respected node. By this doing this mechanism VPP is simply wasting 
machine cycle. If my thinking is worng, please tell me which algorithm 
is this VPP is following so that i can understand.


On Wednesday 31 May 2017 12:52 AM, Burt Silverman wrote:
Another learning possibility, Mahesh: ./build-data/platforms/vpp.mk 
, you can uncomment vpp_enable_tests and then build 
./src/vppinfra/test_longjmp.c's program. Alternatively you can set 
TESTS  to test_longjmp in ./src/vppinfra.am  and 
build. Then you can run the test_longjmp program. Run it with one or 
more parameters and it will print something. I don't know much else 
about it. Also you might Google setjmp and longjmp -- I believe the 
clib_ versions are optimized and stylized for VPP.


Burt

On Tue, May 30, 2017 at 10:02 AM, Dave Barach (dbarach) 
 wrote:


Please look at the clib_calljmp(...) call in src/vlib/unix/main.c.
It calls the function “thread0” on the first allocated thread
stack. All of the other calls are similar.

Thanks… Dave

*From:*Mahesh Ishwar Mathad [mailto:mi.mah...@globaledgesoft.com
]
*Sent:* Tuesday, May 30, 2017 9:25 AM
*To:* Dave Barach (dbarach) ;
vpp-dev@lists.fd.io 
*Subject:* Re: [vpp-dev] Need some help on VPP

Thank you. As you mentioned function f, could you please tell for
which function respected stack is created and what is that
function f is responsible for?

On Tuesday 30 May 2017 05:10 PM, Dave Barach (dbarach) wrote:

Longjmp.S provides setjmp/longjmp and "call a function f on a new 
stack" support for multiple CPU architectures. Switching stacks involves saving, 
restoring, and avoiding damage to registers. The file is written in multiple assembly 
languages.

  


If you have specific questions, I'm willing to take a shot at answering 
them. You'll need to look at instruction set reference documents and compiler 
ABI documents to fully understand each implementation.

  


If you're not experienced with assembly language programming, I'd be 
tempted to steer clear. Stipulate that the code works, and move on...

  


Thanks... Dave

  


-Original Message-

From:vpp-dev-boun...@lists.fd.io   
[mailto:vpp-dev-boun...@lists.fd.io
] On Behalf Of Mahesh Ishwar Mathad

Sent: Tuesday, May 30, 2017 5:07 AM

To:vpp-dev@lists.fd.io 

Subject: [vpp-dev] Need some help on VPP

  


Hi Guys,

  


I need some help in understanding contents of the file ie.

./src/vppinfra/longjmp.S .

  

-- 


Thanks & Regards,

Mahesh Mathad.

Disclaimer:This message is intended only for the designated
recipient(s). It may contain confidential or proprietary
information and may be subject to other confidentiality
protections. If you are not a designated recipient, you may not
review, copy or distribute this message. Please notify the sender
by e-mail and delete this message. GlobalEdge does not accept any
liability for virus infected mails.

___ vpp-dev mailing
list vpp-dev@lists.fd.io 
https://lists.fd.io/mailman/listinfo/vpp-dev
 


--
Thanks & Regards,
Mahesh Mathad.


Disclaimer:- The information contained in this electronic message and any 
attachments to this message are intended for the exclusive use of the 
addressee(s) and may contain proprietary, confidential or privileged 
information. If you are not the intended recipient, you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately and 
destroy all copies of this message and any attachments. The views expressed in 
this E-mail message (including the enclosure/(s) or attachment/(s) if any) are 
those of the individual sender, except where the sender expressly, and with 
authority, states them to be the views of GlobalEdge. Before opening any mail 
and attachments please check them for viruses .GlobalEdge does not accept any 
liability for virus infected mails.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP Node Debug

[Luke, Chris]

printk() is typically a kernel thing, no? This isn’t kernel code. 😊

If you just want stuff on the console when running in a debugger, or 
interactively, clib_warning() may be what you are looking for.

Chris.


From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, June 1, 2017 10:35
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP Node Debug

Hi all,

I am using this code "https://gerrit.fd.io/r/#/c/6721/"; to in order to enable 
an external process to receive UDP packets.

I tried to use printk -- including module.h in the c file.

When I compile VPP with:

TOPDIR/vpp make build-release

I got the following error

fatal error: linux/module.h: No such file or directory
compilation terminated.

Do you have any idea why?

Is there a better way to debug the code of a node in VPP?

Thanks,
Alessio
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] State of the verify jobs

[Ed Kern (ejk)]

well that would certainly help me poke around to repo..

Now could you link the console log from a few minutes ago and not the
one from 13 hours ago?


Ed


On Jun 1, 2017, at 8:30 AM, Ed Warnicke 
mailto:hagb...@gmail.com>> wrote:

We are still seeing the 'six' issue as of a few minutes ago:

https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console

Ed

On Thu, Jun 1, 2017 at 7:26 AM, Ed Kern (ejk) 
mailto:e...@cisco.com>> wrote:
well as quickly as it came I no longer see this error on any build in the last 
three hours..

One comment though Ed its not clear if its what WAS biting us here..

I have a long history with deb/apt installed python packages (in this case 
python-six) ‘fighting’ with pip installed versions of packages
over the last couple years alone (and varying wildly with the version of pip) 
this can manifest itself in any number of ways:
a. pip not installing newer or prerequisite versions of a package because it 
refuses to ‘touch’ (aka remove) apt version of a package
b. pip installing newer version but software still pointed at or favoring the 
older version.
c. pip trying and failing (but thinking it succeeded) in removing deb installed 
version..

imho.. take one ‘boat’ or the other and don’t straddle otherwise your bound to 
get wet.

Ed



On Jun 1, 2017, at 7:20 AM, Ed Warnicke 
mailto:hagb...@gmail.com>> wrote:

Klement,

It is an interesting question.  I presume however as we are installing things 
via pip that it could be an upstream change.

Ed

On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON 
TECHNOLOGIES at Cisco) mailto:ksek...@cisco.com>> wrote:
Hmm, system-wide modules will probably have no effect, as we use
virtualenv to install our own modules as needed as part of make test.

I wonder why this suddenly fails, when it worked before?

Quoting Ed Warnicke (2017-06-01 05:15:55)
>A brief probe patch indicates that we already have the latest python 'six'
>module installed:
>[1]https://gerrit.fd.io/r/#/c/6966/
>
> [2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubuntu1604/581/console
>
>  02:59:03 python-six is already the newest version (1.10.0-3).
>
>  Ed
>
>On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke 
> <[3]hagb...@gmail.com> wrote:
>
>  We've had some turbulence in the last couple of days.
>  We are back to triggering jobs correctly, but we appear to be having an
>  issue with a missing python module that is causing issues for make test:
>  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console
>  We are missing a module named '[5]six' that provides python2 and python
>  3 compatibility. As a result several python module installs are failing:
>  19:31:29   Copying subprocess32.egg-info to
>  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
>  19:31:29   running install_scripts
>  19:31:29   Traceback (most recent call last):
>  19:31:29 File "", line 1, in 
>  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  60, in 
>  19:31:29   main()
>  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line
>  54, in main
>  19:31:29   'Programming Language :: Python :: Implementation ::
>  CPython',
>  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line 151, in
>  setup
>  19:31:29   dist.run_commands()
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 953, in
>  run_commands
>  19:31:29   self.run_command(cmd)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
>  line 235, in run
>  19:31:29   self.run_command('install')
>  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29   self.distribution.run_command(command)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python/virtualenv/local/lib/python2.7/site-packages/setuptools/command/install.py",
>  line 61, in run
>  19:31:29   return orig.install.run(self)
>  19:31:29 File "/usr/lib/python2.7/distutils/command/install.py",
>  line 613, in run
>  19:31:29   self.run_command(cmd_name)
>  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
>  run_command
>  19:31:29   self.distribution.run_command(command)
>  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
>  run_command
>  19:31:29   cmd_obj.run()
>  19:31:29 File
>  
> "/w/workspace/vpp-verif

Re: [vpp-dev] VPP Node Debug

[Alessio Silvestro]

I knew VPP run in user space and that printk is not the best option,
however from the documentation it is not clear to me how to do that.

For example now I inserted the command clib_warning("I am here!") in the
node I create -- that from vppctl show trace I can see processes the
packets.

Where does it prints?

Still I cannot figure it out.

Thanks,
Alessio

On Thu, Jun 1, 2017 at 6:00 PM, Luke, Chris  wrote:

> printk() is typically a kernel thing, no? This isn’t kernel code. 😊
>
>
>
> If you just want stuff on the console when running in a debugger, or
> interactively, clib_warning() may be what you are looking for.
>
>
>
> Chris.
>
>
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Alessio Silvestro
> *Sent:* Thursday, June 1, 2017 10:35
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] VPP Node Debug
>
>
>
> Hi all,
>
>
>
> I am using this code "https://gerrit.fd.io/r/#/c/6721/"; to in order to
> enable an external process to receive UDP packets.
>
>
>
> I tried to use printk -- including module.h in the c file.
>
>
>
> When I compile VPP with:
>
>
>
> TOPDIR/vpp make build-release
>
>
>
> I got the following error
>
>
>
> fatal error: linux/module.h: No such file or directory
>
> compilation terminated.
>
>
>
> Do you have any idea why?
>
>
>
> Is there a better way to debug the code of a node in VPP?
>
>
>
> Thanks,
>
> Alessio
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP Node Debug

[John Lo (loj)]

The output of clib_warning() call should be in the syslog. If running vpp in 
Ubuntu, take a look in /var/log/syslog.  -John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, June 01, 2017 12:11 PM
To: Luke, Chris 
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP Node Debug

I knew VPP run in user space and that printk is not the best option, however 
from the documentation it is not clear to me how to do that.

For example now I inserted the command clib_warning("I am here!") in the node I 
create -- that from vppctl show trace I can see processes the packets.

Where does it prints?

Still I cannot figure it out.

Thanks,
Alessio

On Thu, Jun 1, 2017 at 6:00 PM, Luke, Chris 
mailto:chris_l...@comcast.com>> wrote:
printk() is typically a kernel thing, no? This isn’t kernel code. 😊

If you just want stuff on the console when running in a debugger, or 
interactively, clib_warning() may be what you are looking for.

Chris.


From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Alessio Silvestro
Sent: Thursday, June 1, 2017 10:35
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] VPP Node Debug

Hi all,

I am using this code "https://gerrit.fd.io/r/#/c/6721/"; to in order to enable 
an external process to receive UDP packets.

I tried to use printk -- including module.h in the c file.

When I compile VPP with:

TOPDIR/vpp make build-release

I got the following error

fatal error: linux/module.h: No such file or directory
compilation terminated.

Do you have any idea why?

Is there a better way to debug the code of a node in VPP?

Thanks,
Alessio

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Build failures on master

[Florin Coras]

Hi Tomas, 

That sure is weird. 

(backup everything that’s not in git)
git clean -fdx
make bootstrap
make build

Do you still see the issue?

HTH, 
Florin

> On Jun 1, 2017, at 6:18 AM, Tomas Brännström  
> wrote:
> 
> Hi
> I'm getting build errors when trying to build a recent commit on the master 
> branch:
> 
> /home/ubuntu/git/vpp/build-data/../src/vnet/tcp/builtin_client.c:25:29: fatal 
> error: vpp/app/version.h: No such file or directory
>  #include 
>  ^
> compilation terminated.
> 
> I'm building using the "extras/vagrant/build.sh" script (or 
> "build-root/vagrant/build.sh" in slightly earlier versions). What's strange 
> here is that I built it successfully on the exact same commit yesterday on 
> another machine. The commit in question is 
> 79ea7ec3b3c04d334a21107818c64d70c42b99ae but I tried on the latest master as 
> well.
> 
> Also, I tried to build an earlier version (git tag v17.07-rc0) and got 
> another error, where the .deb files could not be built  because the "version" 
> was missing. I don't have the exact printout though.
> 
> Am I missing something here? I'm trying to build in an ubuntu trusty server 
> install, and it has worked before.
> 
> /Tomas
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP/How To Build The Sample Plugin

[Burt Silverman]

Oh, man, that (referring to my last post) is some tricky stuff. My reaction
reminds me of one of my colleagues reaction years ago when I created some
firmware that would only fit in flash by using an AIX C compiler
optimization trick that discarded uncalled functions. After I told him the
solution he required, he exclaimed loudly, "OH, I THINK IT STINKS." Now,
one of my issues, not the primary question, but the "stinks" issue, is that
there are at least two unique load_one_plugin functions that behave
differently but both show up in the log as "load_one_plugin."

OK, the function in vlib/unix/plugin.c will not accept my
vpp_api_test_plugins even though I have them in the plugin path I
configured in /etc/vpp/startup.conf, because they do not have section
vlib_plugin_registration in the ELF. I think there is a separate
vat_plugin_path that is hard coded to /usr/lib/vpp_api_test_plugins in
vpp/api/plugin.c. How can I configure this so that I can have these vat
plugins in
$TOP/build-root/install-vpp-native/vpp/lib64/vpp_api_test_plugins? As I
have mentioned earlier, I am trying to come up with a developer work flow
that does not require building and installing packages.

Burt

On Wed, May 31, 2017 at 3:56 PM, Burt Silverman  wrote:

> Damjan,
>
> I have a related question, but it does not involve the sample-plugin. I
> wish to "make build-release" and then adjust my plugin path in
> /etc/vpp/startup.conf to use the plugin directories underneath
> TOP/build-root/install-vpp-native/vpp/lib64. Well it seems that the
> plugins in directory vpp_plugins are acceptable, but the ones in
> vpp_api_test_plugins are not. I end up with a result like:
>
> [burt@localhost ~]$source ./vpp.sh
> [sudo] password for burt:
> vlib_plugin_early_init:356: plugin path /home/burt/vpp/build-root/
> install-vpp-native/vpp/lib64/vpp_plugins:/home/burt/vpp/
> build-root/install-vpp-native/vpp/lib64/vpp_api_test_plugins
> load_one_plugin:184: Loaded plugin: acl_plugin.so (Access Control Lists)
> load_one_plugin:83: Not a plugin: acl_test_plugin.so
> load_one_plugin:184: Loaded plugin: dpdk_plugin.so (Data Plane Development
> Kit (DPDK))
> load_one_plugin:83: Not a plugin: dpdk_test_plugin.so
> load_one_plugin:184: Loaded plugin: flowperpkt_plugin.so (Flow per Packet)
> load_one_plugin:83: Not a plugin: flowperpkt_test_plugin.so
> ...
> load_one_plugin:63: Loaded plugin: /usr/lib/vpp_api_test_plugins/
> acl_test_plugin.so
> load_one_plugin:63: Loaded plugin: /usr/lib/vpp_api_test_plugins/
> dpdk_test_plugin.so
> load_one_plugin:63: Loaded plugin: /usr/lib/vpp_api_test_plugins/
> flowperpkt_test_plugin.so
> load_one_plugin:63: Loaded plugin: /usr/lib/vpp_api_test_plugins/
> gtpu_test_plugin.so
> ...
> [but I want it to work without installing the vpp-plugins package]
>
> Can it be fixed easily? It seems that I cannot use the vppctl program
> ("show pci" for example) without the test plugins (or I am missing
> something else.)
>
> Thanks.
>
> Burt
>
> On Wed, May 31, 2017 at 12:31 PM, Damjan Marion (damarion) <
> damar...@cisco.com> wrote:
>
>> >
>> > On 31 May 2017, at 18:18, Kinsella, Ray  wrote:
>> >
>> >
>> > Ok - but that doesn't get us any closer to helping newbies use the
>> sample plugin with 'make build' and 'make run', right? They still need to
>> install vpp, then the sample-plugin - lots of hoops.
>>
>> make run is not built for running out-of-tree plugins but this should
>> work:
>>
>> make bootstrap
>> make pkg-deb
>> dpkg -i build-root/*.deb
>> cd src/examples/sample-plugin
>> autoreconf -fis
>> ./configure
>> make
>> sudo make install
>>
>> >
>> > I disagree with a documentation heavy approach in principle, the wiki
>> suggests, that it similarly goes 'out of sync' quiet quickly.
>> >
>> > BTW - I wasn't advocating PLUGIN_DISABLED, I provided build-data
>> configs in the same way we do enabling/disabling dpdk features.
>>
>> ok
>>
>> >
>> > The updated patch provides the separation between example/sample
>> plugins and plugins that was asked for. It re-uses all the same autotools
>> configs as src/plugins, so shouldn't go out of sync.
>>
>> i still disagree, sample-plugin should be stand-alone autotools project,
>> you are removing configure.ac so for me it is no-go.
>>
>> >
>> > Ray K
>> >
>> >
>> > On 31/05/2017 17:05, Damjan Marion (damarion) wrote:
>> >>
>> >> I do not agree with that proposal, I think we need to have one sample
>> of out-of-tree plugin as it is today.
>> >>
>> >> Still, I agree that we need to help newbies and my proposal is that we
>> just document build process for out-of-tree plugins with simple README.md
>> inside src/examples/sample-plugin.
>> >>
>> >> btw I consider use of PLUGIN_DISABLED (as default choice) as evil, as
>> it mens that plugin will go out of sync sooner or later.
>> >>
>> >>
>> >>> On 31 May 2017, at 17:37, Kinsella, Ray 
>> wrote:
>> >>>
>> >>>
>> >>> Ok, typically example/sample code is intended to be used by the
>> newest of the new, newbies. So the sample plugin should work with

Re: [vpp-dev] VPP Node Debug

[otroan]

Alessio,

you may start VPP with the unix {interactive} options too...
e.g. put that line in the configuration file pointed to by STARTUP_CONF 
environment variable (see make help).
then do "make run" or "make debug".

please let me know your success with the punt socket feature. it is a little 
experimental.

Best regards,
Ole

> On 1 Jun 2017, at 18:10, Alessio Silvestro  wrote:
> 
> I knew VPP run in user space and that printk is not the best option, however 
> from the documentation it is not clear to me how to do that.
> 
> For example now I inserted the command clib_warning("I am here!") in the node 
> I create -- that from vppctl show trace I can see processes the packets.
> 
> Where does it prints?
> 
> Still I cannot figure it out.
> 
> Thanks,
> Alessio
> 
> On Thu, Jun 1, 2017 at 6:00 PM, Luke, Chris  wrote:
> printk() is typically a kernel thing, no? This isn’t kernel code. 😊
> 
> 
> 
> If you just want stuff on the console when running in a debugger, or 
> interactively, clib_warning() may be what you are looking for.
> 
> 
> 
> Chris.
> 
> 
> 
> 
> 
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
> Behalf Of Alessio Silvestro
> Sent: Thursday, June 1, 2017 10:35
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] VPP Node Debug
> 
> 
> 
> Hi all,
> 
> 
> 
> I am using this code "https://gerrit.fd.io/r/#/c/6721/"; to in order to enable 
> an external process to receive UDP packets.
> 
> 
> 
> I tried to use printk -- including module.h in the c file.
> 
> 
> 
> When I compile VPP with:
> 
> 
> 
> TOPDIR/vpp make build-release
> 
> 
> 
> I got the following error
> 
> 
> 
> fatal error: linux/module.h: No such file or directory
> 
> compilation terminated.
> 
> 
> 
> Do you have any idea why?
> 
> 
> 
> Is there a better way to debug the code of a node in VPP?
> 
> 
> 
> Thanks,
> 
> Alessio
> 
> 
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev



signature.asc
Description: Message signed with OpenPGP
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] MPLS L3VPN PING FAILED

[薛欣颖]

Hi Neale,

These patches you upload have something conflict with the  master branch.I 
can't add all the patches.
Can I use' git clone https://gerrit.fd.io/r/vpp 'to get the vpp  code with your 
pathes?

Thanks,
xyxue


 
From: Neale Ranns (nranns)
Date: 2017-05-31 18:09
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
 
The MPLS config works for me with:
  DBGvpp# sh version
   vpp v17.07-rc0~314-g79ea7ec built by vagrant on localhost at Wed May 31 
00:46:42 PDT 2017
which is master branch from a few hours ago.
 
Regards,
neale
 
Packet 1
 
00:09:02:603978: af-packet-input
  af_packet: hw_if_index 1 next-index 4
tpacket2_hdr:
  status 0x2001 len 98 snaplen 98 mac 66 net 80
  sec 0x592e95b3 nsec 0x8466a6e vlan 0 vlan_tpid 0
00:09:02:604038: ethernet-input
  IP4: 3a:4c:48:ed:59:c3 -> 02:fe:1a:e1:c5:4c
00:09:02:604054: ip4-input
  ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x1c3e
00:09:02:604062: ip4-lookup
  fib 1 dpo-idx 3 flow hash: 0x
  ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x1c3e
00:09:02:604072: ip4-mpls-label-imposition
mpls-header:[33:63:0:eos]
00:09:02:604081: mpls-midchain
  adj-idx 5 : mpls via 0.0.0.0  mpls-tunnel0: 
  stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] 
via:[43:3784]]
  [0] [@6]: mpls-label:[1]:[34:255:0:neos]
  [@1]: mpls via 2.1.1.2 host-vcore-link-1: 
02feb30a3b6f02fe4eafc6638847 flow hash: 0x
  
00:09:02:604088: adj-midchain-tx
  adj-midchain:[5]:mpls via 0.0.0.0  mpls-tunnel0: 
  stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] 
via:[43:3784]]
  [0] [@6]: mpls-label:[1]:[34:255:0:neos]
  [@1]: mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
00:09:02:604096: mpls-label-imposition
mpls-header:[34:255:0:neos]
00:09:02:604100: mpls-output
  adj-idx 4 : mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847 
flow hash: 0x
  : 
  0020: 
00:09:02:604102: host-vcore-link-1-output
  host-vcore-link-1
  MPLS: 02:fe:4e:af:c6:63 -> 02:fe:b3:0a:3b:6f
  label 34 exp 0, s 0, ttl 255
 
Packet 2
 
00:09:02:604968: af-packet-input
  af_packet: hw_if_index 2 next-index 4
tpacket2_hdr:
  status 0x2001 len 106 snaplen 106 mac 66 net 80
  sec 0x592e95b3 nsec 0x84c97da vlan 0 vlan_tpid 0
00:09:02:604978: ethernet-input
  MPLS: 02:fe:b3:0a:3b:6f -> 02:fe:4e:af:c6:63
00:09:02:604987: mpls-input
  MPLS: next mpls-lookup[1]  label 1024 ttl 255
00:09:02:604993: mpls-lookup
  MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0
00:09:02:605000: lookup-mpls-dst
 fib-index:0 hdr:[1023:63:0:eos] load-balance:33
00:09:02:605005: ip4-mpls-label-disposition
  disp:0
00:09:02:605008: lookup-ip4-dst
 fib-index:1 addr:192.168.2.20 load-balance:35
00:09:02:605014: ip4-rewrite
  tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.2.20 host-vce-link-1: 
3a4c48ed59c302fe1ae1c54c0800 flow hash: 0x
  : 3a4c48ed59c302fe1ae1c54c08004554e9fd3e010c33c0a80314c0a8
  0020: 0214243e07d20010b3952e59311e02001011
00:09:02:605018: host-vce-link-1-output
  host-vce-link-1
  IP4: 02:fe:1a:e1:c5:4c -> 3a:4c:48:ed:59:c3
  ICMP: 192.168.3.20 -> 192.168.2.20
tos 0x00, ttl 62, length 84, checksum 0x0c33
fragment id 0xe9fd
  ICMP echo_reply checksum 0x243e
 
 
 
 
 
 
 
From: 薛欣颖 
Date: Wednesday, 31 May 2017 at 08:40
To: "Neale Ranns (nranns)" , vpp-dev 
Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED
 
Hi Neale,
 
The configuration without MPLS:
    
 ###VPP1 
create host-interface name eth0
create host-interface name eth1
set interface ip table host-eth1 0
set interface ip table host-eth0 1
set interface mac address host-eth0 00:03:7F:FF:FF:FF
set interface mac address host-eth1 00:03:7F:FF:FF:FE
set int ip address host-eth0 192.168.3.1/24
set int ip address host-eth1 2.1.1.1/24
ip route add 192.168.2.0/24 via 2.1.1.2

    
 VPP2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface mac address host-eth0 00:50:43:00:02:02
set interface mac address host-eth1 0E:1A:0D:00:50:43
set int ip address host-eth0 192.168.2.1/24
set int ip address host-eth1 2.1.1.2/24
ip route add 192.168.3.0/24  via 2.1.1.1


The configuration with MPLS:
   
 PE1  
 
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
set interface ip table host-eth1 0
set interfa

Re: [vpp-dev] Build failures on master

[Tomas Brännström]

No it's the same :-(

One thing though: when I get these errors I clone from a fork of the vpp
repo that we made. Is there some kind of git-hook that creates these
version files/update the .deb files with a version when cloning from the
main vpp gerrit repository, that might not fire when cloning from a fork?

/Tomas

On 1 June 2017 at 19:02, Florin Coras  wrote:

> Hi Tomas,
>
> That sure is weird.
>
> (backup everything that’s not in git)
> git clean -fdx
> make bootstrap
> make build
>
> Do you still see the issue?
>
> HTH,
> Florin
>
> On Jun 1, 2017, at 6:18 AM, Tomas Brännström 
> wrote:
>
> Hi
> I'm getting build errors when trying to build a recent commit on the
> master branch:
>
> /home/ubuntu/git/vpp/build-data/../src/vnet/tcp/builtin_client.c:25:29:
> fatal error: vpp/app/version.h: No such file or directory
>  #include 
>  ^
> compilation terminated.
>
> I'm building using the "extras/vagrant/build.sh" script (or
> "build-root/vagrant/build.sh" in slightly earlier versions). What's strange
> here is that I built it successfully on the exact same commit yesterday on
> another machine. The commit in question is 
> 79ea7ec3b3c04d334a21107818c64d70c42b99ae
> but I tried on the latest master as well.
>
> Also, I tried to build an earlier version (git tag v17.07-rc0) and got
> another error, where the .deb files could not be built  because the
> "version" was missing. I don't have the exact printout though.
>
> Am I missing something here? I'm trying to build in an ubuntu trusty
> server install, and it has worked before.
>
> /Tomas
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev