|
Wiana
|
Description
|
|
Register nodes
|
 | For
manual registration follow this link and enter the hardware key of the
machine. |
| Alternatively run
wianaregister at the command line of the node.
|
|
|
XX registered
|
·
Click here to see the list of nodes and check in status
|
|
Realm manager
|
·
Use the realm
manager to setup and maintain
users on the network
|
|
Node details
|
|
|
Hardware
Key
:
|
| This
32 character value identifies your node uniquely. To find the hardware
key of a mesh node that you are logged into type
the command hardwarekey
at the command prompt Version: 0 - Build: 24 |
| Major
releases of the MeshAP software are counted in "builds".
This value reports the current build installed on this node |
|
|
Wiana
certified IP
:
|
·
1.214.163.220
| Each
node has a wireless IP number. These start off as random 10.x.x.x
numbers. Once registered WIANA assigns fixed 1.x.x numbers |
| Node
certificate live or Node
certificate ready - hit Make Changes
|
| Each node has a
digital certificate. Once they are live they are used to drive the
encryption and authentication checks between nodes.
|
|
|
Node configuration
|
| Set
the primary wireless communication parameters in this section |
| Node
name: |
| Wiana
reports
will show this node name, which can be easier to remember than the
hardwarekey or IP number
|
|
|
ESSID
:
|
·
Set the ESSID
of the wireless network here.
|
|
Captive portal
:
|
| The
captive portal controls access to services by clients using the
network. Turning it off lets users go straight in to the network
without first reaching a login page. |
| The Old System
setting is a compatibility function for legacy installations. Not
needed in normal circumstances.
|
|
|
Portal mode
:
|
| Fine-tune
the captive portal settings. Both lets guests in freely, and is useful
for early stages, |
| Both
Auth and Open - Allow logins by recognized users and guests |
| Auth
Only - stops guest access. |
| Guest
Access open - Everyone’s a guest? |
| No Access - Node is
closed - e.g. use this for maintenance periods
|
|
|
Portal timeout
(hours):
|
| Set
the time that each login session lasts for. |
| Portal
style: There are a variety of kinds of portal that you can set
here: |
·
WIANA based
·
nocatsplash
·
ticketed
·
remote
|
|
Ticket timeout
:
|
·
When using single use tickets, set the time they give on the
network here in minutes
|
|
GUI
:
|
·
Turn the internal graphical user interface on the MeshAP
on or off here. Turning this off preserves system resources.
|
|
PCMCIA support
:
|
·
Use this option for installation with a PCMCIA wireless
card; turn it off to save loading unnecessary drivers
|
|
Atmel support
:
|
| Use
this option for to load the Atmel USB
drivers, turn it off to
save unnecessary loading faster boot up: |
| This option skips
some checks during booting, saving about 10 seconds
|
|
|
First interface Wireless mode
:
|
·
Set the mode between adhoc and infrastructure. Beware that a
node on one mode can't talk to a node on the other mode, so change with
care, and work from the outer reaches of the network back to the centre
when making changes.
|
|
First interface Wireless Channel:
|
·
Set the channel carefully and ensure that there are other
machines within range that can communicate on this channel too.
|
|
WEP
:
|
·
Infrastructure
mode can support WEP
, but ad-hoc mode does not. This is currently supported on Prism adapters
only.
|
|
WEP
key:
|
·
The WEP
key must be shared with other clients using this cell
|
|
Second
interface Wireless mode
:
|
·
Secondary interface settings apply to twin radio nodes.
Beware that a node on one mode can't talk to a node on the other node, so
change with care, and work from the outer reaches of the network back to
the centre.
|
|
Secondary ESSID
:
|
·
Set the ESSID
of the second wireless network here.
|
|
Second interface Wireless Channel
:
|
·
Set the channel carefully and ensure that there are other
machines within range that can communicate on this channel too.
|
|
WEP
:
|
·
Infrastructure
mode can support WEP
, but ad-hoc mode does not. Currently supported on Prism adapters only
|
|
WEP
key:
|
| The
WEP
key must be shared with
other clients using this cell |
| 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.
|
|
CTV USB
web cam:
|
|
|
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.
|
|
Always mesh IPSEC
:
|
·
Setting this to YES stops the mesh talking to
un-certificated nodes; this can make it hard to get new nodes on the
network, but makes the security tighter.
|
|
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. |
| Lock
to realm
prefix: |
| Select a local realm
, as defined in the realm manager that
this node will use for authentication
|
|
|
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
).
|
|
Mesh watchdog
:
|
·
The mesh watchdog is only suitable for use in well-saturated
networks, where the node should expect to see a lot of neighbors. 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.
|
|
Wormhole capable
:
|
·
Wormholes are VPNs that link meshes together over the
internet. See Wormhole
Hubs
.
|
|
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
|
|
Traffic Shaping
|
| Shaping
values set here define the parameters for managing bandwidth at the
node. |
| Mesh traffic is the
data passed through this node from carried on behalf of other nodes in
the mesh. Routing traffic is the data sent between nodes to establish
routes.
|
|
|
enable shaping
:
|
·
Turn Shaping on or off
|
|
optimize traffic
:
|
·
Optimization should improve performance
|
|
eth
bandwidth
:
|
·
Define the speed of the Ethernet network
|
|
wlan0 bandwidth
:
|
·
Define the speed of the wireless network
|
|
mesh down: mesh up: mesh down burst: mesh up burst:
|
·
Mesh upload and download rates are set here, they can be
exceeded up to the value of the burst limit if there is spare capacity
available on the network.
|
|
routing down: routing up: routing down burst: routing
up burst:
|
·
Routing bandwidth settings are important to ensure that the
network can remain intact.
|
|
Client
Shaping
|
| Client
shaping defines the rules that are used to deliver bandwidth to users
of the mesh. |
| Users
can have one of four classes, Owner, Public, Member, and Unknown.
These values relate to the class defined in their Realm user settings. |
| Client
shaping rules are applied on a per user basis. |
| Each class of user
has rules for their bandwidth rights, defined separately for upload
and download. In addition to their regular bandwidth they can also use
a limited number of "burst" events, where they request data
at a higher rate for a short period. This improves interactive
response without giving away too much bandwidth on an ongoing basis.
|
|
|
Burst settings
allow greater bandwidth use if spare capacity is available.
|
| unknown down:
|
| unknown up:
|
| unknown down burst:
|
| unknown up burst:
|
| public down:
|
| public up:
|
| public down burst:
|
| public up burst:
|
| member down:
|
| member up:
|
| member down burst:
|
| member up burst:
|
| owner down:
|
| owner up:
|
| owner down burst:
|
| owner up burst:
|
|
|
Firewalling
|
| Firewall
settings are applied in relation to user class. By default higher
classes of users don't get blocked. |
|
|
Apply
block to Owner users:
Apply block to Member users:
Apply block to Public users:
Allow FTP port 21:
Allow SSH port 22:
Allow TELNET port 23:
Allow SMTP port 25:
Allow HTTP port 80:
Allow POP3 port 110:
Allow RPC port 111:
Allow HTTPS port 443:
|
|
|
Total
block on incoming wired:
|
·
This locks down a wired LAN that is connected via the mesh,
to make a high security fire walled connection.
|
|
Root password
:
.
|
·
Set the root password here.
·
Privacy cipher:
·
You can use this value to secure the data on your mesh
|
|
Mesh Port
mappings:
|
·
These options will allow port mappings - not yet
implemented
|
|
Bluetooth
.
|
·
These features apply to the Bluetooth
meshing functions, which are available as a separate
commercial module
|
|
Bluetooth
:
|
·
Enables the Bluetooth
functions
|
|
Bluetooth
|
