Re: [vpp-dev] RAW IP VIA VPP

> On 29 May 2019, at 08:12, amitmulay...@gmail.com wrote: > > Hi guys > i have an issue that i want to consulte. > > VPP as we know dosent "support" usb devices meaning that if i have a wwan0 > port the vpp will not take it > if i wanted to connect it to vpp the way was via tap in the vpp tha

[vpp-dev] gerrit

If people didn’t notice, after gerrit upgrade yesterday, there is new UI available. There is switch at the bottom right… Nice thing about it, it doesn’t show FD.io logo over the half of the page. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/R

[vpp-dev] VPP 19.04.1 Maintenance Release starts today

Folks, As announced at the last 2 VPP community meetings, today I'll be starting the VPP 19.04.1 Maintenance Release at 1800UTC. Currently there are no patches in stable/1904 that are not merged.  Please unicast me if you have a fix that needs to be included in this maintenance release. Th

Re: [vpp-dev] RFC: IPSec Tunnel remodel

Hi Neale, Sure, it sounds ok. If I end up having trouble integrating with the new APIs I can revisit the issue and figure out if there's some enhancement needed at that point. Thanks, -Matt On Mon, May 27, 2019 at 7:01 AM Neale Ranns (nranns) wrote: > > > Hi Matt, > > > > I’m glad the change

[vpp-dev] Periodic processes should be started on demand when practicable

Folks, We've accumulated quite a number of periodic processes which start whether or not the related feature will [ever] be used. See below. It's quite easy to switch to on-demand process creation. See https://gerrit.fd.io/r/#/c/19878 for a complete example. Here's a sketch of how to start a p

[vpp-dev] vpp received signal SIGSEGV, PC 0x7fe54936bc40, faulting address 0x0

When i install a vpp stable/1810 on an ubuntu server 1604 successfully, but, vpp service does not start. I executed `*/usr/bin/vpp -c /etc/vpp/startup.conf*` command to see the error: ... load_one_plugin:189: Loaded plugin: tlsopenssl_plugin.so (openssl based TLS Engine) load_one_plugin:117: Plugi

Re: [vpp-dev] VPP crashes using bvi interface

Yes we need the bvi part for routing.Following is journalctl -xe when vpp crashes:May 24 05:51:57 localhost.localdomain sudo[40264]: pam_unix(sudo:session): session opened for user root by root(uid=0)May 24 05:51:57 localhost.localdomain sudo[40264]: pam_unix(sudo:session): session closed for user

[vpp-dev] Policer: How to get multiple buckets of same policy

Respected people, What is the correct procedure to use Policer in VPP? I want to limit bandwidth to 4Mbps for each connection. Using steps below I can assign 4Mbps to the combined traffic, instead of separate 4Mbps for each pppoe connection. I made a policy to limit bandwidth. Then added 2 rule

[vpp-dev] Messages stuck in the vpp-dev list moderation queue

Folks, Please note that list postings by non-list-members end up in an email moderation queue. Because 90+% of the emails in the moderation queue are spam / phish garbage, I tend not to look at the moderation queue very often. To ensure timely posting, please join the list. You can disable mes

Re: [vpp-dev] VPP 19.04.1 Maintenance Release starts today

Starting VPP 19.04.1 Maintenance Release now. VPP Committers, Please do not merge any patches into stable/1904 until after the VPP 19.04.1 is complete. Thanks, -daw- "Your Friendly VPP 19.04 Release Manager" On 5/29/2019 8:59 AM, Dave Wallace via Lists.Fd.Io wrote: Folks, As announced at th

Re: [vpp-dev] vpp received signal SIGSEGV, PC 0x7fe54936bc40, faulting address 0x0

Clueless with useless tracebacks. Please hook up gdb and get the complete human-readable backtrace. Steven From: on behalf of Mostafa Salari Date: Wednesday, May 29, 2019 at 10:24 AM To: "vpp-dev@lists.fd.io" Subject: [vpp-dev] vpp received signal SIGSEGV, PC 0x7fe54936bc40, faulting address

Re: [vpp-dev] FD.io Maintenance: 2019-05-28 @ 1700 UTC (10:00am PDT) - 2100 UTC (2:00pm PDT)

The issues with the NSH_SFC and CICN jobs is resolved. These issues were not due to the upgrade, they just happened to be discovered during testing. The jobs that weren't being configured properly in Jenkins were jobs that use {stream} and not {os} but were using the os-parameter to set the node t