* Dont display previous neighbors with empty hostnames
* Use IP address when name missing
* Fix bug where missing names became ever growing string of whitespace
* Improve the firmware upgrade process
The old firmware upgrade process attempted to free up RAM by reusing
the 'upgrade_kill_prep' script which is later used by '/sbin/sysupgrade'.
Unfortuantely this doesn't work as intented. While the script will go about
killing various services, 'procd' just goes and starts them up again using
quite a bit more memory in the process. Instead this script just kills
the various daemons 'no questions asked' and then runs the associated
'/etc/init.d/xxx stop' script to instruct 'procd' not the start them up again.
This gets us to the place the original script was trying to go.
+ A syntax fix in '007' patch (need spaces around the [ .. ])
* Inline the style for the firmware page to avoid sleep before flash
* Minor reliability improvements
* Clear away services even earlier
* Final bits of perl replaced by lua
* Use iwinfo during first boot (api I was using fails this early)
* Retry getting phy device (it can fail as the node is booting up)
* Lua vpn server and client pages
* Lua vpn server and client pages
* Fix reporting of daemon restart errors
* Lua olsrd-config
* Fix reversed client/server ip assignments
* Fix patterns for finding active tunnels
/etc/config.mesh/aredn sometimes gets truncated, although reproducing it is difficult. This
is one of the few places this file is mindlessly written to, so instead use cursors to update it.
* Lua Services
* Lua versions of user page (non-admin)
* Support multiple antenna chains
* Improved led detection
* Fix logging
* Add manager.log files to support tool
* Lua versions of user page (non-admin)
* Dont count default route
* Fix board id for older nodes
* Handle missing node.history
* Check /tmp/snrlog exists
* Per discussion, make the Lua pages the defaults and Perl the backups
* Migrate /etc/config/dmz-mode to /etc/dmz-mode
* Migrate dmz_mode into /etc/config/aredn
* Use cmd append
* Changes should be in /etc/config.mesh
* Add commit
* add uci migration script
* removed debug lines
* added newline to end
* include gridsquare values
* migrate lat/lon/gridsquare to uci format
* remove from sysupgrade kept files list
* Memory and cpu performance improvements
* Fix bandwidth reporting
* Discard large arrays once we're done with them
* Fixup whitespace
* Improve string constructions
* Use available mem
* Print the Remote Nodes as we go (can be big)
* Local variables
* Stop re-reading arp/mac files
* Reduce calls to system 'cat'
* Simply lat/lon read
* Only read route30 once
* Whitespace
* Make meshstatus limits configurable
* and => &&, or => ||
* gzip content if we can
fixes#155
* api: add RF IP for non-RF links
Add the RF IP address for non-RF linked devices. This allows the
services to be displayed for non-RF Current Neighbors.
* remove case manipulation
Update the alert banner background color to distinguish it from the
"supported hardware" messages. This makes it look more like a standard
sticky note.
Aliases in NAT mode allows the node admin to create alias names for hosts on the LAN and then use those for creating port forwarding rules. The aliases DO NOT effect the rest of the mesh network and are not propagated via OLSR.
NAT Mode aliases are only usable on the local LAN where the IP addresses are known and routable only on the subnet. Since the NAT hides these IP addresses or the node masquerades, other mesh nodes and devices by definition only know about the node’s hostname. Thus aliases on the LAN in NAT mode are not propagated by OLSR across the mesh. You _CANNOT_ use an alias name in a service listing.
You _will_ be able to set an alternate hostname for any host on the nodes' LAN however.
A host named `CBY45-DELLLAPTOP` can also be known as `wxc-shack-laptop`. It may make remembering which host is which a bit easier.
Since OLSR does not propagate the alias, the "Do Not Propagate" checkbox while in NAT Mode is hidden.
* enhancement: show the "non propagated" hosts as a grey color in the mesh list on the localnode.
This allows for the node admin to see, at a glance, which of the hosts are "hidden" or not.
* changed colors a little bit for the black background styles.
also assed in the aliases so now they will show up as a different color too.
this only effects the mesh listing on the localnode to where the aliases and/or non propagated hosts are.
the rest of the network does not see this.
* add a tooltip to the aliased/non propagated hostnames to help explain what they mean
Allows for aliased hostnames on the mesh. One IP/Host can be assigned to multiple hostnames.
This is useful for many things including virtual hosts, virtual machines, virtual email addresses, etc.
The possibilities are actually _endless_.
Fixes#516
Allows for the node admin to choose to have DHCP leased hostnames/IP's propagated over the rest of the mesh network or not.
Defaults to allowing the hostname/IP to propagate.
The hostname/IP will *still* be resolvable from the localnode and will show up in the list of hosts on the localnode only.
This allows for selected local mesh devices to be not available over the rest of the mesh network.
ie: switches, routers, cameras, etc.
This will work immediately for *new* DHCP leases when the checkbox is selected.
For *existing* DHCP leases, it may take a while for the network to update, if ever.
To speed up the process of full network OLSR "DNS" updating, reboot all the nearest neighbor device(s) to the node you made these changes to.
That seems to get the changes "out" to the rest of the network faster than normal.
Fixes#508
Change the Advanced Configuration warning banner: slightly wider to
distinguish from Alerts banner, add WARNING and make text color pure
white for contrast.
In the US, part 97 ham radio lower band edge is 5650.
Channel 131 @ 10MHz channel width is the lowest channel
setting that stays within allocation.
fixes#550
in the past nodes could be configured uniquely for
a given mode: ap, wifi client, mesh. Current behavior
in basic setup no longer has unique modes, rather wireless
cards can be configured in different modes in basic setup
and devices with multiple wireless interfaces can
be setup to use multiple modes at the same time.
fixes#533fixes#535
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP:
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP address:192.168.0.254
catch the tunnel comment field in perlfunc's read_post_data function where certain characters are changed to the html character entity in order to not interfere with the config files.
Tested with all kinds of crazy charcters such as: zdsfkh? <!@#$%^&*()> "quote"
Fixes#515
Specifications:
* SoC: Qualcomm Atheros AR9344 (560 MHz)
* RAM: 64MB
* Storage: 8 MB
* Wireless: 2.4GHz N based built into SoC 2x2
* Ethernet: 2x 100/10 Mbps, integrated into SoC, 24V POE IN
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP:
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP address:192.168.0.254
TP-Link CPE610-v2 is an outdoor wireless CPE for 5 GHz with
one Ethernet port based on Atheros AR9344
Specifications:
Based on the same underlying hardware as the TP-Link CPE510
Power, LAN0, WLAN green LEDs
23dBi high-gain directional 2×2 MIMO antenna and a dedicated metal reflector
Flashing instructions:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Signed-off-by: Andrew Cameron apcameron@softhome.net
* enhancement: added contact info/comment field for each tunnel connection.
Allows for a short comment or an email address so you can remember who to contact for each tunnel.
The field is optional and does not need to be filled out to get a tunnel connection up.
Also cleaned up some of the layout on the tunnel pages and hopefully made it a bit easier to tell what is what.
Fixes#457
* added `maxlength='50'` to the comment/contact field.
50 characters should be enough for an email address or a short comment.
* Allow for spaces in the Tunnel contact/comment field
This adds support for a popular low-cost 5GHz N based AP
Specifications:
- SoC: Atheros AR9344
- RAM: 64MB
- Storage: 8 MB SPI NOR
- Wireless: 5GHz 300 Mbps, 2x RP-SMA connector, 27 dBm TX power
- Ethernet: 1x 10/100 Mbps with 24V POE IN, 1x 10/100 Mbps
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Signed-off-by: Andrew Cameron <apcameron@softhome.net>
Mesh status will show service entries of a remote mesh
node at the top with 0 ETX value. The owning mesh hostname
displays blank across the mesh network.
The root cause is OLSR not propagating the node's hostname due
to the admin assigning a conflicting/duplicate hostname. These
services will no longer show in mesh status.
* Add experimental support for the GL.iNet GL-AR150 - https://openwrt.org/toh/gl.inet/gl-ar150
Mesh networking and tunneling have been confirmed working.
This device has been confirmed capable of operating on channel -1, but /etc/config/wireless has to be manually edited to select this channel.
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150
* www/cgi-bin/perlfunc.pm patched to add UI support for the GL.iNet GL-AR150 - seems like only 18 dBm TX power is possible
* Remove Experimental comments and designate as stable
* Configure Ethernet ports & VLANs for GL-AR150, and update README.md
* Fix misunderstanding re README.md
* Patch Upstream OpenWRT GL-AR150 LAN & WAN LED mapping, configure WLAN LED as mesh linked indicator.
* sysinfo.json additions
lua library additions
Dependent on #389 and #391
Replaces #387
* additional check for nil needed
tested on a node with several very marginal RF links (IP, no host name) and it is working, so far.
also removed the decimal point on the n/lq values, we didn't need 10 places of accuracy. :)
* a couple more small changes
* changed neighborLinkInfo() function in aredn.info to show *all* links, not just RF.
Adds additional info for each RF link (tx/rx_rate, noise, signal)
* Removed redundant function.
Removed functions no longer needed.
Reworked getCurrentNeighbor function to add in the additional RF link info if requested.
10MHz channel width is most commonly used. This default
will minimize how many new users are unable to connect
to a local mesh on first try. In 2GHz use ch -2
as only clear part 97 10MHz channel available and
predominently used.
* wscan can output results as json
* added a page for displaying scan results as json
* updated file permissions with +x
* added endpoint for wifi scan
* Revert "updated file permissions with +x"
This reverts commit 6f0a038334fbacc3f585f0a86fb7d9986a47b7d2.
* Revert "added a page for displaying scan results as json"
This reverts commit 4806ad01b6b717e2e02f248309a0257bb390af23.
* Revert "wscan can output results as json"
This reverts commit 75454e7e790a0457a0846182b0a8a44205772368.
* removed hardcoded device name
* exposed freqlist through the api
* moved signal.json code into the api
* old signal page uses /api?page=chart
* removed signal.json
* chart has targets for realtime and archive
* updated old signal page to use new api
* wscan can output results as json
* added a page for displaying scan results as json
* updated file permissions with +x
* added endpoint for wifi scan
* Revert "updated file permissions with +x"
This reverts commit 6f0a038334fbacc3f585f0a86fb7d9986a47b7d2.
* Revert "added a page for displaying scan results as json"
This reverts commit 4806ad01b6b717e2e02f248309a0257bb390af23.
* Revert "wscan can output results as json"
This reverts commit 75454e7e790a0457a0846182b0a8a44205772368.
* removed hardcoded device name
* exposed freqlist through the api
This reverts commit d5be7814b3.
Auto Distance is not ready for a release and will be
reintroduced afterwards. Added logic to reset '0' distance
to 60km so tower nodes will continue to respond after
upgrade if running the experimental auto distance
Add option for hap ac lite to select which band to
use for LAN AP option, 2GHz or 5GHz. Also, ensure
all wireless cards are defined when disabled to
prevent default wireless config options.
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
Installation:
Flash factory image through stock firmware WEB UI
or through TFTP
To get to TFTP recovery just hold reset button while powering on for
around 4-5 seconds and release.
Rename factory image to recovery.bin
Stock TFTP server IP:192.168.0.100
Stock device TFTP adress:192.168.0.254
enable passwords with virtually any character, enable SSIDs
with virtually any character. ensure ap is always
encrypted to give operator control of client access and
license compliance. Remove (week) WEP encryption option.
* aredn: hAP ac lite enable 5GHz LAN Access Point
enable ability to bridge LAN physical ports with wireless
LAN Access Point capability. On dual band hAP ac lite,
used in parallel with mesh RF on 2GHz. Enables future
features on single band devices to turn off mesh RF and
repurposed for mesh LAN Access Point.
closes: #215
Also removed the description block from the mesh page if the description has not been set.
(there was a small grey area before, even with no description set)
* bugfix: Check for existing hostnames on the network in DHCP reservations
fixes#216
*additional check for existing hostname when creating new DHCP lease.
checks hosts_olsr file if entered hostname already exists or not on the connected network(s).
outputs info saying such and gives advice to prefix hostname with callsign.
* change to use =~ /\s$host\S/i
* Reworded warning message
* moved the position of the hostname check to only when you click "add" on the DHCP leases page.
this stops it checking all the previously entered hostnames.
* initial commit
* feature: advanced configuration page
fixes#230
* add help page updates
* added menu links to perlfunc.pm
* add default value for serverpath
* move "Reset to Firstboot" button from setup page to advancedconfig page
* secure page
minor ui changes
* center the help icon
* implement callback capabilities pre/post
* hardening uci calls to prevent command injection attacks
* moved settings to custom aredn uci file
* resolve shellcheck warnings
* feature: Provide firmware file advice for uploading firmware files
also reduces page size by removing unnecessary style info on option tags.
fixes#206
* update for Mikrotik filename exceptions
* correct download .list file name
* add support for cpe devices
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
Correct read_postdata() to only accept files from pages that are
specifically designed to accept files.
This should be limited to authenticated pages only.
SCS-2017-001
Change-Id: Ic40f19a88e543d83a8097abcd4e7254ccea90f49
During creation of the backup file some errors may be masked.
While this isn't confirmed to be the cause of any known report it
is possible users have in the past experienced this and we just
couldn't see it.
Change-Id: I12136b7c53aabfb243445170b91c69928206bb1b
Make supporttool clean up its temporary folder when done
executing.
ref AREDN->ticket:204
ref AREDN->ticket:44
Change-Id: Ibc0bc1205ce8f66d382fad238877c881f2a21e3b
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>
Allows the supporttool to generate support files
when run from the shell for times that it may
be required when the web interface is offline.
Change-Id: I696289ea10c2e5b57f3e93d81ec7004469c4bba0
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
Adjust power levels to reflect what is in the board.info
This was likely a typo when I put the device in the first time.
In addition adjust naming to match Ubiquiti device rename.
{{{
board.sysid=0xe4e5
board.cpurevision=0x00001122
board.name=PowerBeam M5
board.shortname=P5B
board.subtype=400
board.netmodes=7
board.hwaddr=0418D65EEB39
board.reboot=40
board.upgrade=150
board.phycount=1
board.phy.1.maxmtu=2024
board.phy.2.maxmtu=2024
radio.1.name=
radio.1.shortname=
radio.1.bus=ahb
radio.1.subsystemid=0xe4e5
radio.1.subvendorid=0x0777
radio.1.txpower.max=26
radio.1.txpower.offset=4
radio.1.antennas=2
radio.1.def_antenna=1
radio.1.antenna.1.id=1
radio.1.antenna.1.name=400
radio.1.antenna.1.gain=25
radio.1.antenna.2.id=2
radio.1.antenna.2.name=Feed only
radio.1.antenna.2.gain=3
}}}
ref AREDN->ticket:185
Change-Id: I71d2a944b6abb9e30862d7ada7f46b80df2c731c
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
User UI login uses http-basic authentication which is just base64 encoded
for transit but not encrypted.
This is a long standing error in documentation.
Change-Id: Ib3e49533b2acb32496e5e2a9b9b93e1436bc5f0d
Provide HTTP header to search engines not to index the page.
Eventually we will likely want to add nofollow and a robots file
but first we need to get this pushed out and into search engine hands
so they delist the entires that may already be cached.
Change-Id: I47a68fcc8fb69c43c3f1bbe2b8a04a3e8d51571a
Tim Wilkinson