On 2013-09-10 9:53 AM, Bastian Bittorf wrote:
> * Luis R. Rodriguez <mcg...@qca.qualcomm.com> [10.09.2013 09:32]:
>> On Fri, Sep 6, 2013 at 12:39 PM, Luis R. Rodriguez
>> <mcg...@qca.qualcomm.com> wrote:
>> > From: "Luis R. Rodriguez" <mcg...@qca.qualcomm.com>
>> >
>> > iw is to iwconfig as
>> > ip is to ifconfig
>> >
>> > As with iwconfig, ifconfig is deprecated, promote usage of ip
>> > using netlink.
>> >
>> > Signed-off-by: Luis R. Rodriguez <mcg...@qca.qualcomm.com>
>> 
>> Actually perhaps its best to enable iproute2 package instead.
> 
> This is discussion is old, an there are some reasons not to switch.
> Mostly because of size und that most functions which are possible with
> 'ip' are not used in standard builts. if we switch to 'ip' we should
> also drop 'ifconfig','netstat' and 'route'.
> 
> a quick 'git grep' show usage of 'ifconfig' in preinit-scripts and
> '/lib/wifi/hostap.sh' + /lib/wifi/mac80211.sh (see appendix), but all
> of them can be converted.
I don't think they should be converted, I think uses of ip/ifconfig in
scripts should be made unnecessary and removed. It's netifd's job to
handle that stuff.

> i would like to see openwrt with a modern 'ip' - but i'am mostly alone 8-)
> 
> some size-related facts on ar71xx:
> 
>  99439 bytes - ip_3.10.0-1
> 229047 bytes - busybox_1.19.4-7(standard openrt)
> 218418 bytes - busybox without ifconfig, netstat, route
> 
> so we add ~80k to a standard built. i'am ok with this, because we also
> add a lot of features and possibilities which are simply not possible
> with ifconfig/route/netstat.
What features/possibilities do you see here? For things related to
configuration, I don't want to rely on either ifconfig or ip at all.

> the busybox-native ip-command is limited/uncomplete and we should not discuss
> it at the moment IMHO.
I agree.

- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to