Since the switch to netifd, proto handlers may always set the defaultroute
and provide dns server addresses, netifd will decide in the generic code
path whether the announced values are masked or not.
Additionally protocol handlers should not modify the routing tables themselves
and prevent any launched services from doing so.
Remove the additional defaultroute and peerdns option handling from the ppp.sh
protocol handler and rely on netifd to mask or not mask the values.
git-svn-id: svn://svn.openwrt.org/openwrt/packages@34537 3c298f89-4303-0410-b956-a3cf2f4a3e73
Remove module loading from xl2tpd init-script now that module gets loaded
properly during boot (since that was already fixed in #32562, this partly
reverts #32563)
Signed-off-by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/packages@32574 3c298f89-4303-0410-b956-a3cf2f4a3e73
This integrates xl2tpd suppport into netifd, based on what I saw for ppp and pptp.
I also changed the init script so that it makes sure that all modules needed for
kernel-mode l2tp support are loaded at the time that xl2tpd is started, as
otherwise xl2tpd falls back into using user-mode l2tp.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/packages@32563 3c298f89-4303-0410-b956-a3cf2f4a3e73
* Fix initscript for
https://bugzilla.redhat.com/show_bug.cgi%3Fid%3D247100
* Fix for two Windows machines behind the same NAT with the same
number of l2tp connection attempts since boot [Shinichi Furuso]
Changes in this patch:
* use PKG_INSTALL:=1
* use standard config file names like in other major distributions
* new patch to disable building pfc (which was not installed anyway),
removes dependency to libpcap
* include a commented sample config file
* use INSTALL_CONF instead of INSTALL_DATA + chmod 0600
-Raphael
git-svn-id: svn://svn.openwrt.org/openwrt/packages@20276 3c298f89-4303-0410-b956-a3cf2f4a3e73