OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by André Lange - 11.03.2017
Last edited by Yousong Zhou - 19.03.2017

FS#620 - ip-full: monitor command throws error

Hi,

I would like to port my project ip6neigh https://github.com/AndreBL/ip6neigh to LEDE. The following issue was found when testing it in LEDE (17.01.0, r3205-59508e3) VirtualBox x64 image and ip-full package with details below:

root@LEDE:~# opkg info ip-full
Package: ip-full
Version: 4.4.0-8
Depends: libc, libnl-tiny
Provides: ip
Status: install user installed
Section: net
Architecture: x86_64
Size: 137862
Filename: ip-full_4.4.0-8_x86_64.ipk
Description: Routing control utility (Full)
Installed-Time: 1488935742

When trying to run the ip -6 monitor command, and error is thrown like shown below:

root@LEDE:~# ip -6 mon neigh dev br-lan
open(”/proc/self/ns/net”): No such file or directory root@LEDE:~# ip monitor
open(”/proc/self/ns/net”): No such file or directory root@LEDE:~#

I would like to contribute with the ip6neigh script on LEDE. The monitor command is essential to make it work there.

Regards,
André

Closed by  Yousong Zhou
19.03.2017 04:44
Reason for closing:  Fixed
Additional comments about closing:  

Fixed by ht tps://git.lede-project.org/0f23e80c272be 4eaaa3e898f9e427886203be720

Project Manager
Yousong Zhou commented on 17.03.2017 09:37

We may need to apply this patch: https://www.spinics.net/lists/netdev/msg396172.html

Craig Miller commented on 18.03.2017 20:44

I have reproduced this on a Buffalo WZR-HP-G300NH running LEDE 17.01.1

It appears that the 'ip' command has been compiled to support network namespaces, but the kernel hasn't, and therefore /proc/self/ns/net is not present.

While I agree that the patch yousong refers to would fix the problem, I suspect the ip command itself has a configure option to support (or not) network namespaces, which would be a better solution.

Project Manager
Yousong Zhou commented on 19.03.2017 05:37

Hi, Craig

I just took a look at the code, it seems that iproute2 does not have such a configure option at the moment. The code is likely geared more toward runtime detection of features' availability.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing