I’m sure there is, but it’s not a very squeaky wheel.
Also, patches welcome. :) Best way to get familiar with the code is to get up
to your elbows in it!
Cheers,
Chris.
From: Matt Paska [mailto:mattjpa...@gmail.com]
Sent: Friday, October 13, 2017 18:51
To: Florin Coras
Cc: Luke, Chris ; Matus
I think this should about cover the situation... (😉)... HTH... Dave
void
vl_msg_api_config (vl_msg_api_msg_config_t * c)
{
api_main_t *am = &api_main;
/*
* This happens during the java core tests if the message
* dictionary is missing newly added xxx_reply_t messages.
* Should never
I understand, thanks! I just mean in general if there wasn't interest in
Syslog in SNAT. Looking back the thread, I chimed in June about it being
included 17.07. I'm not too familiar with the SNAT codebase myself to help
directly so I'm trying to figure out if there is possibility for the
future.
Indeed!
Florin
> On Oct 13, 2017, at 3:31 PM, Luke, Chris wrote:
>
> The release stable branch was forked several weeks ago; at this point it the
> release only accepts bug fixes.
>
> Chris.
>
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Matt Pas
The release stable branch was forked several weeks ago; at this point it the
release only accepts bug fixes.
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Matt Paska
Sent: Friday, October 13, 2017 17:11
To: Matus Fabian -X (matfabia - PANTHEON TECHNO
Thanks for the info. Is there not enough interest to warrant being included?
On Thu, Oct 12, 2017 at 9:26 PM, Matus Fabian -X (matfabia - PANTHEON
TECHNOLOGIES at Cisco) wrote:
> Syslog in NAT plugin is not a part of 17.10 release.
>
>
>
> Matus
>
>
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [m
Yes, I did. I just worked it out myself... Thanks… Dave
From: Ole Troan (otroan)
Sent: Friday, October 13, 2017 1:48 PM
To: Ole Troan (otroan)
Cc: Dave Barach (dbarach) ; Ole Troan
; vpp-dev@lists.fd.io
Subject: Re: jvpp core future test failure (gerrit 8743)
s/map/dns
if you were to cut and
s/map/dns
if you were to cut and paste.
#define vl_msg_name_crc_list
#include
#undef vl_msg_name_crc_list
static void
setup_message_id_table (api_main_t * am)
{
#define _(id,n,crc) vl_msg_api_add_msg_name_crc (am, #n "_" #crc, id);
foreach_vl_msg_name_crc_dns;
#undef _
}
Ole
On 13 Oct 2017
Hi,
Are there cases where unsigned __int128 can be used instead of u32x4 or
similar-width vector.h type abstraction for code that does plain C-style
bitwise/arith ops or assignments?
Thanks,
Brian
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also b
Dear Dave,
I wonder if you forgot to hookup the messages in the CRC dictionary?
#define vl_msg_name_crc_list
#include
#undef vl_msg_name_crc_list
static void
setup_message_id_table (api_main_t * am)
{
#define _(id,n,crc) vl_msg_api_add_msg_name_crc (am, #n "_" #crc, id);
foreach_vl_msg_name_c
Dear Ole,
See https://gerrit.fd.io/r/#/c/8743. It turns out that the java core future
"make test" test fails as shown below.
The patch adds three xxx_reply_t binary api messages. See
.../src/vnet/dns/dns.api.
It sure looks like the Java code knows about them, but isn't doing a very good
job o
Hi All,
I was trying to get mellanox NIC ConnectX-4 working with VPP on Cavium's
aarch64 SoC. After applying patch https://gerrit.fd.io/r/#/c/8390/ on top of
v1710-rc2 and with some local changes I am able to compile VPP successfully.
One of the compilation issue I faced was with
dpdk/dpdk-17
Hi,
Will vhash and pfhash continue to be unused?
Which hash is used the most often?
Thanks,
Brian
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not
Hi all,
Why there is no vlan l2 forward, only bridge forward ?
Regards,
Ewan
yug...@telincn.com
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Hello,
We see that IPv6 Neighbor solicitation messages sent by VPP are
having Ethernet Destination MAC address as FF:FF:FF:FF:FF:FF - Broadcast
MAC.
Aren't IPv6 Neighbor solicitation messages supposed to have
destination MAC as - 33:33:FF:?
VPP sent NS messages:
14:23:13.721695 88:a2:5
15 matches
Mail list logo
