John Crispin cba772f5bc pppd: Place plugin-specific options after `plugin name`. ... Before this patch, if we specify a plugin specific option through `pppd_options` in /etc/config/network, e.g. `rp_pppoe_verbose 1`, pppd would quit with the following error in log. Wed Oct 9 09:42:58 2013 daemon.notice netifd: GORG (1689): /usr/sbin/pppd: unrecognized option 'rp_pppoe_verbose' Wed Oct 9 09:42:58 2013 daemon.err pppd[1689]: unrecognized option 'rp_pppoe_verbose' Wed Oct 9 09:42:58 2013 daemon.notice netifd: GORG (1689): pppd version 2.4.5 Wed Oct 9 09:42:58 2013 daemon.notice netifd: GORG (1689): Usage: /usr/sbin/pppd [ options ], where options are: This is due to the requirement that function add_option() should be called by the plugin_init() function first before pppd can parse those options. Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> SVN-Revision: 38911		2013-11-25 14:09:16 +00:00
..
files	pppd: Place plugin-specific options after `plugin name`.	2013-11-25 14:09:16 +00:00
patches	pppd: don't call modprobe at all from pppoatm	2013-11-11 13:40:28 +00:00
utils	packages: sort network related packages into package/network/	2012-10-10 12:32:29 +00:00
Makefile	ppp: correctly handle address when reloading	2013-06-10 10:42:34 +00:00