ffpb-debug-report on crash.

As it is only assumed that the bug, which causes A.L.F.R.E.D. 2013.4 to
crash, got fixed in 2014.1, it is important to know whether or not this
really is the case. Hence, an additional check got implemented that
tests for the A.L.F.R.E.D. daemon's major version. If the major version
is greater than 2013 an additional ffpb-debug-report gets issued
automatically, so that the dev-team gets informed about the crash.

Monitors whether or not the A.L.F.R.E.D. is still running on a node or
not. Version 2013.x crashes from time to time and thus some nodes dis-
appear from the map. It is thus suitable to monitor the state of the
daemon on the node itself by periodically making requests to avoid un-
necessary support-requests and manual restarts of these nodes. In a
failure state, the daemon can simply be restarted by triggering its
init-script.

Please note that the bug is most likely gone in v2014.1 and newer and
and thus the package does not need to be included in the firmware in
newer firmwares.

First of all, the ffpb-debug script is now written in lua and thus requires
a lua interpreter to be installed. But since the script makes use of some
gluon-specific lua-functions/-variables (such 'site_conf' in site_conf.lua),
we have to make ffpb-debug depend on the 'gluon-core', which in turn would
define all other dependencies.
Moreover, since ffpb-debug-live got rewritten to work with Barrier Breaker
(i.e. gluon 2014.4 and later), the already defined dependency towards the
busybox package does not suffice any longer, as we fetch interface-details
and -statistics via ubus now. As ubus outputs its data in JSON, we moreover
need the helper functions from the 'libubox' package for a convenient hand-
ling of such data in shell scripts.

It was only used in a local test and the same functionality can
be accomplished in the next Gluon version by setting
`siteconfig.authorized_keys`.

Wifi Blackout Workaround (Extension of ffpb-debug)

This patch extends ffpb-debug to include additional WiFi infos and values from the ath9k-debugfs (as proposed in gluon issue #130).

Due to the WiFi blackout problem with ath9k devices, gluon devs request additional
debugging data from the ath9k debugfs [1]. We follow this advice and try to fetch even
more data from the debugfs for ffpb-debug.

[1] https://github.com/freifunk-gluon/gluon/issues/130

Master

offline capabilty for ffpb-debug log file storing and sending them afterwards. should be triggered via conjob

  this script is intended to be run by a cronjob in $timeinterval and will
  automagically remove the report if send is succesful.

Signed-off-by: Stefan Kloepping <nothalpha@c3pb.de>

Signed-off-by: Stefan Kloepping <nothalpha@c3pb.de>

Copied from https://github.com/freifunk-gluon/packages/commit/341bb49b201ee734dbf842713b45e1d56ffaf517

This makes debugging a lot easier and you cannot forget to redirect the output
because this happens automatically.