Technical data

4. Packages
DYNDNS_1_CIRCUIT='1 2 3' # Only ISDN: Circuits 1 to 3
or
DYNDNS_1_CIRCUIT='pppoe' # Only DSL: pppoe-Circuit
or
DYNDNS_1_CIRCUIT='dhcp' # Update with DHCP providers
# (opt_dhcp needed)
or
DYNDNS_1_CIRCUIT='pppoe 1' # DSL and ISDN
or
DYNDNS_1_CIRCUIT='static' # fli4l i.e. behind a LTE Router
DYNDNS_x_RENEW Some providers expect an update every n days even without your IP
having changed. This interval may be set here. If no value is given an update will be
forced every 29 days.
It should be noted that an update is triggered only when dialing. This means: DSL or
ISDN connections or a renewing of a lease of an interface configured via DHCP like in
a cable modem. If no dialing occurs for a longer time period you have to trigger the
update in other ways.
DYNDNS_x_EXT_IP This variable configures the method by which the external IP address
is detected. By setting this to 'no' no external service will be queried for the IP address
and the IP address of the WAN interface will be used instead. This usually works only
with WAN connections which terminate directly on the fli4l, such as PPPoE via DSL.
If specifying 'dyndns' the IP address used when updating is determined by using the
external service of checkip.dyndns.org. When using 'stun' the list of STUN servers is
queried one by one until a valid response is returned. The use of an external service to
determine the IP address is necessary if the router itself is not getting the external IP.
It should be noted that the router will not note a change of the external IP in this case
and thus can’t update the dyndns name entry immedeately.
DYNDNS_x_LOGIN Some providers require the user to log in to their Web page regularly
by using her/his user account to prevent the service from being deactivated. If this
variable is set to 'yes', the FLI4L will do that for you. However, this only works if the
dyndns package is prepared for this provider. Such a regular registration is currently
only necessary and possible for the provider “DYNDNS”. Please remember also that the
use of this function requires OPT_EASYCRON=’yes’ in package easycron.
DYNDNS_LOGINTIME If you use a provider FLI4L should log into regularly to prevent
deactivation of the service (see above), you can use this variable to configure at what
time this login process is intended to take place. A time value in Cron format is required
here, for details please read the Documentation of package easycron. The default setting
is 0 8 * * *, meaning a daily login at eight o’clock in the morning.
DYNDNS_ALLOW_SSL Setting this variable to 'yes' will update over an encrypted SSL
connection if possible.
116