This makes the applications of the affected plots more versatile
and thus reduces the need for duplicate code.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This patch aims at showing the client-caused traffic. We use
bat0 for this, at this seems to be the easiest way which does not
require router-specific ifs etc.
This patch distinguishes between routers and gateways:
- For routers, we just use the bat0 data
- For gateways, we aggregate eth0.1, eth1.1, w2ap and w5ap
This requires changes to the MySQL database!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This change the behavior concerning the displayed netif name in
the legend of the neighbor stats plot. Previously, the netif name
of the device was shown, now we show the netif name corresponding
to the neighbor. This is necessary, as we do not log netif names
for neighbors.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
If a router is currently not connected as neighbor, we don't see
its history. This patch shows all current and former neighbors.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
The data for each netif is only loaded when the respective row
is clicked.
Correspondingly, br-mesh is loaded initially.
So far, it is unclear how big the impact of the netif filter in
MySQL transactions is, as those have no key of their own.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
With this patch, only the neighbor stats for the last day are
loaded by default. If you want more, a hyperlink is implemented
for this purpose.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Since events do not cost much, the number stored and displayed
is drastically increased.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adds display support for BATMAN_V data.
This is step 1 of 2. It does change the background colors for
neighbors, but does NOT change the link colors in the map.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This only works for routers with updated nodewatcher.
This requires changes to the MySQL database!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This only works for routers with updated nodewatcher.
This requires changes to the MySQL database!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This affects only whether the status indication is SHOWN. It does
not affect the storage of this tag.
One can still en- or disable the blocked status of a V2 router via
the options menu.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This only works for routers with updated nodewatcher.
This requires changes to the MySQL database!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This only works for routers with updated nodewatcher.
This requires changes to the MySQL database!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This includes various changes throughout the code. Additionally,
some fields are reordered.
This requires a change of the MySQL table router_neighbor!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This shows information about WiFi parameters (e.g. channel).
Except the Tx-Power, data is only available if a firmware with
a corresponding nodewatcher update is present (version 44).
This requires a change of the MySQL table router_netif!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
If routers are supposed to be removed from the Monitoring
permanently, they can now be banned based on their MAC address.
All admins can do that via the web interface.
ATTENTION: This requires a database update!
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
This is fixed to the br-mesh address. If a router has no br-mesh,
no perma-link is displayed.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Since we use regex for the query string, we have to set markers
for beginning and end when we want to match only the whole field.
Fixes#85
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
The mysql queries had been executed in a for loop, this is
moved to a single query now.
Side effect may be a little more JavaScript execution time.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Adrian Schmutzler
Dominik Heidler