Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
openwrt-bot opened this issue Mar 11, 2017 · 3 comments
Closed

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

openwrt-bot opened this issue Mar 11, 2017 · 3 comments
Labels

Comments

@openwrt-bot
Copy link

openwrt-bot commented Mar 11, 2017

AndreL:

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é

@openwrt-bot
Copy link
Author

openwrt-bot commented Mar 17, 2017

yousong:

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

@openwrt-bot
Copy link
Author

openwrt-bot commented Mar 18, 2017

cvmiller:

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.

@openwrt-bot
Copy link
Author

openwrt-bot commented Mar 19, 2017

yousong:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant