[vpp-dev] No joy: ping6 gerrit.fd.io

[Dave Barach (dbarach)]

It looks like gerrit.fd.io has dropped off the ipv6 radar screen. Appears not 
to be a DNS problem or other problem on my end:

$ ping6 gerrit.fd.io
PING gerrit.fd.io(2604:e100:1:0:f816:3eff:fe7e:8731) 56 data bytes
^C
--- gerrit.fd.io ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms

$ ping6 www.google.com
PING www.google.com(iad30s07-in-x04.1e100.net) 56 data bytes
64 bytes from iad30s07-in-x04.1e100.net: icmp_seq=1 ttl=49 time=33.4 ms
64 bytes from iad30s07-in-x04.1e100.net: icmp_seq=2 ttl=49 time=30.4 ms
^C
--- www.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 30.413/31.943/33.473/1.530 ms

Please investigate AYEC.

Thanks... Dave

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Test job maybe not working correctly

[Dave Wallace]

Matt,

Thanks for pointing this out.  There appears to be a bug in 
ci-management/jjb/vpp/vpp.yaml, where the node type is specified as 
'ubuntu-s' instead of an os node (e.g. '{os}-basebuild-8c-32g').


- %< -
- job-template:
    name: 'vpp-test-poc-verify-{stream}-{os}'

    project-type: freestyle
    node: 'ubuntu-s'
- %< -

@Ed, is this a bug or intentional (for testing purposes only)?

Thanks,
-daw-

On 10/16/2017 11:33 AM, Matthew Smith wrote:


Hi,

After submitting a rebased patch set this morning, I went and looked 
at the console output of one of the jenkins jobs that kicked off 
automatically. The job was named vpp-test-poc-verify-master-centos7. 
It caught my eye that the name of the job implies that it should be 
running on CentOS 7 but the console output showed that it was building 
deb packages. Here’s the full console log for that build:


https://jenkins.fd.io/job/vpp-test-poc-verify-master-centos7/255/consoleFull

Is something broken there? This seemed a little suspect to me, but I 
don’t have a full understanding of what each jenkins job is supposed 
to be doing or how they’re supposed to run.


Thanks,
-Matt Smith



___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] SNAT hash tables

[Yuliang Li]

Get it. It use spinlock (in vppinfra/bihash_template.c):

while (__sync_lock_test_and_set (h->writer_lock, 1))

On Mon, Oct 16, 2017 at 11:39 AM, Yuliang Li  wrote:

> Hi all,
>
> I am curious in the SNAT implementation. I see that SNAT's hash tables
>  are shared by all
> worker threads. Does SNAT use lock to avoid multiple threads updating the
> hash table concurrently? If not, how does it avoid race condition?
>
> Thanks,
> --
> Yuliang Li
> PhD student
> Department of Computer Science
> Yale University
>



-- 
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] SNAT hash tables

[Yuliang Li]

Hi all,

I am curious in the SNAT implementation. I see that SNAT's hash tables
 are shared by all worker
threads. Does SNAT use lock to avoid multiple threads updating the hash
table concurrently? If not, how does it avoid race condition?

Thanks,
-- 
Yuliang Li
PhD student
Department of Computer Science
Yale University
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Test job maybe not working correctly

[Matthew Smith]

Hi,

After submitting a rebased patch set this morning, I went and looked at the 
console output of one of the jenkins jobs that kicked off automatically. The 
job was named vpp-test-poc-verify-master-centos7. It caught my eye that the 
name of the job implies that it should be running on CentOS 7 but the console 
output showed that it was building deb packages. Here’s the full console log 
for that build:

https://jenkins.fd.io/job/vpp-test-poc-verify-master-centos7/255/consoleFull 


Is something broken there? This seemed a little suspect to me, but I don’t have 
a full understanding of what each jenkins job is supposed to be doing or how 
they’re supposed to run.

Thanks,
-Matt Smith

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Neighbor Solicitation MAC

[Akshaya Nadahalli]

Can any of IPv6 experts comment on this? My understanding is that for
IPv6 even at L2 there shouldn't be broadcast address and should use
multicast address.

-- 
Regards,
Akshaya N 

-Original Message-
From: Akshaya Nadahalli 
To: vpp-dev@lists.fd.io
Subject: Neighbor Solicitation MAC
Date: Fri, 13 Oct 2017 14:39:42 +0530

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:5e:b5:37:8d (oui Unknown) > Broadcast, ethertype
IPv6 (0x86dd), length 86: 1::1 > ff02::1:ff00:3: ICMP6, neighbor
solicitation, who has 1::3, length 32

Linux sent NS messages:
14:36:00.731147 d2:bc:70:75:5e:f2 (oui Unknown) > 33:33:ff:00:00:01 (oui
Unknown), ethertype IPv6 (0x86dd), length 86: 1::2 > ff02::1:ff00:1:
ICMP6, neighbor solicitation, who has 1::1, length 32


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Fwd: 转发：the vapi test problem

[15803846349]

来自 魅族 MX4 Pro

 原始邮件 
发件人：重新开始 <15803846...@qq.com>
时间：周日 10月15日 21:46
收件人："Klement Sekera -X (ksekera - PA" 
主题：转发：the vapi test problem

when i send [want_vpncrack_decrypt_info] msg, why i receive 
[delete_subif_reply] msg ?   why i can not receive 
[want_vpncrack_decrypt_info_reply] msg ?


-- 原始邮件 --

发件人: "重新开始";<15803846...@qq.com>;

发送时间: 2017年10月15日(星期天) 下午5:13

收件人: "Klement Sekera -X (ksekera - PA";

主题: the vapi test problem


Hi, Klement    

The fllowing is the my plugin vapi test result. Can you explain why ? Thank you 
very much!

vpp@vpp-VirtualBox:~/test$ sudo ./test

DBG:vapi.c:316:vapi_connect():client api map `/vpe-api'

DBG:vapi.c:321:vapi_connect():connect client `test'

DBG:vapi.c:371:vapi_connect():Message `test_fake_msg_reply_cafebafe' not 
available

DBG:vapi.c:371:vapi_connect():Message `test_fake_msg_cafebafe' not available

DBG:vapi.c:371:vapi_connect():Message `test_fake_details_cafebafe' not available

DBG:vapi.c:371:vapi_connect():Message `test_fake_dump_cafebafe' not available

vapi connect success!

rv0 = 0

--- Receive stats using generic blocking API ---

ws->payload.pid = 3496 

DBG:vapi.c:435:vapi_send():send msg@0x3007c2f4:665[want_vpncrack_decrypt_info]

DBG:vapi.c:455:vapi_send():vapi_send() rv = 0

DBG:vapi.c:131:vapi_store_request():stored@0: context:8001 (start is @0)

--- 22 ---

DBG:vapi.c:700:vapi_dispatch_one():vapi_dispatch_one()

DBG:vapi.c:521:vapi_recv():doing shm queue sub

DBG:vapi.c:545:vapi_recv():recv msg@0x3004a454:7[delete_subif_reply]

DBG:vapi.c:740:vapi_dispatch_one():dispatch, context is 0

DBG:vapi.c:685:vapi_dispatch_event():No handler/generic handler for msg id 
0[delete_subif_reply], message ignored

DBG:vapi.c:700:vapi_dispatch_one():vapi_dispatch_one()

DBG:vapi.c:521:vapi_recv():doing shm queue sub




-- 原始邮件 --

发件人: "Klement Sekera -X (ksekera - PA";;

发送时间: 2017年10月13日(星期五) 下午5:17

收件人: "重新开始"<15803846...@qq.com>;

主题: Re: 回复： why my plugin api can not generate 
vapi_want_..andvapi_alloc_want... functions?


Oh, I probably see the issue. The VPP API is poorly designed and the
message types are guessed based on names.

Your want_XYZ_event message is recognized as `event' based on the
`_event' suffix. Since events are not to be allocated and sent by
client, the vapi_alloc* functions are not generated for them.

Currently, you'll have to respect the naming convention if you want the
generator to work correctly.

So, please only use _event suffix for actual events. Change the want_XYZ
messages so that they don't end with _event and everything should work
fine.

Regards,
Klement

Quoting 重新开始 (2017-10-13 11:10:45)
>    This is the init vapi.h file. The pre vapi.h file is modified by me. I try
>    to write the vapi_alloc_want ... and vapi_want. .. functions referening
>    the other functions. But the writen apis do not work.
>    -- 原始邮件 --
>    发件人: "Klement Sekera -X (ksekera - PA";;
>    发送时间: 2017年10月13日(星期五) 下午4:53
>    收件人: "重新开始"<15803846...@qq.com>;
>    主题: Re: why my plugin api can not generate
>    vapi_want_..andvapi_alloc_want... functions?
>    Hi 重新开始,
> 
>    I can't help you because you didn't provide the API nor mentioned any
>    error messages. Simply stating "it doesn't work, why?" is not enough to
>    debug the issue ;-)
> 
>    Cheers,
>    Klement
> 
>    Quoting 重新开始 (2017-10-13 10:45:32)
>    >    Hi, Klement
>    >    I use src/vpp-api/vapi/vapi_c_gen.py test.json to generate
>    >    test.api.vapi.h. and the fllowing is ok
>    >    static inline vapi_msg_vpncrack_pwh_update*
>    >    vapi_alloc_vpncrack_pwh_update(struct vapi_ctx_s *ctx)
>    >    {
>    >      vapi_msg_vpncrack_pwh_update *msg = NULL;
>    >      const size_t size = sizeof(vapi_msg_vpncrack_pwh_update);
>    >      /* cast here required to play nicely with C++ world ... */
>    >      msg = (vapi_msg_vpncrack_pwh_update*)vapi_msg_alloc(ctx, size);
>    >      if (!msg) {
>    >    return NULL;
>    >      }
>    >      msg->header.client_index = vapi_get_client_index(ctx);
>    >      msg->header.context = 0;
>    >      msg->header._vl_msg_id = vapi_lookup_vl_msg_id(ctx,
>    >    vapi_msg_id_vpncrack_pwh_update);
>    >      return msg;
>    >    }
>    >    static inline vapi_error_e vapi_vpncrack_pwh_update(struct vapi_ctx_s
>    >    *ctx,
>    >      vapi_msg_vpncrack_pwh_update *msg,
>    >      vapi_error_e (*callback)(struct vapi_ctx_s *ctx,
>    >   void *callback_ctx,
>    >   vapi_error_e rv,
>    >   bool is_last,
>    >   vapi_payload_vpncrack_pwh_update_reply
>    *reply),
>    >      void *callback_ctx)
>    >    {
>    >      if (!msg || !callback) {
>    >    return VAPI_EINVAL;
>    >      }
>    >      if 

Re: [vpp-dev] jvpp core future test failure (gerrit 8743)

[Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)]

Hi,

and here is jvpp fix to fail on the first CRC mismatch:
https://gerrit.fd.io/r/#/c/8831/

Regards,
Marek

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Barach (dbarach)
Sent: 14 października 2017 01:06
To: Ole Troan (otroan) ; Ole Troan 
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] jvpp core future test failure (gerrit 8743)

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 = _main;

  /*
   * This happens during the java core tests if the message
   * dictionary is missing newly added xxx_reply_t messages.
   * Should never happen, but since I shot myself in the foot once
   * this way, I thought I'd make it easy to debug if I ever do
   * it again... (;-)...
   */
  if (c->id == 0)
{
  if (c->name)
 clib_warning ("Trying to register %s with a NULL msg id!", c->name);
  else
 clib_warning ("Trying to register a NULL msg with a NULL msg id!");
  clib_warning ("Did you forget to call setup_message_id_table?");
  return;
}


Thanks… Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Dave Barach (dbarach)
Sent: Friday, October 13, 2017 1:32 PM
To: Ole Troan (otroan) >; Ole Troan 
>
Cc: vpp-dev@lists.fd.io
Subject: [vpp-dev] jvpp core future test failure (gerrit 8743)

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 of registering them. Note that I had to modify the binary API client 
library to keep Java from ASSERTing due to the NULL msg id’s squawked below.

What’s going on here? These messages work like a champ in vpp_api_test...

INFO: Testing Java future API for core plugin
[New Thread 0x7fffd5f9c700 (LWP 4611)]
vl_msg_api_config:671: Trying to register dns_enable_disable_reply with a NULL 
msg id!
vl_msg_api_config:671: Trying to register dns_name_server_add_del_reply with a 
NULL msg id!
vl_msg_api_config:671: Trying to register dns_resolve_name_reply with a NULL 
msg id!
[Thread 0x7fffd5f9c700 (LWP 4611) exited]
Exception in thread "main" java.lang.IllegalStateException: API mismatch 
detected: dns_resolve_name_reply_451ab6c0 is missing
 at io.fd.vpp.jvpp.core.JVppCoreImpl.init0(Native Method)
 at io.fd.vpp.jvpp.core.JVppCoreImpl.init(JVppCoreImpl.java:75)
 at io.fd.vpp.jvpp.JVppRegistryImpl.register(JVppRegistryImpl.java:72)
 at 
io.fd.vpp.jvpp.core.future.FutureJVppCoreFacade.(FutureJVppCoreFacade.java:25)
 at 
io.fd.vpp.jvpp.core.test.FutureApiTest.testFutureApi(FutureApiTest.java:50)
 at io.fd.vpp.jvpp.core.test.FutureApiTest.main(FutureApiTest.java:44)
[New Thread 0x7fffd54af700 (LWP 4612)]

Thanks… Dave

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] bug/issue notification

[Justin Iurman]

Hey guys,

Here are two issues I faced while installing/running VPP. It would be great to 
fix them.

1) Install not executed (at least, it seems that it's the case...) - tested 
with current version 18.01 (cloned today) but it's the same with previous 
versions too.

git clone https://gerrit.fd.io/r/vpp
cd vpp/build-root/vagrant
vagrant up

**waiting during the installation of the VM**
Note: install.sh does not seem to be executed during this process (can't see 
related outputs).

In the VM when logged in with vagrant ssh:

vvp <-- not found
cd /vpp/build-root/vagrant
./install.sh <- Permission denied

First problem: need to manually chmod +x install.sh (maybe that's the reason 
why ?).

Then, execute it again. It finishes but tells me there is a dependency error 
(second problem): package python-cffi is not installed. To manually fix it, I 
do the following:

sudo apt-get install python-cffi
sudo apt-get -f install

After that, install goes fine. Also, note that I've a plugin where a reference 
to "vlibsocket/api.h" needs to be removed from plugin.c and plugin_test.c in 
order to compile (removed/moved in this new version of VPP ?).

2) This bug seems to be gone since last week with vpp 18.01 (cloned today: 
Monday 16 October 2017). But I'll mention it, just in case you didn't hear 
about it. When running: "sudo vppctl -s /run/vpp/cli-vpp1.sock create 
host-interface name vpp1out", an error was returned (sorry, I don't remember 
exactly what was said). And this error was not in earlier versions (around the 
25 September 2017 I'd say).

Thanks !

Justin
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev