Re: [sugar] 65-node simple mesh test (and counting... ;-)

John Watlington wrote: One interesting note is that the suggested routing algorithm for 802.11s is a combination of reactive and proactive routing (unlike our current one, which is solely reactive). Perhaps that provides the adaptation necessary for the mesh to work ? If you refer to

Re: [sugar] 65-node simple mesh test (and counting... ;-)

On Tue, May 13, 2008 at 12:19 PM, Polychronis Ypodimatopoulos [EMAIL PROTECTED] wrote: John Watlington wrote: One interesting note is that the suggested routing algorithm for 802.11s is a combination of reactive and proactive routing (unlike our current one, which is solely reactive).

Re: [sugar] 65-node simple mesh test (and counting... ;-)

Hi Greg A couple of points in clarification... On Fri, May 9, 2008 at 3:01 PM, Greg Smith (gregmsmi) [EMAIL PROTECTED] wrote: Hi Polychronis, Thanks for sharing the results. Did you use a wireless AP or active antenna? If you can include a few details on that it will help. Can you also

RE: [sugar] 65-node simple mesh test (and counting... ;-)

; Sugar ml Subject: Re: [sugar] 65-node simple mesh test (and counting... ;-) Hi Greg A couple of points in clarification... On Fri, May 9, 2008 at 3:01 PM, Greg Smith (gregmsmi) [EMAIL PROTECTED] wrote: Hi Polychronis, Thanks for sharing the results. Did you use a wireless AP or active

Re: [sugar] 65-node simple mesh test (and counting... ;-)

Michael Stone wrote: Data Questions: * Are the measurements used to make the display of 'distributions of profile arrival rate vs. time' produced from timestamps of profile arrival as recorded by all the laptops or by some smaller set of 'sentinels'? All XOs got synced clocks (by

RE: [sugar] 65-node simple mesh test (and counting... ;-)

Hey Pol, what format is the data in, is this pcap? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Polychronis Ypodimatopoulos Sent: Friday, May 09, 2008 3:35 PM To: Michael Stone; OLPC Development Subject: Re: [sugar] 65-node simple mesh test

Re: [sugar] 65-node simple mesh test (and counting... ;-)

Bill Mccormick wrote: Hey Pol, what format is the data in, is this pcap? yes, it's libpcap. Saved from wireshark. I just tested the file and successfully loaded in wireshark ;-) Pol The raw capture is here: http://lyme.media.mit.edu/cerebro/capture-1

RE: [sugar] 65-node simple mesh test (and counting... ;-)

Hi Greg, Greg Smith (gregmsmi) wrote: Thanks for sharing the results. Did you use a wireless AP or active antenna? No access points or active antennas were involved. This is a simple mesh network test. If you can include a few details on that it will help. Can you also include the XO

RE: [sugar] 65-node simple mesh test (and counting... ;-)

address. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Polychronis Ypodimatopoulos Sent: Friday, May 09, 2008 3:35 PM To: Michael Stone; OLPC Development Subject: Re: [sugar] 65-node simple mesh test (and counting... ;-) Michael Stone wrote: Data

RE: [sugar] 65-node simple mesh test (and counting... ;-)

Development' Subject: RE: [sugar] 65-node simple mesh test (and counting... ;-) It does look like the NM code will select APs over mesh... I bet this plays havoc with IP changing between link local addresses and DHCP addresses. Did you expect over half of the packets in your data file

Re: [sugar] 65-node simple mesh test (and counting... ;-)

Bill Mccormick wrote: Pol, I forgot to ask, do you have a tool that parses the messsages and counts up etc.? Wireshark only parses the 1st mac header. Heh, you 're putting your finger on the wound now! The main reason I did not attempt a wireshark plugin for Cerebro yet is because I

Re: [sugar] 65-node simple mesh test (and counting... ;-)

Bill Mccormick wrote: It does look like the NM code will select APs over mesh... I bet this plays havoc with IP changing between link local addresses and DHCP addresses. This is partly because of the scalability limitations of the existing collaboration model in a simple mesh. However,