Post date: Jul 4, 2011 2:40:45 PM
Extra features
Additional functions are set here.
Hybrid protocol:
Set to YES allows the take up of additional protocols as they become available.
Band extension:
Recommended set to NO. On some networks setting YES will allow seamless roaming between nodes.
Bandwidth revenue:
Will enable future features for brokering traffic between other nodes.
CCTV USB webcam:
Check this to YES if you want to use a webcam. Find the webcam images at http://1.wiana.ip.number:10192/singleframe.html (replace 1.wiana.ip.number with YOUR node's actual Wiana Certifified IP address)
Max wired clients:
Limit the number of local clients that can connect via the Ethernet interface
Max wireless clients:
Limit the number of local clients that can connect via the wireless network interface
Mesh nodes to use:
Limit the number of other mesh nodes that this node will talk to within one hop.
DHCP services:
Defaults to YES. Set to "NO" to stop offering DHCP services. Use this setting on a machine that is only working as a repeater.
DHCP nak wrong nets:
Use NO on ad hoc networks that are overlapping their wireless DHCP services and giving confused DHCP leases. Otherwise leave as YES
DNS services:
Defaults to YES. Set to NO to stop offering DNS services over the network. Normally matched with the DHCP service
IPsec:
This option turns the IP Security between nodes on and off.
mesh routing IPsec:
Setting this to YES stops the mesh talking to un-certificated nodes, which can make it hard to get new nodes on the network, but makes the security a lot tighter.
cross mesh IPsec:
Radius only local:
Defaults to YES. When YES the local radius realm is used as set below.
Radius local prefix:
This value is set by the system and should not be changed in normal circumstances. It should be the same as the value shown in brackets.
Lock to realm prefix:
Select a local realm, as defined in the realm manager that this node will use for authentication
twin realm prefix:
Allows a second realm - often used for ticketed realms - see SettingUpTicketedPasswords
Minimum cell signal:
To avoid poor quality links through marginal connections, set this value above zero. The exact value to use will depend upon your network characteristics. Observe signal strengths on the Mesh Monitor (on drop down menu in GUI) or using reporter on the command line. Signal numbers will change between cards and builds, so make sure to set to 0 before upgrading, as otherwise can block all links after an upgrade. In build25, the meshboxes test connections to see if they are stable or not, and will block links that are not good. However, minsig can be used to augment this automatic blocking, or to force links to better quality signals. See BlockNode.
Mesh watchdog:
The mesh watchdog is only suitable for use in well saturated networks, where the node should expect to see a lot of neighbours. If no other mesh nodes can be seen the watchdog assumes that connectivity is lost, and goes into a network search, to try to re-establish a connection as a client, so that it can download its settings and get back on the mesh.
Internal watchdog:
Set to YES this watchdog will reboot the machine if processes lock-up.
Wireless sensitivity:
Adjusts the sensitivity value for receiving on supported network cards.
Wireless transmit:
into clean
into noisy
adjusts fragmentation thresholds which can improve performance in noisy environments, but will reduce performance if set to noisy in a clean environment
Client Roaming:
Client decides
AP decides
Manual
Specifies behaviour of clients when they are in range of two APs
Mesh with any ESSID:
Determines whether mesh nodes will communicate with APs with a different ESSID. Can cause problems if in range of APs which are not MeshAPs. Meant for nodes at border of two meshes to link them together.
Wormhole capable:
Wormholes are VPNs that link meshes together over the internet. See WormholeHubs.
Wormhole hub address:
Enter the Wiana IP or private LAN address of the hub here
Wormhole key:
Each node needs to enter the shared key here
Wormhole type:
Internet wormholes use the Wiana IP, LAN wormholes go over a private network. P2P not supported yet.
Wormhole transport:
Use UDP unless your network blocks it, in which case use TCP