On my last week at 1cc, I performed several tests on MeshPortalPoint(MPP)
configurations.
Perhaps it is good for all to have an insight on what is possible, and what
isnt with MPP.
(especially after tomorrows network presentation!)
For those who dont know yet, an XO acts as an MPP, when it
sorry for the multiple tickets.
i had a problem accessing trac.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
these is a list some bugs discovered tonight on 706
5848: The mesh circle in the main view was disappered
7121: Chat would not load
7119: Usb stick was too slow to mount(1min)
7118: Letters in all sugar activities became tiny!
**5848 probably isnt linked to the new libertas
On Tue, May 27,
On Mon, May 12, 2008 at 10:58 AM, Mikus Grinbergs [EMAIL PROTECTED] wrote:
Some small discrepancies in the output of the new 'olpc-netstatus':
1) I have a wired connection. (NO wireless.) I do not understand why,
but for some Joyride builds, the wired connection gets assigned to 'eth0',
The past couple of weeks I have been working on developing several Network
testing scripts,
that make testing a more pleasant experience!
The scripts collect and display information about
the network configuration, telepathies and their status, the neighbor XOs
and the forwarding tables
For
The action USB key offers the capability to customize the XOs nand image
automatically.
It is also possible to set certain function perform at every boot.
It is a very usefull tool to customize quickly many XOs, collect information
to the usb, transfer files to the XO etc..
The required can be
thanx,
thats exactly what i needed
On Tue, Apr 22, 2008 at 5:56 AM, Guillaume Desmottes
[EMAIL PROTECTED] wrote:
Le lundi 21 avril 2008 à 10:05 +0200, Guillaume Desmottes a écrit :
Le samedi 19 avril 2008 à 22:18 +0300, Giannis Galanis a écrit :
In the testbed in peabody, the list
-gabble logs. For
every new arrival or departure there must a specific entry.
On 4/19/08, Dafydd Harries [EMAIL PROTECTED] wrote:
Ar 18/04/2008 am 23:25, ysgrifennodd Giannis Galanis:
When connecting to a jabber server, how can we check the list of XOs that
are seen in the mesh view
We have these network UI bugs:
5904 - GUI problem updating buddies clustered around shared activity
5459 - second circle in sugar home view provides false information
5908 - Laptop unable to connect to schoolserver jabber server
Also 4193 - Two XOs were connected to an access point and were
When connecting to a jabber server, how can we check the list of XOs that
are seen in the mesh view, or the analyze activity?
Is checking the gabble log the only way?
What records in the log indicate arrival or departure?
When testing with 50 or 100 XOs connected it is often impractical to
Chris,
what does inhibit-idle-suspend do?
On Wed, Mar 12, 2008 at 11:45 PM, Build Announcer v2 [EMAIL PROTECTED]
wrote:
http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build699http://pilgrim.laptop.org/%7Epilgrim/olpc/streams/update.1/build699
Changes in build 699 from build: 698
Ok.
Should we test automatic suspend by removing the file?
Or we dont consider it a priority any more?
On Fri, Mar 14, 2008 at 12:05 AM, Chris Ball [EMAIL PROTECTED] wrote:
Hi,
what does inhibit-idle-suspend do?
It allows you to disable automatic idle suspend while keeping enabled
the
PROTECTED] wrote:
Read sharing is a critical feature. Please do test it.
-walter
On 2/23/08, Morgan Collett [EMAIL PROTECTED] wrote:
Giannis Galanis wrote:
2. I will try to update all of them with the build we will agree to
initially test with. This would be 693/D13
Kim,
The suspend/resume problems will show even with 2 XOs. This cannot be fixed
at the moment.
As Michalis mentioned in another email, testing S/R and mesh scalability
will just break the test. We have to test them invidually.
On Sun, Feb 24, 2008 at 10:35 PM, Kim Quirk [EMAIL PROTECTED]
in case you need it, i am resending the script because it was blocked
On Fri, Feb 22, 2008 at 2:55 PM, Giannis Galanis [EMAIL PROTECTED] wrote:
I have noticed that an idle machine will resume for some time, and suspend
again, several times for no reason.
I wrote a simple script that checks
I have noticed that an idle machine will resume for some time, and suspend
again, several times for no reason.
I wrote a simple script that checks every 1sec whether the machine is
suspended on not.
It gives a timeline of Suspended times and Resumed times.
A left an XO completely idle overnight
It is possible indeed. We have to check.
I will try to test how it works with avahi.
On Fri, Feb 22, 2008 at 3:25 PM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
Yanni,
But we should note that, not everything that expires, does so because of a
timer.
A cache entry may have an associated
A couple of stuff for the next week's test.
1. We have about 45 XOs in the conference room, and we can make it up to 80
by collecting other XOs in the office. Do you think this is enough?
2. I will try to update all of them with the build we will agree to
initially test with. This would be
When the XO connects to a mesh channel, it sends a specific request for a
School server.
If it receives a reply it knows there is SS somewhere in the mesh. After it
receives the reply it will attempt to connect to it.
If no reply is received within a certain timeout, then the XO will connect
to
On Feb 19, 2008 10:13 AM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
I was asking whether it would help to have the wireless module wake us
on multicast packets instead of only unicast. Are you saying that it
would?
It seems so, though it would, as John points out, make resumes far more
.
On Feb 19, 2008 1:19 PM, Benjamin M. Schwartz [EMAIL PROTECTED]
wrote:
On Tue, 2008-02-19 at 13:11 -0500, Giannis Galanis wrote:
The wakeup required is T minutes for every T minutes.
Actually you would need to be awake for T minutes
and suspended for T minutes to be sure u are ok.
So
of the
peers/targets? I think they do, unless i am very confused. Couldn't we
awake/resume the target XO when it receives these specific packets?
we need to do some sniffing
On Feb 19, 2008 1:13 PM, Giannis Galanis [EMAIL PROTECTED] wrote:
On Feb 19, 2008 10:13 AM, Ricardo Carrano
On Feb 19, 2008 12:55 PM, Benjamin M. Schwartz [EMAIL PROTECTED]
wrote:
On Tue, 2008-02-19 at 12:29 -0500, Giannis Galanis wrote:
The avahi works is that every several minutes(a predetermined timeout)
each host will send multicast request for all peers in its list.
Then all peers receiving
these specific packets?
On Feb 19, 2008 3:00 PM, Giannis Galanis [EMAIL PROTECTED] wrote:
The list expires in 10min-30min.
But we cant wait 30min before suspending, it is way too long.
On Feb 19, 2008 11:37 AM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
Yanni,
As I posted in the bug, I believe
On Feb 19, 2008 4:10 PM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Yanni,
Did a use it otherwise? Because of the effects of xmas tree, the timeout
for a failed XO until it's icon is removed is 10-30min.
I am talking about the time it takes for an avahi entry to expire. For
what you
There are a couple of important issues/bugs regarding Salut and
Suspend/Resume.
FIRST, there is a sugar issue, (or at least it seems so).
When an XO resumes after long suspends, all icons(APs, XOs, but not the
meshes) instantly vanish*(#6467)*. Then they slowly reappear. Although with
the APs the
Perhaps it is not important, but the shown changes from olpc-utils 0.67 to
0.68 is wrong.
It includes stuff that were added in previous versions ages ago
On Feb 13, 2008 2:24 AM, Build Announcer v2 [EMAIL PROTECTED] wrote:
I believe in the blind table of XO-1, you have to include the anycast
address C027C027C027.
I think the last digits of the address are custom, but not sure though.
Still, in your case, you should only blind XO2 to XO1, and dont forget to
invert the blinding table.
On Feb 11, 2008 11:41 AM, John
I believe in the blind table of XO-1, you have to include the anycast
address C027C027C027.
I think the last digits of the address are custom, but not sure though.
Still, in your case, you should only blind XO2 to XO1, and dont forget to
invert the blinding table.
On Feb 11, 2008 11:41 AM, John
2. It takes up to 10min for avahi even to detect the inactivity of a
peer.
i.e. If an XOs switches channels, for up to 10min avahi wont even
know(it
used to be 1-2min).
Is this with or without the patch from bug #6162 ? If without, then the
time it
takes avahi to discover it should
On Jan 31, 2008 10:54 AM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
I believe our current salut/avahi issues are described in the following
points:
1. I was under the impression that when a peer switches channels it
sends a goodbye signal. And in fact only anorthodoxically removed
can you please specify:
which jabber you tried to connect to?
which build are you running?
On Jan 20, 2008 7:42 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote:
I don't have any wireless. I do have a wired ethernet connection to
a LAN (which in turn uses a proxy to reach the internet).
Even
I understand that salut is not very popular lately since we are drifting
mostly towards infra mode.
Still, it is the preferable way for G1G1 laptops to talk to each other,
since there is no SS, and the public jabber is not guaranteed, or in the
future overcrowded.
I have conducted several tests
people
will use it anyway.
U see my point?
Also, if it is smth simple we can quickly implement is for Update.1.
On Jan 17, 2008 7:36 PM, David Woodhouse [EMAIL PROTECTED] wrote:
On Thu, 2008-01-17 at 19:16 -0500, Giannis Galanis wrote:
It must be noted that the important issue
David,
There are a couple of issues i would like to address, mostly related to the
new wireless driver.
First, the netstat command:
About 50% of the time it becomes very slow(practically freezes) and spews a
getnameinfo error.
The result from strace is:
---
.
socket(PF_INET,
in 100% of the times you try the above.
I believe that if the emulator you operate, uses the proper timeouts, you
will see the effect
yani
On Dec 14, 2007 4:31 AM, Sjoerd Simons [EMAIL PROTECTED] wrote:
On Thu, Dec 13, 2007 at 11:18:01PM -0500, Giannis Galanis wrote:
THE TEST:
6 XOs connected
On Dec 13, 2007 5:08 PM, John Watlington [EMAIL PROTECTED] wrote:
On Dec 13, 2007, at 1:05 PM, Giannis Galanis wrote:
I also installed the rpm in custom machine(not a school server) in
1CC.
I must note that the ejabberdctl-extra.diff patch in the wiki page
is for another version than
.
Regards,
Rob
Giannis Galanis wrote:
Robert,
It was me that logged in the jabber. Sorry i did not let u know, i didnt
think it was important.
I am trying to set up a jabber server at another school server, but i
was having continuous erros with the config file.
I logged on to copy
The feature, although not usable by the activities, it has other benefits.
By observing the buddy list, you acquire instant information of the network
connection go the users:
when connected to channel 1 for example:
169.254.x.x address are in link-local
172.18.x.x are connected to schoolserver
Pascal,
I have been working on something similar. It is a console script that gather
networks related logs, and will be available in the next joyride.
At the moment it includes:
var/log/messages
var/log/xorg.0.log
/home/olpc.sugar.logs/presenceservice
/home/olpc.sugar.logs/gabble
Simon,
I think the email i send you is incomplete, my connection was poor and gmail
must have saved the wrong draft. But, 1-2-3, is what i intended to send you.
I also meant to ask, How many times do you try _init_connection before you
assume the connection is down?
I hope so. I have a tarball
Yes, i have seen this ticket in the past. To detect whether an XO is
actually there or not, is a simple task to accomplish, and I am currently
working on a simple script that will give a list of the properly connected
XOs, along with the temporarily disconnected.
It is a very useful idea to
Since you are updating the presence service, it is a could opportunity to
fix the switch from salut to gabble.
When internet connectivity is detected, salut should stop, and gabble should
start right after. However, this doesnt work properly even on latest
builds, especially when the XO connects
Since you are updating the presence service, it is a could opportunity to
fix the switch from salut to gabble.
When internet connectivity is detected, salut should stop, and gabble should
start right after. However, this doesnt work properly even on latest
builds, especially when the XO connects
Simon,
I think the email i send you was incomplete, my connection was poor and
gmail must have saved the wrong draft. But, 1-2-3, is what i intended to
send you.
I also meant to ask, How many times do you try _init_connection before you
assume the connection is down?
I hope so. I have a
, Giannis Galanis wrote:
Sjoerd,
I would like to ask you,
you replied at one of the bugs:
Moving from a bugreport to a private mail might not be a great idea..
Could you
in the future just put your questions in the bugreport so we can have the
discussion in a more public fashion :)
Salut
, iff means if and only if. It's often
used by mathematicians.
On Tue, 06 Nov 2007 at 03:23:39 -0500, Giannis Galanis wrote:
What does proper notification mean? Which are the cases that it happens?
If Salut is explicitly asked to disconnect, it will tell Avahi to delete
all its mDNS records
Pascal,
I have been working on something similar. It is a console script that gather
networks related logs, and will be available in the next joyride.
At the moment it includes:
var/log/messages
var/log/xorg.0.log
/home/olpc.sugar.logs/presenceservice
/home/olpc.sugar.logs/gabble
Eduardo,
There is a wiki page with some similar info:
http://wiki.laptop.org/go/Developer_Environment
I just realized that this page is created and edited by you
So you have written scripts for this purpose as well?
I have attached my two scripts. The are written in bash, but they are not
The feature, although not usable by the activities, it has other benefits.
By observing the buddy list, you acquire instant information of the network
connection go the users:
when connected to channel 1 for example:
169.254.x.x address are in link-local
172.18.x.x are connected to schoolserver
Simon,
The following are the current bugs/enhancements regarding the presence
service. They are listed from high to low priority with their corresponding
trac number.
1. The presence service should detect more efficiently the internet
connectivity and switch to gabble when appropriate(4193)
2.
Kim, Ricardo,
I have updated the Network connectivity test page(
http://wiki.laptop.org/go/Test_Network_Configuration).
I have added some additional information concerning the IP addresses and the
resolv.conf file, in order to make things more clear.
I updated the connectivity_status script. It
.
yani
On 10/12/07, Kim Quirk [EMAIL PROTECTED] wrote:
Yani,
Lots of good work on this document! I've added my comments inline below.
Copying Alex for comments as well.
Kim
On 10/12/07, Giannis Galanis [EMAIL PROTECTED] wrote:
Kim,
A couple of things in case I forget later today
53 matches
Mail list logo
