mirror of https://github.com/aredn/aredn.git
bugfix: Fixed README and comment typos (#220)
* typos * Update README.md * Update aimer
This commit is contained in:
parent
134a135784
commit
6f9a8327cb
|
@ -22,7 +22,7 @@ the earlier an issue is found, the faster an enhancement will be
|
|||
turned into a release.
|
||||
|
||||
Here is a summary of significant features added since 3.18.9.0
|
||||
was releaed:
|
||||
was released:
|
||||
|
||||
* Locked to Openwrt 18.06.1
|
||||
|
||||
|
|
|
@ -27,7 +27,7 @@ $RSSI_3=-73;
|
|||
$RSSI_2=-80;
|
||||
$RSSI_1=-94;
|
||||
|
||||
# LED Set Wrappe
|
||||
# LED Set Wrapper
|
||||
sub SetLED {
|
||||
($fh, $state ) = @_ ;
|
||||
print $fh $state ;
|
||||
|
|
|
@ -77,10 +77,10 @@ provided through those nodes.
|
|||
<li><strong>WiFi Scan</strong> displays a list of other 802.11 signals that the
|
||||
node can see and only of the same bandwidth. The 802.11 signals include
|
||||
Access Points (AP), neighbor nodes (connected ad-hoc stations), and other mesh networks
|
||||
(foriegn ad-hoc networks). The AREDN mesh is created on top of an 802.11 'ad-hoc' network.
|
||||
Consequently when multiple ad-hoc networks are visiable to each other (different SSID or
|
||||
(foreign ad-hoc networks). The AREDN mesh is created on top of an 802.11 'ad-hoc' network.
|
||||
Consequently when multiple ad-hoc networks are visible to each other (different SSID or
|
||||
channel), the 'network' is displayed and not individual nodes (stations). There is also an
|
||||
automatic scan mode. It is not recommend to run a wifi scan continously because this will degrade mesh
|
||||
automatic scan mode. It is not recommend to run a wifi scan continuously because this will degrade mesh
|
||||
performance. A wifi scan transmits queries on all channels to discover other devices.<br><br></li>
|
||||
|
||||
<li><strong>Setup</strong> takes you to the setup pages of the web
|
||||
|
@ -236,7 +236,7 @@ ETX should be interpreted with care. From a quality perspective, the ETX for Re
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Transmitted Mbps (TxMbps) is calculated with the formula (TxMbps = rate * EWMA) where rate is the 802.11 data rate in use by the transmitter and EWMA is the Exponetially Weighted Moving Average or the current time weighted chance that a packet at this rate will reach the remote station. If no traffic is being routed to the Neighbor, this value may be '0' until data is available to measure and determine the optimal settings. For further details: <a href='http://wireless.wiki.kernel.org/en/developers/documentation/mac80211/ratecontrol/minstrel'>Rate Control Algorithm</a>
|
||||
Transmitted Mbps (TxMbps) is calculated with the formula (TxMbps = rate * EWMA) where rate is the 802.11 data rate in use by the transmitter and EWMA is the Exponentially Weighted Moving Average or the current time weighted chance that a packet at this rate will reach the remote station. If no traffic is being routed to the Neighbor, this value may be '0' until data is available to measure and determine the optimal settings. For further details: <a href='http://wireless.wiki.kernel.org/en/developers/documentation/mac80211/ratecontrol/minstrel'>Rate Control Algorithm</a>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
@ -341,7 +341,7 @@ ie: "This device is maintained by (callsign) Please contact email@address for mo
|
|||
<em>This is completely optional</em>. There are no character restrictions in the field.<br>
|
||||
The maximum length allowed is 210 characters.<br>
|
||||
HTML tags simply will not work.<br>The description displayed on the main status page is
|
||||
automatically word-wrapped at about 70 charaters or so, and shouldn't split a word in the middle.
|
||||
automatically word-wrapped at about 70 characters or so, and shouldn't split a word in the middle.
|
||||
</p>
|
||||
<p>
|
||||
The <strong>Mesh RF</strong>, <strong>LAN</strong>,
|
||||
|
|
Loading…
Reference in New Issue