Add support for the hAP lite model rb952UI-5ac2nD equivilent to
the UBNT AirRouter. The 5Ghz interface will be configured in a
2nd phase. This hAP lite model has double the RAM and Flash
of the AR. the 2Ghz is MIMO (5Ghz is single antenna).
* aredn: node description on mesh page, lat/lon on both status and mesh, olsr entries
Added node description to mesh status page
Fixes#161
Added Lat/Lon (if available) to status and mesh pages.
It is diplayed above the description and under the node name.
Fixes#145
Added OLSR Routing tables entries to status page just under the memory area
Also added this same info just above the buttons on the mesh status page
Fixes#160
* aredn: OLSR routing table entries
Small addition to the displayed info
* aredn: corrections
move lat lon if statement farther up
changed system command lines to have () around them...
* aredn: added comments for new lines
* aredn: more corrections
back to using backticks on system commands per short discussion with ae6xe
* aredn: updated some lines so they will not toss warnings in the syntax tests
* aredn: Node Description Enhancements
Node Description entry on setup page is now multiline.
Fixes#91
Node Description display on status page is now a table cell,
allowing for background color addition and word-wrapping.
Fixes#90
Description background color added to CSS files with colors appropriate to each theme.
Other CSS additions for the description input field on the setup page.
Updated onboard help file about the node description field (and fixed a typo)
* move some of the character filtering "higher up the chain" in perl.
javascript still will replace any new lines with a space in case the user hit's enter in the description entry box.
tested with curl and I can't find any problems yet.
* removed some commented lines that were not needed
* actually fix the typo I saw in help.html file.
with low memory conditions, typically on 32Mb RAM, the
device would become unresponsive in hours to days. The
symptoms only occured when no RF links. iw processes
would hang in Zombie state. Updates to use iwinfo where
possible and avoid using both iw and iwinfo. crontab
script is implemented to detect Zombie processes and free
up resources in the reduced chance the symptoms are still
occuring.
* config change to make uhttpd listen on port 80 and 8080
* add port 80 to tunnel firewall rules
* add port 80 to tunnel firewall rules in config, update help
* firewall rules for wan + dtdlink
I found a duplicated file in www, only 16k, but every bit matters now.
Removed the duplicate and the replaced the file with a minified version.
Updated www/cgi-bin/scan to use new minified file.
Tested. works fine.
This Device is almost the same as the CPE210 V2.0
Once Support for the TP-LINK CPE210 V3.0 gets added to the OpenWrt code we
will need to drop the patch 001-add_support_for_TP-Link_CPE210_v3.patch
Closes#32
* feature: add node description to status page
* feature: add node description to status page
* scrub for html like tags and correct node description label
* cleanup extra whitespace, comments, and debug stmt
* Added the Nodes locally hosted service listing to sysinfo.json
Added the Nodes locally hosted service listing to sysinfo.json file.
* Forgot to change api_version
* Change info[] section to be services_local to keep in line with the function is called
was info[local_services] now info[services_local]
* Added Uptime and Load Averages to the sysinfo.json file.
All code copied from Darryl, dman776.
* Updated Api Version number to 1.2.
Updated Api Version Number to 1.2.
Once the PR for this is accepted by Openwrt we will need to remove the file
001-add_support_for_TP-Link_CPE510_v2.patch
Removed 001-add_support_for_TP-Link_CPE210_v2.patch as PR #937 has been committed
Updated 99_setup_aredn_include to remove unused Rssi Led configuration
AirRouter does not have a Status 4 LED.
The Power LED does similar to the Status 4 on the AirRouter.
Changing the text to be more generic removing reference
to LED's and leave the documentation of how to know
a node has booted to be done elsewhere.
fixes AREDN->ticket:208
Change-Id: I8821f86e89e17d25e4a21abfdd94d989619d081a
olsrd-watchdog can trigger when the olsrd service is restarted
Such as when a tunnel comes up, or when a config change is
made to olsrd.
procd already monitors olsrd and makes sure it remains running.
With procd we no longer need olsrd-watchdog and can remove it.
fixes AREDN->ticket:215
Change-Id: I5067d380a22bd0ab5e597746478ef3e1ba05d72d
The DHCP Name reservation on the ports page would allow
a user to use the name of the mesh node as a hostname
for a reserved host which would mess up the remote display
of hosts on the mesh status screen.
In addition while testing the verification code it was found
that it was case sensitive while dns is case insensitive.
fixes AREDN->ticket:198
Change-Id: Ie51a594f733eca38e8547faeab0260d7b23b8818
It is possible for the system to run out of memory when dealing
with large file uploads and installs.
As part of the upgrade procedure shutdown services that are not
essential for node operations to allow more memory for install
to take place.
Includes changes to linkled to indicate this new state as it will
be shutdown as part of the cleanup process.
Memory gain (approximate)
dropbear 100kb
linkled 200kb
logd 200kb
odhcp 100kb
snmpd 500kb
xinetd 100kb
Total(approximate): 1200kb (around %4 on 32mb devices)
This is somewhat similar to files/usr/local/bin/upgrade_kill_prep
except that it kills only a select group of services
so that the system can handle the file upload while
upgrade_kill_prep does the final system cleanup to run the full
upgrade.
ref AREDN->ticket:204
Change-Id: Ic6d3aa028725064a97c4723f6d9b36e1e51d87a7
If a user tries to upload a file (especially firmware images) while
a tunnel is active the nodes run a high risk of running out of
available RAM.
Change-Id: I6c31a5c641c7266f337aa4b209367ae0491703ad
dman776