* api: revise localhost function
Revise getLocalHosts() so it doesn't report unwanted hosts.
getLocalCnxType() is no longer needed.
* include new iplookup function too
* incorporate Eric r1de values for getCurrentNeighbors
* use alternative for mac2host()
* get actual wlan interface for arp query
* tested on dualband radio
Tested on dualband radios with active clients on both Mesh RF and Wifi
AP.
* add more error checking
* fix iplookup match
It is possible to have 2-digit "mid" prefixes. Fixes match to account
for 2 possible digits.
* tighten up code
* add extra info values for Eric r1de
* 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
* Remove local.mesh suffix from CurrentNeighbor hostname
* Uppercase hostname for consistency
* Make hostname lowercase for consistency with Local Hosts display in newui
* fix: Local Alert File Read All
Read the entire local_message file rather than just the first line.
* fix: Local Alert File Read All
Also fix the issue with empty alert files showing empty newui alert
dialogs.
* Format Uptime as String
Format uptime as a string with values for days, hours, minutes, and
seconds.
* Format uptime as String
Change code to use the secondsToClock function in utils.lua
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
dman776