* Bringing up network interface lo ... ip: either "to" is duplicate, or "scope" is garbage [ ok ] * Bringing up interface lo * Caching network module dependencies * 127.0.0.1/8 ... [ ok ] * Adding routes * 127.0.0.0/8 via 127.0.0.1 ... [ ok ]
I need more information. Which ip command/arguments are not compatible? Thanks, William
loopback 29.38|+ ebegin Bringing up network interface lo loopback 29.38| * Bringing up network interface lo ...+ type ip loopback 29.39|+ ip addr add 127.0.0.1/8 dev lo brd + scope host loopback 29.39|ip: RTNETLINK answers: File exists loopback 29.39|+ ip route add 127.0.0.0/8 dev lo scope host loopback 29.39|ip: either "to" is duplicate, or "scope" is garbage loopback 29.39|+ ip link set lo up loopback 29.39|+ eend 0 loopback 29.39| [ ok ] (not sure what's happening there ... ?!)
*** Bug 506526 has been marked as a duplicate of this bug. ***
busybox iproute2 does not support the 'scope' argument in 'ip addr add', but it does support it in the 'ip addr show'. Worse, there's no --help output that we can use to detect if it's supported or not. It does seem to support it for both 'addr show' as well as routes. The bug does go a VERY long way back, but wasn't caught before because of lack of error checking. baselayout-1.11.15/net-scripts/net.modules.d/iproute2: ip addr add 127.0.0.1/8 dev lo brd + scope host that's in the old SVN stuff, pre-baselayout2, and the tag dates to 2005/apr/14.
As for an immediate fixing plan, do we actually still NEED to specify 'scope host' manually? I think we should change it to use the kernel's default, and only pass in the scope if the user explicitly sets it themselves.
netifrc: [master 699636d] net/iproute2: no automatic scope=host on loopback. 1 file changed, 5 deletions(-) github/robbat2/openrc: [loopback-scope 6d60bba] init.d/loopback: drop scope on loopback Date: Mon Oct 24 14:19:22 2016 -0700 1 file changed, 2 insertions(+), 2 deletions(-)
https://github.com/OpenRC/openrc/pull/103
This is present in the 0.5 series, and handled in openrc as well.
