By using the netifd for open fortivpn we are able to set up multiple
VPN connections and manage them through the netifd toolset.
This also adds support for binding an openfortivpn client to a given
interface, in which case when that interface comes online, the vpn
will be initiated via a hotplug script.
This is a breaking commit and configurations will need to be migrated
from openfortivpn.config into the /etc/config/networks.
Example configuration via /etc/config/network:
config interface 'ftvpn'
option proto 'openfortivpn'
option server 'example.com'
option username 'USERNAME'
option password 'PASSWORD'
# optional arguments follow
option local_ip '192.0.5.1'
option port '443'
option iface_name 'wan'
option trusted_cert 'CERT_HASH'
option set_dns '0'
option pppd_use_peerdns '0'
option metric '10'
Signed-off-by: Aaron Goodman <aaronjg@stanford.edu>
Build is failing because HWTSTAMP_TX_ONESTEP_P2P is defined anymore on
linux net_tstamp.h.
Moreover, the usual way of linuxptp build is looking for system includes
unless user defines differently. That also was tried to fix.
PKG_RELEASE bumped to 3.
Signed-off-by: Paulo Machado <pffmachado@yahoo.com>
Removed patch
`03-configure-allow-to-manually-disable-POSIX-capabiliti.patch` that has been backported into release.
Signed-off-by: Jan Hak <jan.hak@nic.cz>
The existing interface selection/detection code was incomprehensible at
worst and convoluted at best. The uci config file suggested it
understood an external ipv6 interface but in reality the init script
took no notice. Re-work it so it is at least comprehendible and takes
notice of ipv6 interface details if specified.
Update the hotplug script to use the same interface selection/detection
code as the init script and take note of ipv6 interface selection, only
restarting miniupnpd on interface up events and only if that interface
isn't already known (for that ip class) by miniupnpd.
For me this has solved numerous 'flaky' startup problems, especially
with regard to ipv6.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
prereq-build.mk says that GCC 4.8 and above is supported. GCC 4.8
defaults to std=gnu89, breaking the build. GCC5 defaults to gnu99.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
prereq-build.mk says that GCC 4.8 and above is supported. GCC 4.8
does not default to gnu++11. This fixes compilation.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
The minimum version of GCC according to prereq-build.mk is 4.8 which
defaults to gnu89. This breaks the host build when the host GCC is less
than 5, which defaults to gnu99. Add a simple CFLAG to fix.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
It seems 1.11.1 is old and has CVEs.
Removed boost hack since upstream removed boost support.
Removed outdated InstallDev hacks.
Added PKG_CPE_ID.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
