Hi Dave,
Thanks for the patch. I merged your edits and compiled a debug version
using stable/1908 as base.
Every time a make a ping request from a LAN device, VPP is restarting.
Sometimes vppctl just hangs, but when I do get into vppctl, if I run a
command (ex: sh nat44 address), VPP again
Hi Dave,
It worked! Really appreciate the help :)
I learned a lot about git, never new about the bare feature.
On Fri, Aug 16, 2019 at 5:11 AM Dave Barach (dbarach) wrote:
>
> That setup will cause no end of pain if your git chops aren't up to it. I
> guess you've already discovered that. If
> UDPI will be easily misunderstood as UDP+I.
> uniDPI is ok?
+1 to uniDPI.
Vratko.
From: 李幸福(Xingfu Li)
Sent: Tuesday, August 13, 2019 12:45
To: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco); Ni, Hongjun;
Alexey; t...@lists.fd.io
Cc:
uniDPI is ok?
UDPI will be easily misunderstood as UDP+I.
李幸福/Xingfu Li
山东华辰泰尔信息科技股份有限公司/Shandong Huachentel Information Technology Co., Ltd.
山东省济南市高新区舜泰广场8号楼西区17层 250101/West of F17, Building 8 of Shuntai Square,
High-tech Zone, Jinan, China 250101
电话/Tel：86-531-62325307 86-531-88877658-8019
Hi Bin & Neale,
I know this exchange is a couple of years old now, but I'm having the exact
issue where the Ping reply from VPP is being sent in cleartext rather than
going through the IPSec tunnel. Could you provide some information on how this
was resolved?
Thanks in advance.
Dom
Please submit a patch.
From: vpp-dev@lists.fd.io On Behalf Of ??
Sent: Friday, August 16, 2019 8:19 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Pcap trace doesn't work while using a seperate worker thread
instead of main
Dear Developers:
If I use just one thread for configure and packet
Dear Developers:
If I use just one thread for configure and packet processing. The pcap trace
module works well.
But If I use two CPU cores, one for main(config) and another for packet
processing, Pcap fails to capture any packet.
After using gdb to debug this problem, I think I found the
That setup will cause no end of pain if your git chops aren't up to it. I guess
you've already discovered that. If you do things in a more normal way, you
won't have to add tags or argue with the build system.
A more straightforward way to work - which I use myself - goes like so:
Create a
> On Aug 13, 2019, at 6:34 AM, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES
> at Cisco) via Lists.Fd.Io wrote:
>
> >> uDPI
>
> > microDPI
>
> Universal Deep Packet Inspection is the new project here.
> Would it make sense to use UDPI as its abbreviation
> (e.g. capital U, to distinguish
Hi Carlito,
You almost certainly want them in the same table.
As I said, if you do this:
ping 8.8.8.8 source wan1
then the ping packet will be constructed with a source address from wan1, but
it will still follow your routing config for transmission. This means that if
you have:
ip
when i use 19.04 version, there's a stats.sock in /run/vpp director,
when i use 18.10 version, there's no stats.sock in the same director.but i see
the stats.sock init codes is exsit.
how can i get /run/vpp/stats.sock in 18.10 version ? thansk
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
11 matches
Mail list logo
