On 2011-10-22 1:30 AM, Hanno Schupp wrote:
Thank you for the fast response.
For sake of clarification: When you mention 'network configuration scripts'
are you talking about scripts like the old brcm-2.4 init.d netconfig script
and things like target profile specific network configuration defaults
stored in target/linux/atheros/base-files/etc/uci-defaults/network and
target/linux/ar71xx/base-files/etc/defconfig/* for example?
I'm talking about the actual scripts that configure the network, e.g.
/lib/network/*.sh, /sbin/ifup, some scripts in /etc/hotplug.d.
netifd is intended to stay compatible with the existing format of
/etc/config/network, the only exceptions being rare special cases like
aliases or the overlay variables in /var/state, though even most of
those can be easily emulated.
One thing that netifd does much better is handling config changes. When
/etc/config/network changes, you no longer have to restart all
interfaces. Simply run /etc/init.d/netifd reload, which will issue an
ubus call to netifd, telling it to figure out the difference between
runtime state and the new config and apply only that. This works on a
per-interface level, even with protocol handlers written as shell scripts.
- Felix
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
