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.
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
Inside the source files the word "contained" was mispelled
as "conained"
The website currently lists this correctly as "contained"
This was an error in the intial stamping of the source files in
changeset:5c3ee1d0686c6e6f2907fe4fc393d86d6c5a69b5/aredn_ar71xx
Line is part of "Additional Conditions" permitted by GPLv3.
Line does not impact coders prior to the AREDN setup date
as it was added by the AREDN team.
Change-Id: I3bc09aea548100f35c08aebe8686b8d4808d56d8
Signed-off-by: Conrad Lara - KG6JEI <KG6JEI@amsat.org>
Signed-off-by: Joe Ayers <ae6xe@arrl.net>
Signed-off-by: Darryl Quinn <k5dlq@arrl.net>
Signed-off-by: Trevor Paskett - K7FPV <snoopytjp@gmail.com>
This is at the top of the license header.
It prevents the code from being processed but doesn't
actually impact the license terms in any way.
Change-Id: Ic91f2400f9694056b6f06fa43d1074411d6c6262
Mesh nodes would need a significant amount of configuration
including some operational checks everytime an interface comes up
to be able to handle this.
The more sane method is to only allow a node to be a mesh_gw when
the WAN port is utilized and the node is in DIRECT mode.
This changes the UI to prevent this setup from being allowed.
fixes AREDN->ticket:184
Change-Id: I1a1289bc914a349149f5842812dbebc0a70442f7
Mainly relates to TP-Link devices which have a roving power level programmed into the hardware.
The datasheets for the hardware may say higher power but the chip has been programmed to not go above these values.
Trying to registry over-write the antenna setting has never been a good idea in the first place.
The hardware fully handles antenna selection without forcing it already.
ref AREDN->ticket:120
All node type's except mesh have been deprecated.
In a future release we will remove them (and the associated code) to streamline the project.
It is recommended to use a dedicated purpose driven device for these modes in the future
When a node is first setup (unconfigured) the rf channel or when user presses reset button the wifi channel and bandwidth will be set to mesh default even if it does not match the current RF channel.