[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2018-04-26 Thread Abhik
** No longer affects: libnl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache Status in libnl3

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2018-04-26 Thread Abhik
Hi, Same issue. I am using similar test application to get the neighboring mac addresses on a Centos 7.2.1511 machine. Installed 3.21, 3.28, 3.4 versions and all returned with NULL. Is this going to be fixed? Or Is there any other API within libnl3 that can do the trick? Abhik -- You

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2018-04-26 Thread Abhik
** Also affects: libnl Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2017-10-16 Thread Rafael David Tinoco
** Changed in: libnl3 (Ubuntu) Assignee: Rafael David Tinoco (inaddy) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill;

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2016-05-28 Thread Mathew Hodson
** Tags added: trusty ** Tags added: testcase ** Changed in: libnl3 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-12-01 Thread Talat Batheesh
Hi Rafael, After updating libibverbs and libmlx4 (upstream version) from the openfabrics, the issue solved. git clone git://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git libibverbs git clone git://git.openfabrics.org/~yishaih/libmlx4.git # apt-get install libnl-3-dev libnl-route-3-dev

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-11-22 Thread Talat Batheesh
Hi Rafael, Unfortunately, after installing the PPA, the udaddy test still fail on Ubuntu 14.04.3 LTS. Tested with ConnectX3-pro. root # udaddy -b 1.1.1.1 udaddy: starting server receiving data transfers ^C root# uname -r 3.13.0-68-generic root# cat /etc/issue Ubuntu 14.04.3 LTS \n \l

Re: [Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-11-22 Thread Rafael David Tinoco
Awesome. Thank you Talat. This was actually a simple example I was giving to Kamal, explaining to him how the SRU process worked and giving him a real example on how to provide a debdiff and create a PPA. So, I really did not expect the fix to be "good" but to give him so clue how things worked.

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-09-16 Thread Rafael David Tinoco
It looks like that Trusty version also suffers from: root@dixie:~# virsh start maas error: Failed to start domain maas error: internal error: missing IFLA_VF_INFO in netlink response Whenever we try to start a VFIO (or KVM passthrough) SR-IOV based machine. I don't think this happens under

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-09-12 Thread Rafael David Tinoco
** Changed in: libnl3 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-09-08 Thread Rafael David Tinoco
** Changed in: libnl3 (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (inaddy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill;

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2015-09-08 Thread Rafael David Tinoco
Kamal, As we talked about, I'm making the following PPA available: https://launchpad.net/~inaddy/+archive/ubuntu/lp1312419 It contains Trusty version + commit: >From 3700cc1ad3a3b507848deb401b9d0f41ff7010bb Mon Sep 17 00:00:00 2001 From: Thomas Graf Date: Fri, 1 Feb 2013

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2014-12-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libnl3 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu.

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2014-12-10 Thread Micah Cowan
I can confirm this issue in Trusty (libnl3 version 3.2.21-1), relative to Precise (3.2.3-2ubuntu2). I can install the Precise binaries for: libnl-3-200 libnl-3-dev libnl-genl-3-200 libnl-genl-3-dev libnl-route-3-200 libnl-route-3-dev onto a Trusty system, and the issue goes away. To

[Touch-packages] [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

2014-12-10 Thread Micah Cowan
I've confirmed that the issue is fixed in Utopic (3.2.24-2) (I didn't know whether Utopic-built binaries work directly - I built from the Utopic source package). Looks like a backport is what's called for. Obviously, I won't be opening upstream bugs after all, since it's already been fixed for