> Thanks everyone for your help on this. I am almost there, just
> finding it very hard to get a mesh of 3 nodes
> that will sync up. I have compiled in the wing-extras, so now I have
> wing_status, and that helps a lot.
Uhm, I should probably add that script to the main wing package.
> I can get hosts, I can get links, but I can't seem to get routes, and
> without routes I can't even ping.
> Is there any special firewall rules that have to be put in place to
> make this work?
Coud you post the output of wing_status
> Roberto, by "goodness" I am trying to find the figure that describes
> how good the link is, in
> terms of speed, minimum packet loss, things like that.
You can get this info using the following handler:
read_handler lt.links
which list the links in the network followed by their metric. The metric
is computed using ETT, then higher values corresponds to bad links.
The metric itself is the amount of time (in usec) spent in average to
send a 1500-bytes long packet over that link.
The last part of the output produced by wing_status contains detailed
information about each neighboring INTERFACE. For example:
Broadcast statistics (1):
6.35.170.122:1 06-0C-42-23-AA-7A seq 1302511688 period 10000 tau 100000
sent 5799 last_rx 0.206923360
6.35.170.122:1 06-0C-42-23-AA-7A [ 12 60 90 100 19 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 12 1500 70 100 24 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 18 1500 70 100 19 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 24 1500 50 100 24 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 36 1500 50 70 23 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 48 1500 40 70 30 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 72 1500 40 40 28 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 96 1500 20 40 26 160 ]
6.35.170.122:1 06-0C-42-23-AA-7A [ 108 1500 30 50 29 160 ]
The stuff above refers to a link between the first interface on the local
node and the first interface of the neighboring node 6.35.170.122.
First line:
6.35.170.122:1 06-0C-42-23-AA-7A seq 1302511688 period 10000 tau 100000
sent 5799 last_rx 0.206923360
Interface id and mac address followed by some internal statistics
(sequence number, broadcasting period and smoothing factor),
the number of probes received, and the amount of time (in secs) since a
probe was received.
Than you have some statistics for each probe sent over this link. Wing
periodically
sends probes at different rates and with different packet lengths. By
default wing sends
one short probe (60 bytes) at the base rate (6 mbps) and one long probe
(1500 bytes)
at each of the supported rates. This information is between the [], so
for example:
6.35.170.122:1 06-0C-42-23-AA-7A [ 12 60 90 100 19 160 ]
should be read as follows:
1) the first number (12) is the data rate multiplied by 2 (this is how
the internal driver represents rates)
2) the second number is the probe length (60)
3) the third number if the packet delivery rate FROM the local node TO
the neighbor
4) the forth number is the packet delivery rate FROM the neighbor to the
local node
5) the last two numbers are respectively the link RSSI and the link
noise levels
> Once I get this going, I will write it up and post it back to the group.
This would be great. If it is ok for you I will add that information to
the wiki.
R.
_______________________________________________
Wing mailing list
Wing@create-net-ml.org
http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing
No comments:
Post a Comment