[vpp-dev] one question IP checksum

[Zhang Yuwei]

Hi Guys and VPP maintainers,
 When I run VPP in vxlan scenario, I found that when VPP receive a 
vxlan packets, after decapsulation, the packet will go into ip-input node 
instead of ip-input-nochecksum which means vpp will re-calculate the checksum 
and verify it. I think the outer UDP checksum has already include the inner 
packet as payload, so can we skip the ip header checksum calculation for inner 
ip header? This part is done by software which will cause some CPU cycles 
consumption and I tried if skip the checksum calculation it will have a obvious 
performance gain. Can anybody give me some instructions? Thanks a lot for your 
kindly help.

Regards,
Yuwei

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10873): https://lists.fd.io/g/vpp-dev/message/10873
Mute This Topic: https://lists.fd.io/mt/27412224/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Question about VPP plugin/node's life cycle

[Rui Cai via Lists.Fd.Io]

Hello vpp experts:

I'm trying to figure out a plugin/node's life cycle with in VPP process. There 
is very rich code/documentation talking about plugin 
registration/initialization and node registration. I understand that nodes are 
created during node graph build up and during plugin init function I can 
further manipulate the edges of my nodes. However, I'm having trouble finding 
the code that handles node tear down/plugin un-initialization. Does VPP have a 
notion of plugin/node un-initialization? For example, if my plugin allocated 
some object during init, I would expect to free it in un-init. If there is such 
concept, what should I search to find them? Or pretty much the node/plugin 
lives as long as the VPP process is running and the plugin/node life cycle is 
never going to be shorter than VPP process?

Thanks a lot!
-Ray
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10872): https://lists.fd.io/g/vpp-dev/message/10872
Mute This Topic: https://lists.fd.io/mt/27411530/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] ipsec transport mode support over vxlan tunnels

[Vijayabhaskar Katamreddy via Lists.Fd.Io]

Hi,

Are there any issues configuring ipsec tunnels over VXLAN tunnels with VPP..
I see that the current cli commands doesn’t support this way.. but are there 
any limitations in general?

Thanks
--Vijay
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10871): https://lists.fd.io/g/vpp-dev/message/10871
Mute This Topic: https://lists.fd.io/mt/27406663/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Problem downloading always VPP 19.01 instead of VPP 18.07

[Edward Warnicke]

Perhaps a bit of an explanation about how the repos are organized might
help:

https://packagecloud.io/fdio/release - Only released packages.  The latest
in there should be 18.07.1 (at least until 18.10 releases soon!)

https://packagecloud.io/fdio/1807 - the throttle branch for 1807 packages.
Not a lot interesting here any more, https://packagecloud.io/fdio/1810 is
the throttle for the upcoming 1810 release, much more fun :)

https://packagecloud.io/fdio/master - follows the master branch, merge by
merge.  That should be the only repo with 19.01-rc0 packages in it at this
time.

Is it possible you were pulling from fdio/master ?

Ed

On Thu, Oct 18, 2018 at 7:06 AM Francesco Spinelli <
francescospinell...@live.it> wrote:

> Hello VPP experts,
>
> I'm trying to download VPP version 18.07  but when I build it and run it,
> I notice that both VPP and the packages belong always to the 19.01 version
>
> It happens if I download them from here
> , using the command:
>
> curl -s https://packagecloud.io/install/repositories/fdio/1807/script.deb.sh 
> | sudo bash
>
>
> and when I pull VPP from gerrit:
>
> git clone https://gerrit.fd.io/r/vpp
>
>
> and then buidling it.
>
> Am I missing anything in my buildling process? How can I retrieve  18.07
> packages and avoid to use the  most recent ones?
>
> Thanks a lot for your help,
> Best Regards,
>
> Francesco
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10868): https://lists.fd.io/g/vpp-dev/message/10868
> Mute This Topic: https://lists.fd.io/mt/27401834/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10870): https://lists.fd.io/g/vpp-dev/message/10870
Mute This Topic: https://lists.fd.io/mt/27401834/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Problem downloading always VPP 19.01 instead of VPP 18.07

[Marco Varlese]

If you want to build the sources yourself then - once you have cloned the VPP
repo - you will have to checkout the correct branch for the version you're
interested in. If you simply clone the repo then the "default" branch is master
which is correctly pointing to 19.01-rc0...
If you want to checkout and eventually build v18.07.1 then do:# git checkout
v18.07.1
That will checkout the 18.07 branch at the tag 18.07.1
Once you've done that... well, it's a matter of building and running VPP.

- Marco
On Thu, 2018-10-18 at 12:05 +, Francesco Spinelli wrote:
> 
> Hello VPP experts,
> 
> 
> 
> 
> 
> I'm trying to download VPP version 18.07  but when I build it and run it, I
> notice that both VPP and the packages belong always to the 19.01 version
> 
> 
> 
> 
> 
> It happens if I download them from here, using the command: 
> 
> curl -s https://packagecloud.io/install/repositories/fdio/1807/script.deb.sh |
> sudo bash
> 
> 
> 
> 
> and when I pull VPP from gerrit:
> 
> 
> 
> 
> 
> git clone https://gerrit.fd.io/r/vpp
> 
> 
> and then buidling it.
> 
> 
> 
> 
> 
> Am I missing anything in my buildling process? How can I retrieve  18.07
> packages and avoid to use the  most recent ones?
> 
> 
> 
> 
> 
> Thanks a lot for your help,
> 
> Best Regards,
> 
> 
> 
> 
> 
> Francesco 
> 
> 
> 
> 
> 
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-Links: You receive all messages sent to this group.
> View/Reply Online (#10868): https://lists.fd.io/g/vpp-dev/message/10868Mute
> This Topic: https://lists.fd.io/mt/27401834/675056Group Owner: vpp-
> dev+ow...@lists.fd.ioUnsubscribe: https://lists.fd.io/g/vpp-dev/unsubb  [mvarl
> e...@suse.de]-=-=-=-=-=-=-=-=-=-=-=-
-- 
Marco V


SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10869): https://lists.fd.io/g/vpp-dev/message/10869
Mute This Topic: https://lists.fd.io/mt/27401834/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Unable to build router plugin

[Dave Barach via Lists.Fd.Io]

#include  and try again?

-Original Message-
From: vpp-dev@lists.fd.io  On Behalf Of carlito nueno
Sent: Wednesday, October 17, 2018 11:16 PM
To: hongjun...@intel.com
Cc: Mehran Memarnejad ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Unable to build router plugin

Hi Hongjun,

Thanks for the patch.
I tried to compile VPPSB project with the latest master and latest VPP
stable/1810 but I am getting this error:

 Building router in /vpp/build-root/build-vpp_debug-native/router 
make[1]: Entering directory '/vpp/build-root/build-vpp_debug-native/router'
  CC   router/tap_inject.lo
  CC   router/tap_inject_netlink.lo
  CC   router/tap_inject_node.lo
  CC   router/tap_inject_tap.lo
/vpp/build-data/../router/router/tap_inject_node.c: In function
‘tap_inject_tap_send_buffer’:
/vpp/build-data/../router/router/tap_inject_node.c:45:13: error:
implicit declaration of function ‘writev’; did you mean ‘write’?
[-Werror=implicit-function-declaration]
   n_bytes = writev (fd, , 1);
 ^~
 write
/vpp/build-data/../router/router/tap_inject_node.c: In function ‘tap_rx’:
/vpp/build-data/../router/router/tap_inject_node.c:231:13: error:
implicit declaration of function ‘readv’; did you mean ‘read’?
[-Werror=implicit-function-declaration]
   n_bytes = readv (fd, iov, MTU_BUFFERS);
 ^
 read
cc1: all warnings being treated as errors
Makefile:483: recipe for target 'router/tap_inject_node.lo' failed
make[1]: *** [router/tap_inject_node.lo] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory '/vpp/build-root/build-vpp_debug-native/router'
Makefile:691: recipe for target 'router-build' failed
make: *** [router-build] Error 2

Thanks
On Sun, Oct 7, 2018 at 7:25 PM Ni, Hongjun  wrote:
>
> Hi guys,
>
> I have submitted a patch to fix the build issue in VPPSB project:
> https://gerrit.fd.io/r/#/c/15135/ Fix build issue due to vpp's 
> function parameters change I have tested it and it works well in my server.
>
> Thanks,
> Hongjun
>
> -Original Message-
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of 
> carlito nueno
> Sent: Friday, September 28, 2018 9:45 AM
> To: memarnejad...@gmail.com
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Unable to build router plugin
>
> Thanks for the tip Mehran. I will take a look and report back.
> On Thu, Sep 27, 2018 at 12:16 AM Mehran Memarnejad  
> wrote:
> >
> > Hi carlito,
> >
> > I've had problems muck like yours. Sometimes VPP updates its functions 
> > while vppsb is still the same, so you need to change it to make it work.
> > In my problem I just updated the vppsb's outdated function to the new one 
> > and it worked.
> > As you know, vppsb is a plugin for vpp and it calls vpp's functions, 
> > so any change in vpp's function affects vppsb e.g. function 
> > singnature change
> >
> >
> > On Thursday, September 27, 2018, carlito nueno  
> > wrote:
> >>
> >> Hi all,
> >>
> >> I am trying to build the router-plugin:
> >> make V=0 PLATFORM=vpp TAG=vpp_debug install-deb netlink-install 
> >> router-install
> >>
> >> I am using the Vagrantfile present in vpp repo and am pulling the 
> >> current master (as of September 26 2018). I am also pulling the 
> >> current master of vppsb.
> >>
> >> But I am getting this error:
> >>
> >>  Building router in 
> >> /vpp/build-root/build-vpp_debug-native/router
> >> 
> >> make[1]: Entering directory '/vpp/build-root/build-vpp_debug-native/router'
> >>   CC   router/tap_inject.lo
> >>   CC   router/tap_inject_netlink.lo
> >> /vpp/build-data/../router/router/tap_inject_netlink.c: In function
> >> ‘add_del_neigh’:
> >> /vpp/build-data/../router/router/tap_inject_netlink.c:140:9: error:
> >> too many arguments to function ‘vnet_unset_ip6_ethernet_neighbor’
> >>  vnet_unset_ip6_ethernet_neighbor (vm, sw_if_index,
> >>  ^~~~ In file included from
> >> /vpp/build-data/../router/router/tap_inject_netlink.c:19:0:
> >> /vpp/build-root/install-vpp_debug-native/vpp/include/vnet/ip/ip6_neighbor.h:84:12:
> >> note: declared here
> >>  extern int vnet_unset_ip6_ethernet_neighbor (vlib_main_t * vm,
> >> ^~~~
> >> Makefile:483: recipe for target 'router/tap_inject_netlink.lo' 
> >> failed
> >> make[1]: *** [router/tap_inject_netlink.lo] Error 1
> >> make[1]: *** Waiting for unfinished jobs
> >> make[1]: Leaving directory '/vpp/build-root/build-vpp_debug-native/router'
> >> Makefile:691: recipe for target 'router-build' failed
> >> make: *** [router-build] Error 2
> >>
> >> Any advice?
> >>
> >> Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10867): https://lists.fd.io/g/vpp-dev/message/10867
Mute This Topic: https://lists.fd.io/mt/26280661/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]

Re: [vpp-dev] Packet error-drop with fragmented packets through NAT #vpp_stability

[Ole Troan]

Hi there,

Would you be able to enable packet tracing in VPP and post that?

Cheers,
Ole

> On 18 Oct 2018, at 10:12, JB  wrote:
> 
> Hello,
> 
> We've got a NAT44 setup configured with separate local and outside linknets, 
> where the internal NAT pool resides on a different subnet and is translated 
> to an outside different subnet.
> 
> When sending, in this case ICMP packets of size 1500 bytes, to 8.8.8.8 we get 
> no response back from the target. However, if we decrease size to 1472, it 
> works. 1500 is including headers (total packet size is 1500).
> 
> When sending packets of size 1500 towards 8.8.8.8, the initial returning 
> packet is 1468 and marked as fragmented with more fragments to come.
> When sending packets of size 1472 towards 8.8.8.8 all the returning packets 
> are of size 1472
> 
> The result of sending packets of size 1500 towards 8.8.8.8 is that we get 
> them back fragmented, and for some reason, not received correctly by the 
> internal device, whether not passed through out2in properly or not 
> reassembled properly.
> 
> Please feel free to attempt reproducing the above and let me know if you need 
> more info. Any thoughts? -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#10864): https://lists.fd.io/g/vpp-dev/message/10864
> Mute This Topic: https://lists.fd.io/mt/27400627/675193
> Mute #vpp_stability: 
> https://lists.fd.io/mk?hashtag=vpp_stability=1480722
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [otr...@employees.org]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10865): https://lists.fd.io/g/vpp-dev/message/10865
Mute This Topic: https://lists.fd.io/mt/27400627/21656
Mute #vpp_stability: https://lists.fd.io/mk?hashtag=vpp_stability=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Packet error-drop with fragmented packets through NAT #vpp_stability

[JB]

Hello,

We've got a NAT44 setup configured with separate local and outside linknets, 
where the internal NAT pool resides on a different subnet and is translated to 
an outside different subnet.

When sending, in this case ICMP packets of size 1500 bytes, to 8.8.8.8 we get 
no response back from the target. However, if we decrease size to 1472, it 
works. 1500 is including headers (total packet size is 1500).

When sending packets of size 1500 towards 8.8.8.8, the initial returning packet 
is 1468 and marked as fragmented with more fragments to come.
When sending packets of size 1472 towards 8.8.8.8 all the returning packets are 
of size 1472

The result of sending packets of size 1500 towards 8.8.8.8 is that we get them 
back fragmented, and for some reason, not received correctly by the internal 
device, whether not passed through out2in properly or not reassembled properly.

Please feel free to attempt reproducing the above and let me know if you need 
more info. Any thoughts?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10864): https://lists.fd.io/g/vpp-dev/message/10864
Mute This Topic: https://lists.fd.io/mt/27400627/21656
Mute #vpp_stability: https://lists.fd.io/mk?hashtag=vpp_stability=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-