Jo-Philipp Wich

@ptpt52 - fixed as well

@dhewg - thanks, fixed.

@ptpt52 - This module currently cannot be used anymore in a stand alone manner anymore. Can you please show the code that was working previously and is not anymore?

Hmm, you can query the valid state of the input fields to see if a valid IP address is present to begin with, then simply check that either both src...

Yes, for backwards compatibility with fw3, only IPv4 is assumed if no explicit `option family '*'` or `option family any` or `option family all` is given.

Please provide the relevant UCI settings of /etc/config/network as well as the generated peer configuration and the peer configuration as it *should* look like. Your description is not clear enough...

Is the `Address = ` part actually needed or is adding the `192.168.43.1` entry to AllowedIPs enough? By default, if you don't specfiy any allowed IPs for the peer, the...

This issue occurs when the channel list is empty, e.g. due to an invalid regdomain. A fix has been pushed in 9af8486517 which at least prevents the exception reported here.

From `ppp.sh`: ``` local lcp_failure="${keepalive%%[, ]*}" local lcp_interval="${keepalive##*[, ]}" ... [ "${lcp_failure:-0}" -lt 1 ] && lcp_failure="" ... proto_run_command "$config" /usr/sbin/pppd \ ${lcp_failure:+lcp-echo-interval $lcp_interval lcp-echo-failure $lcp_failure $lcp_adaptive} \ ``` Means...

Default values in pppd `lcp.c`: ``` int lcp_echo_interval = 0; /* Interval between LCP echo-requests */ int lcp_echo_fails = 0; /* Tolerance to unanswered echo-requests */ ``` So I am...