This option enables build of pptp kernel module. If you have 2.6.37 or later linux kernel you don't need this option because starting from 2.6.37 pptp is included to mainline kernel.
I'm a bit confused by the documentation here. Is your pptp kernel module REQUIRED to use pptp with accel-ppp - or the standard kernel module for pptp works just fine?README wrote: Warning !!!
1. The pptp driver conflicts with ip_gre driver (in kernel), so make sure that ip_gre is not built-in or loaded at run time
(don't matter if you have 2.6.37 or later kernel).
2. Don't mix connections of accel-ppp and poptop's pptpd, before starting accel-ppp make sure that no connections
of pptpd exists.
Because the standard linux kernel module depends on gre
Code: Select all
root@wifi:/mnt/nbd/pcap# lsmod |grep pptp gre 992 2 pptp pptp 13488 0 root@wifi:/mnt/nbd/pcap# lsmod |grep gre gre 992 2 pptp ip6_gre 14528 0 ip6_tunnel 17504 2 ip6_gre ip_gre 9120 0 ip_tunnel 10144 4 ip_gre
I haven't done a pull request for the package yet, but I've done a precursor. I take it building outside the CMAKE_HOME_DIRECTORY is require for ipoa kernel module in shared mode.
All accel-ppp modules are only dynloaded if they are specified in the configuration file right? I'm going to try to use modular packaging for accel-ppp in openwrt then to keep the space down in embedded system's flash. The same kind of way strongswan is built in openwrt.
Is the snmp mode buggy in non-master, or just any mode? I saw some mention of that on the forums.
If I get obsessed with maintaining this package, it will have configuration file validation and luci web gui for administration down the track too.