Hi Elias,
There is a slightly different underlying cause. Fixed in
https://gerrit.fd.io/r/c/vpp/+/22453
I will get that to 19.08 asap.
The root cause was essentially that I had forgotten the memory layout I made
for simple counters in the stat segment.
Cheers
Ole
> On 4 Oct 2019, at 08
Hi,
Yes containers usually do not update /dev after creation, so any device that
shows up dynamically afterwards won't be available by default. Note this is not
specific to VPP. To access PCI devices from userspaces you'll need access to
either /dev/vfio/* or /dev/uio* device nodes depending of
https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/installing/index.html#installing-on-ubuntu
^^^
Thats just an example, get the "Sorry this page does not exist yet" ascii art.
Am I doing it wrong?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online
Well I was and I wasn't.
Found the "we have moved" page when on the home page. I think some clean up is
needed.
Here is what happens:
- I google for "vpp read the docs" or some such and get to:
https://fdio-vpp.readthedocs.io/en/latest/
- this presents me with what appears to be a normal docum
Hi Elias,
>
> I was just chasing a strange error that turned out to be related to
> some code in src/vpp/stats/stat_segment.c where something went wrong
> regarding statistics vectors for different threads (some kind of memory
> corruption that ended up causing an infinite loop inside dlmalloc.c)
Funny about the timing of Jon's query -- I ran into something similar at
around the same time:
I wanted to set up Docker on Windows 10, with Linux containers, and then
run "make test" (following a clone of the git repository.)
My guess is that this is either impossible, or it requires extra trick
Hi Burt,
That should be different: make test relies on packet-generator and not on any
hardware NIC.
However:
1) Linux containers on W10 are using a syscall translation which does not
support all Linux syscalls by far. I'll be surprised if VPP works there (that
might change with WSL2 when it b
Thanks, Ben, I managed to conflate different issues -- I should try HyperV
as per your suggestion.
Burt
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14121): https://lists.fd.io/g/vpp-dev/message/14121
Mute This Topic: https://lists.fd.io/mt/34386
Hi Chuan,
Please remove the SPD config. For tunnels all packets that ingress/egress the
tunnel are decrypted/encrypted, so no policy is required. The presence of the
SPD on the ingress eth0 link could be why it’s not working.
Please provide packet traces when you are reporting packet loss probl
Thanks for helping.
I removed spd configs on both sides, but still no luck. I am pinging from
r230 side.
It seems r230 is able to sending ping pkts over dpdk interface. However, on
r740 side, gre0 interface drops all of them. See the attached updated cfg
files and log files for more details.
I
Hi,
I want to use 256 bit crypto algorithm in my ipsec config.
I have something like this:
ipsec sa add 1 spi 255128 esp tunnel-src 10.10.10.10 tunnel-dst 10.10.10.11
crypto-key 2b7e151628aed2a6abf7158809cf4f3d crypto-alg aes-cbc-256
integ-key 6867666568676665686766656867666568676669 integ-alg sh
Double your key length. Probably better to switch to GCM (aes-gcm-256) and drop
the separate integrity algorithm too.
Thanks,
Chris.
> On Oct 4, 2019, at 7:23 PM, Chuan Han via Lists.Fd.Io
> wrote:
>
> Hi,
>
> I want to use 256 bit crypto algorithm in my ipsec config.
>
> I have something l
12 matches
Mail list logo
