Mitch,
Nandblaster is a blast! We updated 29 XOs in less than 30 minutes
(most in less than 20 minutes).
Just one XO froze (two times), but this unit seems problematic anyway.
I am attaching the stats for the other 28.
There is a minor caveat (that is not actually related to the
nandblaster):
Hi Paul,
Just one XO froze (two times), but this unit seems problematic anyway.
I am attaching the stats for the other 28.
There is a minor caveat (that is not actually related to the
nandblaster): Once you finish updating the XO that will be replicated
it woud be useful to put
run the tests and interpret
the results at UFF (Brazil).
But of course, this agenda may change in the face of other, more
urgent needs. So, just let me know how can I help now and in the
future.
My best regards,
Ricardo Carrano
___
Devel mailing list
On Sat, Dec 20, 2008 at 1:01 PM, Ben Lau xben...@gmail.com wrote:
On Mon, Nov 24, 2008 at 8:02 PM, Ricardo Carrano carr...@laptop.org
wrote:
Hi,
2008/11/24 Ian Daniher it.dani...@gmail.com:
Hello all,
I've been asking on #olpc-devel the last few days, trying to figure out
how
work with collaboration
(Ricardo Carrano?)
Again, WOL works as it is supposed to be. The WOL filter wakes up the laptop
when it receives a frame destined for a multicast address that the network
adapter listens for. That means that as we stand right now the XOs will wake
up on reception
Hi,
2008/11/24 Ian Daniher [EMAIL PROTECTED]:
Hello all,
I've been asking on #olpc-devel the last few days, trying to figure out how
to connect my XO simultaneously to both a mexh network and to an AP.
My goal is to have the same XO able to surf the internet and ssh into meshed
XOs. Whether
On Thu, Nov 20, 2008 at 9:15 AM, Peter Robinson [EMAIL PROTECTED] wrote:
So is there a reason p20 isn't in use? Or is there no requirement for
the features/fixes it has?
p20 does not fix bugs and its new features are currently under test
and development (on the driver side). So, the recommended
Hi!
For differences between firmware releases:
http://dev.laptop.org/pub/firmware/libertas/RELEASE_NOTES.
The current recommended firmware release is 22.p18.
Cheers!
Ricardo Carrano
On Wed, Nov 19, 2008 at 5:59 PM, Peter Robinson [EMAIL PROTECTED] wrote:
Hi All,
Quick query on the libertas
On Wed, Nov 19, 2008 at 8:37 PM, S Page [EMAIL PROTECTED] wrote:
Ricardo Carrano wrote:
For differences between firmware releases:
http://dev.laptop.org/pub/firmware/libertas/RELEASE_NOTES.
The current recommended firmware release is 22.p18.
Nice, I added these to the http://wiki.laptop.org
Hi Mitch!
On Wed, Oct 22, 2008 at 7:01 AM, Mitch Bradley [EMAIL PROTECTED] wrote:
I just achieved a mesh throughput rate - XO to XO - of 2.8 MBytes/sec using
multicast with TTL = 1. That's twice as fast as the best I was able to do
through the Linux driver, using the same parameters.
I did
Hello all!
I need help understanding two things regarding the wpa supplicant on the XO.
1 - The init process:
If you boot your XO and check the running wpa processes, here is what
you'll see:
# ps aux | grep wpa
root 1310 0.1 0.7 5444 1848 ?S23:46 0:00
4) Mesh problems - my sense is that you are all pretty aware of those issues.
I think we should start looking into software-level mesh protocols using
the libertas thin firmware. This is not a solution to this problem, but
it will at least move us to a place where we can have collaborative
On Wed, Sep 24, 2008 at 9:20 PM, Gary C Martin [EMAIL PROTECTED] wrote:
On 25 Sep 2008, at 01:00, Martin Langhoff wrote:
I agree with Albert's proposal - Newcomers to the Wellington test team
open too many apps all the time - and render their machines unusable
through memory pressure. From
Hi,
Have you tried removing your old/previous network configuration?
This can be done in the Control Panel Network Discard network history
Cheers!
Ricardo
On Sun, Sep 21, 2008 at 2:10 PM, [EMAIL PROTECTED] wrote:
I recently did a reinstall of 8.2-760 on my
MP G1G1 XO. The new install
On Mon, Sep 22, 2008 at 9:52 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote:
Have you tried removing your old/previous network configuration?
This can be done in the Control Panel Network Discard network history
I realize this is the politically correct response to AP connect
problems.
But
On Wed, Sep 17, 2008 at 1:26 AM, John Gilmore [EMAIL PROTECTED] wrote:
Ricardo Carrano said:
There are technical challenges in the way, but OLPC should keep
pushing this for the benefits it will bring. It seems a perfect fit
with the Mission.
Mesh and the Marvell WiFi chip have been two
Hi!
It seems that B2s do not have the serial recovery connector. I opened
one that seems really bricked (when turned on only the power light is
on, and removing battery and AC for some time do not fix it) and found
just the place holder for the connector. Is that a way to save this
B2?
By the
!
Cheers!
Ricardo
On Tue, Sep 16, 2008 at 1:26 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
Message: 5
Date: Tue, 16 Sep 2008 11:58:14 -0400
From: Ricardo Carrano [EMAIL PROTECTED]
Subject: Recovery connector?
To: Devel [EMAIL PROTECTED]
Message-ID:
[EMAIL PROTECTED]
Content-Type: text
Hey Richard!
On Tue, Sep 16, 2008 at 5:39 PM, Richard A. Smith [EMAIL PROTECTED] wrote:
Ricardo Carrano wrote:
confirmed that this B2 was updated to a recent build with q2e14. There
you go.
Let's see if the team have good skills with an iron...
Ricardo,
I'm sorry you missed my post
On Tue, Sep 16, 2008 at 6:38 PM, Richard A. Smith [EMAIL PROTECTED] wrote:
Ricardo Carrano wrote:
Thank you for your care and advice.
This B2s belongs to a University in Rio, that actually has 23 B2s.
They are pretty useful devices for networking tests and I am helping
this group to mount
On Tue, Sep 16, 2008 at 6:57 PM, Pia Waugh [EMAIL PROTECTED] wrote:
Hi all,
quote who=Edward Cherlin
This would be even more useful as the basis for an article or
editorial in one or more of the computer magazines or Web sites, or a
fact-filled press release. All of the media people I have
John,
On Tue, Sep 16, 2008 at 9:46 PM, John Gilmore [EMAIL PROTECTED] wrote:
[I posted bug #8524 re lease activation not working on AP's.]
Another mechanism that only works on Mesh is sharing under a tree.
It's perfectly feasible for four or five kids with laptops, all
sitting under a tree,
Martin,
On Fri, Sep 12, 2008 at 2:18 AM, Martin Langhoff
[EMAIL PROTECTED] wrote:
On Fri, Sep 12, 2008 at 5:10 PM, Michail Bletsas [EMAIL PROTECTED] wrote:
Where is that list? Who has it? Who coordinates bugtracking for the
libertas stuff? Can't be that much of a mistery.
/important
If
Martin,
On Thu, Sep 11, 2008 at 12:44 AM, Martin Langhoff
[EMAIL PROTECTED] wrote:
On Thu, Sep 11, 2008 at 12:37 AM, Ricardo Carrano [EMAIL PROTECTED] wrote:
The release notes can be acessed here:
http://www.laptop.org/teamwiki/index.php/Tech:FW_8388_RELEASE_NOTES
22.p18 is the current
On Thu, Sep 11, 2008 at 6:25 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
On Fri, Sep 12, 2008 at 12:24 AM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Fedora 9 ships with a 2.6.25 kernel with a new libertas driver.
Because of the changes implemented in this driver, you should use the
latest
Hi Martin,
On 9/9/08, Martin Langhoff [EMAIL PROTECTED] wrote:
On Wed, Sep 10, 2008 at 1:40 PM, Michail Bletsas [EMAIL PROTECTED] wrote:
- F9 libertas-usb8388-firmware-5.111.20.p49-1
- F9/XO (8.2-759) libertas-usb8388-firmware-5.111.22.p18-1
You are definitely better off using
On Thu, Sep 11, 2008 at 6:25 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
On Fri, Sep 12, 2008 at 12:24 AM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Fedora 9 ships with a 2.6.25 kernel with a new libertas driver.
Because of the changes implemented in this driver, you should use the
latest
Hi Martin,
On 9/9/08, Martin Langhoff [EMAIL PROTECTED] wrote:
On Wed, Sep 10, 2008 at 1:40 PM, Michail Bletsas [EMAIL PROTECTED] wrote:
- F9 libertas-usb8388-firmware-5.111.20.p49-1
- F9/XO (8.2-759) libertas-usb8388-firmware-5.111.22.p18-1
You are definitely better off using
On Mon, Aug 25, 2008 at 2:54 PM, Ton van Overbeek [EMAIL PROTECTED] wrote:
When trying the latest joyride builds (last one I tried was 2331) I noticed
the following regressions (firmware Q2E14):
- As many have already reported the mesh device msh0 is gone. This caused
cerebro to abort and
Hello all!
I am reading a ticket (7967) that reports tests based on joyride 2302.
But this version did not seem to be released (from 2301 it jumps to
2311).
What am I missing?
Thanks!
Cheers!
Ricardo
___
Devel mailing list
Devel@lists.laptop.org
Hello all!
For 9.1 on, I suggest the release schedule to happen before people
begin to take their breaks.
December and August are probably hard months to get a big team push,
due to vacations.
Maybe it would be the case to bring this to June and November.
Just a thought.
Cheers!
Ricardo
models.
I believe that you are referring 7972 and I'll leave that in blocker status
until forced to choose a smaller list.
If there's something else you can't do while looking at this, we could try
to compare them...
Thanks,
Greg S
Deepak Saxena wrote:
On Aug 13 2008, at 03:27, Ricardo
Hi everyone,
On Fri, Aug 15, 2008 at 6:14 PM, John Gilmore [EMAIL PROTECTED] wrote:
Deepak,
Would this be considered a blocker for 8.2 ...
(Not my call.)
or do we primarilly
care about collaboration in mesh mode for deployments?
Very few deployments use mesh mode, because it currently
On Wed, Aug 13, 2008 at 7:04 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Wed, Aug 13, 2008 at 09:31:11AM -0700, Deepak Saxena wrote:
On Aug 13 2008, at 03:27, Ricardo Carrano was caught saying:
But the important result is that collaboration does not seem to be
working in infra mode
On Wed, Aug 13, 2008 at 7:04 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Wed, Aug 13, 2008 at 09:31:11AM -0700, Deepak Saxena wrote:
On Aug 13 2008, at 03:27, Ricardo Carrano was caught saying:
But the important result is that collaboration does not seem to be
working in infra mode
On Tue, Aug 12, 2008 at 3:44 PM, Deepak Saxena [EMAIL PROTECTED] wrote:
On Aug 12 2008, at 12:19, Javier Cardona was caught saying:
So it doesn't look like Javier's patch actually went into one of our
official
branches (stable/testing/master). I'm also not sure we need it b/c testing
and
Dear all,
It is very important to correctly approach the interactions between
suspend/resume and network traffic.
There are at least two mechanisms that need to be in place for both
things to be able to operate together without causing major issues:
1 - The multicast address populating on the
Hi Chris,
On Tue, Aug 12, 2008 at 11:46 AM, Chris Ball [EMAIL PROTECTED] wrote:
Hi Ricardo,
There are at least two mechanisms that need to be in place for both
things to be able to operate together without causing major issues:
1 - The multicast address populating on the firmware,
Hi Javier,
On Tue, Aug 12, 2008 at 3:19 PM, Javier Cardona [EMAIL PROTECTED] wrote:
Deepak,
On Tue, Aug 12, 2008 at 10:38 AM, Deepak Saxena [EMAIL PROTECTED] wrote:
There are at least two mechanisms that need to be in place for both
things to be able to operate together without causing major
Thank you, Javier!
On Tue, Aug 12, 2008 at 6:44 PM, Javier Cardona [EMAIL PROTECTED] wrote:
Ricardo,
On Tue, Aug 12, 2008 at 1:03 PM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Marvell will implement the new wow-signature API with the next
firmware release (22p18)
Though I agree now, as I
So, this is still one more evidence that olpc-utils was the cause of #7776.
Thank you Andrew!
On Tue, Aug 5, 2008 at 9:48 PM, Andrew Burgess [EMAIL PROTECTED] wrote:
Joyrides 2253 and 2254 had no networking for me (no mesh, nothing
but the xo icon in the network view)
Joyride 2255 has
Hi!
On Sun, Aug 3, 2008 at 6:34 PM, Deepak Saxena [EMAIL PROTECTED] wrote:
On Aug 03 2008, at 22:49, Gary C Martin was caught saying:
Just moved from joyride-2241 to 2248, any one else seeing an empty
neighborhood and no network access (just my XO icon in the centre)?
ifconfig shows eth0 is
Dear Pol, Greg and Michael,
There is so much going on here that it's difficult to approach.
I mostly second Michael's comments. Though Greg obviously took a lot
of his time to put these goals together, I think we are missing the
target. It's good to have goals such as 40 XOs being able to chat
Guillaume,
On Wed, Jul 16, 2008 at 11:51 AM, Guillaume Desmottes
[EMAIL PROTECTED] wrote:
Le mercredi 16 juillet 2008 à 09:31 -0300, Ricardo Carrano a écrit :
I am trying to install the Video Chat activity, in order to check #7511.
Following instructions in:
http://lists.laptop.org
that Joe is testing?
Thank you very much!
Cheers!
Ricardo
On Wed, Jul 16, 2008 at 11:57 AM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Guillaume,
On Wed, Jul 16, 2008 at 11:51 AM, Guillaume Desmottes
[EMAIL PROTECTED] wrote:
Le mercredi 16 juillet 2008 à 09:31 -0300, Ricardo Carrano a écrit
On Wed, Jul 16, 2008 at 9:10 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Wed, Jul 16, 2008 at 07:10:23PM -0400, Ricardo Carrano wrote:
I am trying to further investigate this, but I am confused on what
exactly was used on the test. Would you recall what exactly is the
build that Joe
Hey!
I am trying to install the Video Chat activity, in order to check #7511.
Following instructions in:
http://lists.laptop.org/pipermail/devel/2008-April/013227.html
Fetching the rpms from:
http://people.collabora.co.uk/~cassidy/olpc-video-chat/
All the rpms installs ok but the last which
Like Michael pointed out, there are few people at OLPC who understand
and enjoy telepathy. I think this is an understatement. Personally, I
think that Collabora was very pressed to get something working on the
laptop and the resulting presence stack looks like one hack on top of
another. For
a really cool mesh routing protocol. As such,
Cerebro (or at least that portion) should ideally run on the network chip,
not the main CPU. My kingdom for some Free marvell firmware, etc.
Really? Could you develop?
Cheers
Ricardo Carrano
___
Devel
Ben,
~ The invitations are unicast, implemented using TCP. When machine A sends
an invitation to B, we see the following exchange:
1. A broadcasts an ARP request for B
2. B sees the ARP request and replies to A
3. A receives the ARP reply from B and sends a TCP SYN to B
4. B does not see
On Wed, Jun 4, 2008 at 10:41 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
On Wed, Jun 4, 2008 at 7:12 PM, John Gilmore [EMAIL PROTECTED] wrote:
what do people think about the idea of making the existance of established
TCP connections inhibit sleep?
What release are you running?
Finally, tests in wireless should be performed with update-1.706+
Preferably update.1-708
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Sorry for the typo:
http://wiki.laptop.org/go/Wireless_Airtime_Analysis
(s/Artime/Airtime)
On Fri, Jun 6, 2008 at 1:04 PM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Hi all!
For those interested in wireless traffic analysis:
http://wiki.laptop.org/go/Wireless_Artime_Analysis
Comments
Dear all!
(1) Where is it?
In Update-1.706
rpm -qi mkinitrd says it is installed.
But there is no mkinitrd binary in /sbin/ (as rpm -ql would reveal).
Am I missing something?
(2) Whenever I install a new rpm kernel. I keep getting could not
find /lib/modules/kernel/modules.dep.
The file is
On Fri, Jun 6, 2008 at 5:31 PM, Polychronis Ypodimatopoulos
[EMAIL PROTECTED] wrote:
In the spirit of escalating collaboration/communication use cases to
more realistic scenarios, I 'd like to propose creating the following
multihop network testbed.
This testbed will involve about 70 nodes,
On Tue, Jun 3, 2008 at 12:08 PM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:03 -0400, John Watlington wrote:
My bad. This is now Trac #7170
http://dev.laptop.org/ticket/7170
All of the information in this ticket comes from email exchanged with
dcbw and dwmw2 when I
On Tue, Jun 3, 2008 at 11:12 AM, Dan Williams [EMAIL PROTECTED] wrote:
On Mon, 2008-06-02 at 17:12 -0700, Brian Cavagnolo wrote:
To update boot2, copy the boot2 and firmware images to /lib/firmware and:
echo boot2_image_name /sys/class/net/eth2/lbs_boot2
echo firmware_image_name
On Tue, Jun 3, 2008 at 11:49 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:44 -0300, Ricardo Carrano wrote:
Please check comment on:
http://wiki.laptop.org/go/Active_Antenna_Reprogramming#User_Space_Method
Where am I looking? The 'has failed twice' claim? That's hardly
On Tue, Jun 3, 2008 at 11:35 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote:
A necessary rectification:
Firmware updates from the driver are the only method that works
currently. If we want to name one method a disaster, we would have
On Tue, Jun 3, 2008 at 11:35 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Tue, 2008-06-03 at 11:34 -0300, Ricardo Carrano wrote:
A necessary rectification:
Firmware updates from the driver are the only method that works
currently. If we want to name one method a disaster, we would have
Yanni,
On Thu, May 29, 2008 at 12:24 AM, Giannis Galanis [EMAIL PROTECTED] wrote:
these is a list some bugs discovered tonight on 706
5848: The mesh circle in the main view was disappered
I have a theory on that. Please check the ticket.
Cheers!
Ricardo
On Fri, May 16, 2008 at 9:46 PM, Bernie Innocenti [EMAIL PROTECTED] wrote:
Michael Stone wrote:
On Fri, May 16, 2008 at 04:31:05PM +0200, Bernie Innocenti wrote:
The changelog for olpc-utils is missing. Is it a bug in
the script?
Seems likely to me since Koji printed the appropriate
On Tue, May 13, 2008 at 11:59 AM, John Watlington [EMAIL PROTECTED] wrote:
On May 12, 2008, at 3:31 PM, Ricardo Carrano wrote:
How does the collision model/scheme change between AP mode and
ad-hoc/mesh modes?
As far as I can tell, it doesn't. 802.11s is interoperable
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).
On Wed, May 7, 2008 at 1:05 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
2008/5/3 Ricardo Carrano [EMAIL PROTECTED]:
NYC schools use cloaked access points to provide wireless connectivity.
We currently do not support cloaked APs (and ... ok, they hardly provide
any
additional security
Hi!
Please contribute with your ideas to the following:
NYC schools use cloaked access points to provide wireless connectivity.
We currently do not support cloaked APs (and ... ok, they hardly provide any
additional security).
Support for cloaked APs is being discussed in #6237 and it involves
Nicholas mumbles something on a mailing list and it gets translated and
published throughout the world.
Somehow, he has the attention of the world media. That's no small trick.
Without this level of attention it is hard to get sponsors and without
sponsors it is impossible to manufacture
(...)
This isn't what I was talking about. Forget about the mesh. Ban it
from your mind.
(...) the troublesome Mesh and just live with the 802.11b/g,
Ban (...) the troublesome Mesh you say. Sigh.
There is not a single piece of software or hardware in any innovative
project that wasn't or
(sigh, again) I did not distort anything. The suggestion that OLPC should
remove the mesh is there.
And this suggestion is hardly based on a first hand experience or in a
technical analysis.
People who never put three XOs together keep repeating this based on a quite
vague idea that the tickets
;-)
Thank you!
Ricardo Carrano
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On Fri, Apr 18, 2008 at 10:28 AM, David Woodhouse [EMAIL PROTECTED]
wrote:
On Thu, 2008-04-17 at 17:09 -0400, Michael Stone wrote:
Ashish comments on #6869: Firmware release - 5.110.22.p9 as follows:
Currently firmware 5.110.22.p8/9 does not support more than 8 multicast
mac
On Fri, Apr 18, 2008 at 11:26 AM, David Woodhouse [EMAIL PROTECTED]
wrote:
On Fri, 2008-04-18 at 10:58 -0400, Ricardo Carrano wrote:
Mmm, if the driver says it is 32 and the firmware only allows for 8,
we have a problem, don't we? ;-)
Indeed. Do we know which versions of firmware support
On Fri, Apr 18, 2008 at 12:01 PM, Polychronis Ypodimatopoulos [EMAIL
PROTECTED]
wrote:
David Woodhouse wrote:
On Fri, 2008-04-18 at 11:50 -0400, Polychronis Ypodimatopoulos wrote:
what's possible? why not?
David Woodhouse wrote:
On Fri, 2008-04-18 at 11:43 -0400, Polychronis
It is possible that the factory neglected to set the date on some units,
Isn't if the same that we fixed in some units back in December?
http://wiki.laptop.org/go/Fix_Clock
___
Devel mailing list
Devel@lists.laptop.org
It seems a very relevant question.
The way collaboration over salut works now (I ask the experts to confirm
that), every application will demand a multicast mac address. And four are
already taken (01:00:5e:00:00:fb, 01:00:5e:00:00:01, 33:33:00:00:00:01 and
33:33:ff:1:2:3, where 1..3 are the last
. Schwartz
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ricardo Carrano wrote:
| Assuming this is correct, than some questions follow.
| - Is 4 a reasonable limit (is the XO capable of more in terms of
processing
| and memory?)
The XO is definitely capable
Hi!
I would like to ask your attention to the kernel patch at:
http://dev.laptop.org/ticket/#comment:4
It fixes ethtool -S, a very important debugging tool (it provides NIC
statistics).
It was proposed by dwmw2 and already tested. It seems ready for committing.
Best regards,
Ricardo
I will put the new firmware in if im notified of it.
http://wiki.laptop.org/go/Firmware_release_procedures
File a trac bug assign it to me user dgilmore and I will build it in koji.
and get it pushed into joyride as well as updated in fedora.
Thank you, Dennis. That would be
Hi!
I want to include a new wireless firmware into joyride for testing (proper
announcement will follow as soon as I find out how).
It was suggested that I used the dropbox mechanism (
http://wiki.laptop.org/go/Build_system#Dropbox_Mechanism ).
But the instructions are too succinct given my
M,
Release 22p6 is not affected.
On Thu, Apr 10, 2008 at 10:02 PM, [EMAIL PROTECTED] wrote:
And what happens if we go one revision back?
M
- Original Message -
From: Zarro Boogs per Child [EMAIL PROTECTED]
Sent: 04/10/2008 09:03 PM GMT
Cc: [EMAIL PROTECTED]
Subject: Re: #6869
I second Carol's pragmatic approach. What we should do is to use access
points in schools whenever possible. The mesh network was not designed to
compete with infra-structure. It was designed to be used when there is no
infra-structure.
That being said, I will keep repeating myself that
Hi!
As far as I know, there is no available patch for the windows version.
Please refer to: http://wiki.laptop.org/go/Wireshark (though this page is
not updated).
--
Ricardo Carrano
On Mon, Apr 7, 2008 at 7:06 AM, [EMAIL PROTECTED] wrote:
Good day
We would like to do performance tests
, Ricardo Carrano wrote:
Two comments on the /etc/NetworkManager/dispatcher.d/increase-
mcast-rate script
1 - The rates passed to iwpriv must be doubled. The way it is the
rates are being fixed at 18Mbps.
2 - Also using msh0 or eth0 makes no difference. We don't need both
iwpriv
with the back and forth
issue you mention.
--
Ricardo Carrano
On Thu, Mar 27, 2008 at 9:14 PM, [EMAIL PROTECTED] wrote:
On Thu, 27 Mar 2008, Martin Langhoff wrote:
2008/3/27 Ricardo Carrano [EMAIL PROTECTED]:
My suggestion for the Cambrige testbed is:
1 - Validade probe response driver patch
the algorithm to be weighed more heavily in favor of a
minimal hop count ?
wad
On Mar 25, 2008, at 8:41 PM, Ricardo Carrano wrote:
The test consists of 10 nodes pinging the multicast address
224.0.0.1 in a quiet environment ( -96dbm noise floor).
We vary the expiration time for route
(Time to stop using active antennas for packet capture ?)
Please check with another sniffer if you can still listen to
beacons from this active antenna. If so, please stop using it as a
sniffer. Please take a look at #6709.
I already logged with multiple sniffers. Yes, the beacons
Updated from 695 to 702.
No activity icons on the frame...
On Sat, Mar 22, 2008 at 12:17 AM, Build Announcer v2 [EMAIL PROTECTED]
wrote:
http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build702http://pilgrim.laptop.org/%7Epilgrim/olpc/streams/update.1/build702
Changes in build 702
Thanks, David. This accounts for part of the question. Any idea on how this
translates to 2 probe requests in the air?
On Thu, Mar 6, 2008 at 6:16 AM, David Woodhouse [EMAIL PROTECTED] wrote:
On Wed, 2008-03-05 at 20:09 -0300, Ricardo Carrano wrote:
It may be possible that NetworkManager
on the merits of keeping probe requests.
In case we keep them, it seems that we should use less of them.
--
Ricardo Carrano
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
and displaying the
mesh traffic properly.
Could you make this capture files available?
--
Ricardo Carrano
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
I believe it is a WRT54Gv8 model (which, btw has not enough memory to run
some of the openwrt variants around). It is brand new AP (bought it at
BestBuy) with stock LInksys firmware. It is still at 1cc (I brought another
(same model) with me so not to disturb the tests in place).
On Mon, Mar 3,
Just to add that:
- The access point Javier mentions is the one I bought yesterday (Linksys
WRT54G)
- Most of this traffic is retransmission (3606):
(wlan.fc.ds == 3 and wlan.sa[0-2] == 00:17:C4 and wlan.ta[4-5] == ce:6e)
(wlan.fc.retry == 1)
- It is also interesting to detect other wds peers
(last version was incomplete):
Just to add that:
- The access point Javier mentions is the one I bought yesterday (Linksys
WRT54G)
- Most of this traffic is retransmission (3606):
(wlan.fc.ds == 3 and wlan.sa[0-2] == 00:17:C4 and wlan.ta[4-5] == ce:6e)
(wlan.fc.retry == 1)
- It is also
decipher mesh
traffic ?
wad
On Feb 21, 2008, at 9:31 AM, Ricardo Carrano wrote:
Isn't the LLC traffic what you're looking for?
I see a lot of multicast traffic on your file, particularly to
01:00:5e:7f:47:31. They are LLC.
On Thu, Feb 21, 2008 at 10:38 AM, John Watlington [EMAIL
Yanni,
But we should note that, not everything that expires, does so because of a
timer.
A cache entry may have an associated timestamp and expire in timestamp +
ttl.
I have noticed that an idle machine will resume for some time, and suspend
again, several times for no reaso
The result is that
John,
I believe what is discussion here is the choice between waking on multicast
(and then keep MDNS working) or don't wake on multicast (and then saving
more power). Or if there is a way out of this compromise.
Are you cutting to the chase or just changing the movie? (Forgive me for the
joke
,
Sulochan.
On Feb 19, 2008 5:41 PM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
Sulochan,
You should check your forwarding (layer two) table with : iwpriv msh0
fwt_list index (index is 0,1,2,...)
Look for an entry that forwards the frames destined to the anycast mac
address
layer three (IP) routes.
Regards,
Ricardo Carrano
2008/2/19 sulochan acharya [EMAIL PROTECTED]:
Folks,
I can not hop from xo to xo to xs.
Here is what I did:
One XO closer to the server with active antenna.and i can ping the
server from this laptop.
Another XO closer to the first
I believe the most important issue here is that, the way it is now,
suspend/resume will make a disconnected mesh unusable.
On Feb 17, 2008 4:11 AM, Giannis Galanis [EMAIL PROTECTED] wrote:
There are a couple of important issues/bugs regarding Salut and
Suspend/Resume.
FIRST, there is a
Chris,
A mesh will always rely to some degree in multicast/broadcast traffic. This
is not a bug.
Avahi entries will expire after some time. Suspend will prevent it to update
its cache.
On Feb 19, 2008 11:13 AM, Chris Ball [EMAIL PROTECTED] wrote:
Hi,
It does feel like we should turn off
1 - 100 of 158 matches
Mail list logo
