Meshlium Manager System provides an easy way to monitor Meshlium's mesh networks. Each Meshlium can configure its manager to send custom data to a central server, and the interval this data will be sent. Even more, the web manager let you custom which data will send to central server. Central server may be any Meshlium, and different Meshlium may have configured different central servers.
Configure this feature is as simple as moving to Remote Server tab. Once there two sub menus will be displayed, sub menu Send Data and Acquired Data. The Send Data sub menu configures the meshlium behaviour to send data to a central server, and which data should be sent.

To configure sending data to a central server, we must configure ip addresses of the Meshlium that will role as central server. We may configure also a sending interval from 1 minute to 59 minutes. Whit that simple configuration, Meshlium will send information to the selected ip each interval. Just doing so won't make our Meshlium send any data to central server because no information has been selected already, sending data must be allowed too. Only selected information will be sent to central server, so that each Meshlium may work with different behaviours for minimizing  the bandwidth consumption or security tasks. The manager will gather all the system information that has been selected to send to central server and send it by itself.
Acquired data sub menu configure the behaviour of the manager when receiving info from other Meshliums. If  it is configured to receive data, it will  store data information. In Acquired data sub menu is possible to have an overview of all the information received from other Meshliums.



With the Meshlium API is possible parse and manage information stored from Meshliums. It uses this information to display mesh info of each node and interconnection within mesh network.

But any other application in Meshlium or any Plugin for the manager may use this information, without having to worry about mesh topology, gathering system information and sending or receiving system information to any other Meshlium in the net, the web mnanager already do it itself.

This is a real Meshlium's received data file.

 

Recived data
GPS on
Latitude 41.680513333333Longitude -0.8861965Soft Version meshlium-2008.137-13Using key noSend data to brothers each 59 mInterconected interfaces
eth0->ath0
eth0 up
eth0 ip 192.168.1.205
eth0 gateway 192.168.1.1
ath0 up
ath0 ip 10.10.10.5
ath0 gateway 10.10.10.255
ath0 mode ad-hoc
ath0 channel 6
ath0 abg 2
ath1 down
ath1 ip
ath1 gateway
ath1 mode
ath1 channel
ath1 abg
ath0 see_nets num=4 //meshlium-ap 02:0B:6B:86:EB:36 6 28/70 //meshlium-ap 02:0B:6B:86:EB:36 6 23/70 // 02:0B:6B:86:EB:36 6 6/70 //
ath1 see_nets
current cell ath0 essid meshlium-ap
current cell ath0 ap current cell ath0 channel 6
current cell ath1 essid
current cell ath1 ap
current cell ath1 channel
clients ath0 ADDR AID CHAN RATE RSSI DBM IDLE TXSEQ RXSEQ CAPS ACAPS ERP STATE MODE//
00:0b:6b:86:eb:36 0 6 36M 22 -73 0 22962 51312 IS 0 1 Normal WME//00:0b:6b:86:e8:20 0 6 12M 20 -75 0 602 6768 IS 0 1 Normal WME//
00:0b:6b:80:c8:8e 0 6 1M 5 -90 0 10065 13072 IS 0 1 Normal WME//
clients ath1
ppp0 down
ppp0 operator
ppp0 country
bluetooth num 0
zigbee down
zigbee file size
Status up
DebugLevel 0
IpVersion 4
AllowNoInt yes
TosValue
Willingness 7
UseHysteresis no
HystScaling
HystThrHigh
HysThrLow
Pollrate
NicChgsPollInt
TcRedundancy 2
MprCoverage
LinkQualityLevel 0
LinkQualityWinSize
LinkQualityFishEye 1
LinkQualityDijkstraLimit 3 3.0
Interfaces ath0
AutoDetectChanges
Ip4Broadcast
Ip6AddrType
Ip6MulticastSite
Ip6MulticastGlobal
HelloInterval 2.0
HelloValidityTime 10.0
TcInterval 2.0
TcValidityTime 10.0
MidInterval 10.0
MidValidityTime 50.0
HnaInterval 10.0
HnaValidityTime 50.0
brothers 10.10.10.2 10.10.10.3 10.10.10.250