|Wireless (Interfaces) [main menu]|
|Transmit Environment (Fragments)||If the frame size is larger than the threshold, the radio NIC will break the packet into multiple frames, with each frame no larger than the threshold value. This is done to avoid needing to retransmit large frames in the presence of RF interference. The bit errors resulting from RF interference are likely to affect a single frame, and it requires less overhead to retransmit a smaller frame rather than a larger one.|
|Wireless Sensitivity||Adjusts the receive sensitivity of the radio to 3 different levels between 1, 2 & 3. 1 is the most sensitive, 3 is the least. At present, this setting is ignored on Atheros-chip radios|
|Minimum Signal to Block Node||The AODV routing system can use the signal level reported by the radio card firware as a way to determine the signal level of a particular mesh node and block that client accordingly. This value determines at what value and below that the nodes will be blocked. The typical setting is around 90. and is on a scale of 0-255.|
|Enable Signal Testing||
There are 2 types of signal testing that can be used in the mesh. If this setting is enabled the system will use the minimum signal setting set above and will compare that value to the reported signal level from the radio card firmware. If the signal falls below this value the routing system will automatically block the node and will display as blocked in the current mesh node status page.
If this setting is left off the system will use a ping checking system every 30 seconds to see if the nodes reported by AODV within one hop are responding to the ping. If they do not after 5 minutes they will be automatically blocked. This is shown the the /hj/reporter system as (0%@10), (0%@20), etc... The 10, 20 means how many ping checks that node has missed x10.
If it is working correctly it will be displayed as (100%@0)
To completely disable signal testing, set the minimum signal to 0 and set this setting to Yes. This will look like (0%@0) in the /hj/reporter system
|Retest Signals for Blocked Nodes||If a node is blocked you can set how long the system waits before it rechecks the signal strength to add the node to the mesh again.|
|Node Cell ID||
Cell ID is used to set a unique number to represents the backhaul tunnel and wireless subnet for each node.
This must be unique for each unit can can be found by looking at the 3rd octet of the IP addresses assigned by the wireless system. 192.168.x.1
Therefore, you can only have up to 255 nodes on a particular mesh system. If you need more nodes, consider splitting the system into micro meshes.
This does not apply to the wired (eth0) side.
|Wireless IP||This is the factory-assigned specified IP address that is used to route traffic throughout the mesh. It must be in the form 1.x.x.x and must be unique for each node. Do not change this address without specific factory approval!|
|Mesh ID||Mesh ID is the radio ESSID that is used to connect to the mesh. It will be displayed in the radio beacon unless turned off by hiding the SSID in the security menu.|
Mesh: This will put the system into Infrastructure mode (AP mode) and allow the system to make WDS connections (with Prism radios) which join the mesh nodes together wirelessly.
|Data Rate||The default setting is auto. You can manually force the data rate to various fixed rates if needed for your situation (e.g. long-distance links in heavy interference), but on close-in networks this is not usually necessary and can actually hurt your network performance.|
|Channel||Specifies the channel on which the the system will operate. In the USA the choices range between channel 1 (2.412 GHz) & channel 165 (5.625 GHz) or less with certain radios|
|Power||sets the output power of the radio interface. In the Qnode system that range is between auto & 200mW.|
|RTS||users can set a maximum frame length threshold whereby the radio NIC will activate RTS/CTS. For example, a frame length of 1,000 bytes will trigger RTS/CTS for all frames larger than 1,000 bytes. The use of RTS/CTS alleviates hidden node problems, that is, where two or more radio NICs can't hear each other and they are associated with the same access point.
default is 250
Yes / No: enables or disables the WEP key system. Unless you want to run a resticted network you can specify that here, but for system for the public this should typically be left off.
If a string it should be 13 characters long and prepend the string with "s:" (e.g. s: wepkey123457)
Back to Top ++