Re: [sugar] How do I connect to a Jabber server ?
On Tue, Aug 5, 2008 at 19:30, Mikus Grinbergs [EMAIL PROTECTED] wrote: Morgan wrote: My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Therefore you (and the people you want to contact) need to be on a community jabber server You are talking about how to *use* a jabber server once one is connected. I do not *have* a connected jabber server. It should *just work*. However there are many potential problems. You might be able to help us detect problems we haven't triggered ourselves, and by providing logs you can help us diagnose and therefore fix the problem, if it is something we can fix. Unfortunately there are many situations we can't fix, like a jabber server not running - it's up to the admin of that server to rectify that situation, and we are willing to provide assistance with that. To see people from remote locations, you need to be on the same Jabber server as they are. That requires: * Internet access - via an Access Point, or over the mesh via a school server, or over the mesh via a Mesh Portal Point XO which in turn has access, or even via some dialup technology like bluetooth+GPRS. * Network Manager to get an IP address * A jabber server to be configured * That server to be working * Other people to be on the server. What I an aware of is: (1) Months ago, I would boot my XO, and other XO icons would show up in my neighborhood view (from whatever jabber server I had specified via sugar-control-panel). Then remote users stopped showing up (no matter which server I had specified). (2) I do not myself know enough about 'telepathy', etc., to be able to figure out what is going wrong. That is why I am asking for assistance. presenceservice.log and the output of olpc-netstatus should tell us what was happening. You don't *need* to know much about the details, but we will explain for all who are interested. [I'm a G1G1 user, and do not have a Mesh Portal Point to use, nor a school server. Except for me not connecting to a jabber server, the internet works well for me.] I listed possible use cases to illustrate how the system operates... Connecting to an AP disables the mesh, so I don't see the value of what you want. Turning off the mesh while you are connected to a mesh channel would simply (in the proposal) turn the wireless radio off completely, resulting in neither gabble nor salut able to operate. Then I believe the language being used is imprecise. To me, turning off the mesh means turning off the __mesh__. If what is actually being turned off is the __radio__, then call it turning off the wireless radio. What I keep butting my head against is not being able to *control* what is going on. In my mind a 'mesh' is one interface, and an 'AP' is another interface. I would like to turn off the mesh when there are no local XOs, and no school server. You are saying that the 'AP' would get turned off as well. Not something I prefer. Mikus, tickets and logs, logs and tickets. The last time I focused on connectivity was Apr/May. What I concluded then was that my tickets got closed depending on the effect they had on the code -- *not* on whether I as a user could now experience consistent system behavior. We do now have QA people who will try the situation out and see whether the fault was fixed, and a process that involves their signoff before bugs are closed. I'm willing to file a ticket when I see something happening -- such as an error when accessing a Jabber server (though one such ticket was closed as 'invalid' - because that particular server had not given the expected answer). But it is difficult to decide what to ticket/log when I do not see something happening -- for instance, what if a connection to a Jabber server were never attempted by my XO? We appreciate the tickets, even they do on occasion get closed as Won't Fix, Works For Me, Invalid... That's no indication of your ticket-filing skills. We fix the things we can fix, and if it's something out of our control we need to remove it from our work queues. If there's some other way to resolve the situation perhaps we can do better about notifying others if their servers are down, and so on. The log files should tell us a lot about a given situation. presenceservice.log tells us when gabble and salut were running, what disconnected or failed to connect, what buddies were seen and so on. For any presence-related failure, including not seeing any buddies on your screen, presenceservice.log gives us an ability to diagnose the failure. It might not give us enough information, and if there is ultimately not enough information for us to know what failed we have no choice but to close the bug in some way. Sorry. Besides, I post from home - where I do not have a
Re: [sugar] How do I connect to a Jabber server ?
Hi Mikus On Tue, Aug 5, 2008 at 00:40, Mikus Grinbergs [EMAIL PROTECTED] wrote: My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Therefore you (and the people you want to contact) need to be on a community jabber server (http://wiki.laptop.org/go/Community_Jabber_Servers) Currently, only icons from the LOCAL mesh to which I am connected will show up in my Neighborhood view. My question in this topic is: What do I need to do to have icons from REMOTE locations show up ? Connecting to an access point will let you see icons from the local WLAN via telepathy-salut. This can include regular PCs running Sugar. To see people from remote locations, you need to be on the same Jabber server as they are. That requires: * Internet access - via an Access Point, or over the mesh via a school server, or over the mesh via a Mesh Portal Point XO which in turn has access, or even via some dialup technology like bluetooth+GPRS. * Network Manager to get an IP address * A jabber server to be configured * That server to be working * Other people to be on the server. What I am particularly interested in was Eben's statement that the user could turn the mesh on/off with the icon in the Frame. I'm getting much too much 'salut' - I'm hoping that turning off the mesh (*all* of its channels) would give more emphasis to 'gabble'. salut may overwhelm a busy mesh network with many XOs. That would deny service to gabble. Otherwise, gabble takes precedence and will connect if it can. Connecting to an AP disables the mesh, so I don't see the value of what you want. Turning off the mesh while you are connected to a mesh channel would simply (in the proposal) turn the wireless radio off completely, resulting in neither gabble nor salut able to operate. Suddenly the communications link between the school and the internet fails. If the kid happens to be within range of an alternate AP, does he have to do something manually (such as entering the name of a non-school Jabber server) to re-establish Jabber contact to the outside world ? For the known future, school servers will not usually be public. Hence re-establish Jabber contact to the outside world has nothing to do with a school server. But I think you're mixing up connected to a Jabber server / server-cloud and connected to an AP. I don't think I am. When I go to someplace that has wireless, and check my XO, I'm seeing that it connects fine to websites (meaning that the AP must be working), but whenever I then do 'ps -A' I see 'salut' (meaning that 'gabble' must be giving up). Yes, gabble must be giving up. Mikus, tickets and logs, logs and tickets. Please. Anecdotes of it not working are of marginal value and cannot help us debug. We need as much detail as you can possibly give. Which servers did you try? Did you do any other type of check to see if they were up - such as nc servername 5222? presenceservice.log? telepathy-gabble.log? Which establishment provided the AP? Can we do anything to detect if they are filtering ports? Did you have to log on with some sort of portal web page to get Internet access? Currently there is only a *single* field for specifying the Jabber server name (and I've tried many names) - so I expect that when the currently specified one is not working, the user has to manually enter the name of a different Jabber server. Consider it a bug when a server is not working. There is no point in failing over to other servers without user intervention. The community jabber servers are for specific communities. If the whole world joins, of course the server will be swamped and it will be down for everybody. What my question dealt with was how is use of the 'school server' as the Jabber server specified? [I have not seen an answer.] - If the kid has to manually enter an internet-resolvable name for the 'school server', then obviously while the 'school server' is down, the kid has to enter a different name to continue to use Jabber. - But if the use of the 'school server' as __also__ the Jabber server is *automatic* whenever the XO connects to the 'school server', then my question is When the Jabber server at the school fails, HOW does the XO know to start instead using the specified Jabber server name for Jabber-type connections? It is specified in the same field as for any other jabber server. However, the kid simply clicks Register on the home menu, and the XO registers with the school server on the network, if there is one, which automatically populates the jabber server field, so there is no manually enter an internet-resolvable name for the 'school server'. There is no failover. The school server is supposed to work, and keep on working. Using a different jabber server is a choice, and is
Re: [sugar] How do I connect to a Jabber server ?
On Tue, Aug 5, 2008 at 02:56, Gary C Martin [EMAIL PROTECTED] wrote: On 4 Aug 2008, at 23:40, Mikus Grinbergs wrote: My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Currently, only icons from the LOCAL mesh to which I am connected will show up in my Neighborhood view. My question in this topic is: What do I need to do to have icons from REMOTE locations show up ? If gabble fails to get to a named jabber server (set in the control panel) it defaults to salute. This may be via an access point (if you've attached to one) or via the mesh (if it has no luck with an AP). Once it's looking at the mesh it tries each of the 3 slices of spectrum available (1, 6 11) looking for a school server. If it find none it seems to default to go sit on mesh, channel 1, hoping to meet another XO there (though it may re-scan occasionally). Presence Service was designed to run both telepathy connection managers simultaneously. However, it was confusing to have buddies in your neighbourhood view who couldn't see each other, and to know which ones you could collaborate with in one session. So we turn off salut whenever gabble connects. salut is usually up first, so it is the default while gabble is attempting to connect. Now the scanning sequence used to be as stated above (previous official releases), but in recent joyrides I find my XO immediately attaches to my preferred AP and doesn't waist time sniffing the mesh (I like this, but 3 kids under a tree may not). They wouldn't be in range of the AP, or even have a preferred one configured, so they would get the mesh scanning as usual. The xochat.org jabber server is the one I seem to reliably attach to for my XO testing, though I'd love to see an official developer jabber server, so as not to pester real G1G1 users with my tests, and so we can 'eat our own dogfood' in a dev environment**. Connecting to a remote jabber server is currently the way to see and share with other remote users*** in the neighborhood. ** perhaps Sugar Labs could run such an environment? Collabora run a server which is the default setting for jhbuild: olpc.collabora.co.uk *** recently, can even work with non XO jabber clients, though I've not been able to test properly yet. Note: current joyrides past 2241seem to have a broken eth0 networking, allegedly the (local) msh0 is still working but I have no way to test that side of things with a single XO. Regards Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
On 5 Aug 2008, at 09:46, Morgan Collett wrote: The xochat.org jabber server is the one I seem to reliably attach to for my XO testing, though I'd love to see an official developer jabber server, so as not to pester real G1G1 users with my tests, and so we can 'eat our own dogfood' in a dev environment**. Connecting to a remote jabber server is currently the way to see and share with other remote users*** in the neighborhood. ** perhaps Sugar Labs could run such an environment? Collabora run a server which is the default setting for jhbuild: olpc.collabora.co.uk That's good to hear re-confirmed, but I've not seen any buddies/ activities shared on olpc.collabora.co.uk for weeks/months. I'd just assumed your server was always borked by lots of connections, or in some unstable dev status, so I had switched over to xochat.org which always seems to respond and have buddies showing. Using your recent nc olpc.collabora.co.uk 5222 trick I can now see olpc.collabora.co.uk is responding with some xml just fine. So, is no one else using it, or should I do some debugging? Are you running a dev version of a jabber server that's doing something different? --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
Le mardi 05 août 2008 à 12:24 +0100, Gary C Martin a écrit : On 5 Aug 2008, at 09:46, Morgan Collett wrote: The xochat.org jabber server is the one I seem to reliably attach to for my XO testing, though I'd love to see an official developer jabber server, so as not to pester real G1G1 users with my tests, and so we can 'eat our own dogfood' in a dev environment**. Connecting to a remote jabber server is currently the way to see and share with other remote users*** in the neighborhood. ** perhaps Sugar Labs could run such an environment? Collabora run a server which is the default setting for jhbuild: olpc.collabora.co.uk That's good to hear re-confirmed, but I've not seen any buddies/ activities shared on olpc.collabora.co.uk for weeks/months. I'd just assumed your server was always borked by lots of connections, or in some unstable dev status, so I had switched over to xochat.org which always seems to respond and have buddies showing. Using your recent nc olpc.collabora.co.uk 5222 trick I can now see olpc.collabora.co.uk is responding with some xml just fine. So, is no one else using it, or should I do some debugging? Are you running a dev version of a jabber server that's doing something different? olpc.collabora.co.uk was recently reinstalled to a new ejabberd server in order to test Gadget. The shared roster hack was removed which improve stability but doesn't automatically display all the connected buddies anymore. Gadget should solve that, I plan to merge it at the beginning of the 9.1.0 cycle. G. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
Morgan wrote: My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Therefore you (and the people you want to contact) need to be on a community jabber server You are talking about how to *use* a jabber server once one is connected. I do not *have* a connected jabber server. To see people from remote locations, you need to be on the same Jabber server as they are. That requires: * Internet access - via an Access Point, or over the mesh via a school server, or over the mesh via a Mesh Portal Point XO which in turn has access, or even via some dialup technology like bluetooth+GPRS. * Network Manager to get an IP address * A jabber server to be configured * That server to be working * Other people to be on the server. What I an aware of is: (1) Months ago, I would boot my XO, and other XO icons would show up in my neighborhood view (from whatever jabber server I had specified via sugar-control-panel). Then remote users stopped showing up (no matter which server I had specified). (2) I do not myself know enough about 'telepathy', etc., to be able to figure out what is going wrong. That is why I am asking for assistance. [I'm a G1G1 user, and do not have a Mesh Portal Point to use, nor a school server. Except for me not connecting to a jabber server, the internet works well for me.] Connecting to an AP disables the mesh, so I don't see the value of what you want. Turning off the mesh while you are connected to a mesh channel would simply (in the proposal) turn the wireless radio off completely, resulting in neither gabble nor salut able to operate. Then I believe the language being used is imprecise. To me, turning off the mesh means turning off the __mesh__. If what is actually being turned off is the __radio__, then call it turning off the wireless radio. What I keep butting my head against is not being able to *control* what is going on. In my mind a 'mesh' is one interface, and an 'AP' is another interface. I would like to turn off the mesh when there are no local XOs, and no school server. You are saying that the 'AP' would get turned off as well. Not something I prefer. Mikus, tickets and logs, logs and tickets. The last time I focused on connectivity was Apr/May. What I concluded then was that my tickets got closed depending on the effect they had on the code -- *not* on whether I as a user could now experience consistent system behavior. I'm willing to file a ticket when I see something happening -- such as an error when accessing a Jabber server (though one such ticket was closed as 'invalid' - because that particular server had not given the expected answer). But it is difficult to decide what to ticket/log when I do not see something happening -- for instance, what if a connection to a Jabber server were never attempted by my XO? Besides, I post from home - where I do not have a wireless AP. To try anything, I have to go somewhere else, where I do not have access to my notes, etc. Not easy for me to record details. [You ask which establishment provided the AP? Does it *really* make a difference to you whether it was an establishment on 1st street, or one on 6th street ???] The mesh and the AP are mutually exclusive. gabble and salut are independent of the network topology. I'm sorry, but these memes have been said so many different ways that they no longer convey any information to me. If taking down the mesh can take down the AP, how can they be exclusive? If salut listens on the mesh, isn't that a dependence on there being a mesh? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
On Tue, Aug 5, 2008 at 1:30 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote: Morgan wrote: Connecting to an AP disables the mesh, so I don't see the value of what you want. Turning off the mesh while you are connected to a mesh channel would simply (in the proposal) turn the wireless radio off completely, resulting in neither gabble nor salut able to operate. Then I believe the language being used is imprecise. To me, turning off the mesh means turning off the __mesh__. If what is actually being turned off is the __radio__, then call it turning off the wireless radio. I don't actually believe this is the spec at all. I specifically removed the turn off actions from the Mesh (and APs) because we /don't/ want to turn off the radio for either of these cases, since that would naturally prevent the other from working. I don't want to conflate disconnect from AP and turn off the mesh with turn off the radio at all. What I keep butting my head against is not being able to *control* what is going on. In my mind a 'mesh' is one interface, and an 'AP' is another interface. I would like to turn off the mesh when there are no local XOs, and no school server. You are saying that the 'AP' would get turned off as well. Not something I prefer. Right, I agree with you. Turning off the Mesh should be possible in theory; it makes sense. But as I understand it, at present, the only way to turn off any NM device it to associate with another...in this case, an AP. I'd /much/ prefer to have these be independent, so that it's possible to connect/disconnect and/or turn on/turn off these devices without interference. The mesh and the AP are mutually exclusive. gabble and salut are independent of the network topology. I'm sorry, but these memes have been said so many different ways that they no longer convey any information to me. If taking down the mesh can take down the AP, how can they be exclusive? If salut listens on the mesh, isn't that a dependence on there being a mesh? They are mutually exclusive in that you cannot, at present, be connected to both at the same time. It's one or the other, not both, though I believe the goal is to change that in the future. As I mentioned before, I strongly disagree with the idea that turning off the mesh should be connected to turning off the radio. - Eben mikus ___ Sugar mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/sugar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
Hi Mikus On Sun, Aug 3, 2008 at 04:10, Mikus Grinbergs [EMAIL PROTECTED] wrote: Eben wrote: There has been lots of confusion about the difference between mesh and APs. They're really not the same at all, apart from the fact that they both depend on the radio. The new design no longer treats the mesh channels as objects in the Neighborhood view. Instead, there will be (is? not sure if the patch landed yet) a mesh device in the Frame, which you can turn on (and off?) at whim. I am anxiously waiting to *use* some of these improvements. For the last several months, I've __NOT__ been able to connect to a Jabber server. When I look at the running tasks, it's always salut. The XO is supposed to retry reaching the Jabber server every 320 seconds -- but mine (using Joyride) has not had recent success. Last spring, this all worked for me the way it was supposed to work. But since then, new OLPC software versions have been released -- and in my experience my OLPC is no longer connecting to a Jabber server. Please file a bug the next time you can reproduce this. Please include presenceservice.log and telepathy-gabble.log with debug logs enabled in .xsession. (http://wiki.laptop.org/go/Telepathy-debug) If there is a regression, it's a bug. Please don't hesitate to log bugs. In the worst case we never find a reproducible problem. In the second worst case, we close it as a duplicate of another existing bug. No, I change my mind: in the worst case there is a regression, and we never get a trackable record of it or logs. Please log bugs at the slightest hint of a problem that happens more than once, and include all possible logs you can. [I don't have wireless at home, so I have to wait until I go to some sort of establishment that provides an AP. But even when I am able to surf the net from my XO, I'm not connecting to any Jabber server. I've tried many - *surely* at least one should be working.] One quick way to see if a jabber server is up: (you will need to install nc first, with sudo yum install nc) $ nc xochat.org 5222 Type anything and press Enter, you should see some XML returned if the server is up, e.g. ?xml version='1.0'?stream:stream xmlns='jabber:client' xmlns:stream=... If you get connection refused, the server's definitely down. If it just hangs and doesn't show the XML stuff, it's overloaded and non-responsive - consider it down. For people in my situation, what I want is to be able to 'turn off' the XO trying to reach the 'school server' via the mesh (I'm a G1G1 user, and will *never* have a 'school server' where I live). Instead, I want my XO to try HARDER, via the AP to which it is connected, to reach whatever (Jabber) server I've specified. mikus p.s. These may be written down somewhere - but I've not been able to find explanations for how to move a connection : (A) Suppose a kid is communicating with his 'school server' via the mesh. Then he walks so far away that his radio no longer reaches the school. If he happens to be within range of an alternate AP, how would the transfer from 'using mesh addressing for the school' to 'using internet addressing for the school' be handled? [Does the kid ever have to do something manually, such as re-starting Sugar ?] You have to explicitly connect to the AP by clicking on it, since the mesh could heal at any time by you walking back or someone else appearing within range. The schoolserver would only be accessible via the AP if it has a public DNS entry and accepts connections from the outside. Connections over the mesh to the schoolserver typically have an RFC1918 private IP address. (B) Suppose a kid is using the Jabber facilities at his school to contact an overseas buddy. Suddenly the communications link between the school and the internet fails. If the kid happens to be within range of an alternate AP, does he have to do something manually (such as entering the name of a non-school Jabber server) to re-establish Jabber contact to the outside world ? At this stage, the overseas buddy would have to be registered on this kid's school jabber server, to collaborate, since we do not have server to server federation. In that case, if this kid can't access his school jabber server in any way, communication breaks down. See above about connecting via AP. Alternatively, this kid would have to register with an external jabber server (thereby disconnecting from his own school jabber server) to communicate with the remote buddy in the first place. Either way, no changing jabber server names is required to *re-establish* communication, but he would have to switch to the AP by clicking on it. Regards Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
On Sat, Aug 02, 2008 at 10:10:09PM -0400, Mikus Grinbergs wrote: Eben wrote: There has been lots of confusion about the difference between mesh and APs. They're really not the same at all, apart from the fact that they both depend on the radio. The new design no longer treats the mesh channels as objects in the Neighborhood view. Instead, there will be (is? not sure if the patch landed yet) a mesh device in the Frame, which you can turn on (and off?) at whim. I am anxiously waiting to *use* some of these improvements. Sorry for the delay in landing #6995 - there are a number of improvements I keep trying out, delaying the patch. But, this time, it's almost ready. I had one volunteer on IRC who might be able to help me test before I ask for wider testing. For people in my situation, what I want is to be able to 'turn off' the XO trying to reach the 'school server' via the mesh (I'm a G1G1 user, and will *never* have a 'school server' where I live). Instead, I want my XO to try HARDER, via the AP to which it is connected, to reach whatever (Jabber) server I've specified. I am in the same situation and would like the same feature, but I don't think things are too possible with the current NM: see http://lists.laptop.org/pipermail/devel/2008-August/017686.html mikus Martin p.s. These may be written down somewhere - but I've not been able to find explanations for how to move a connection : It Just Happens - Network Manager notices a connection is down (somehow? probably device- kernel-specific) and starts looking for new ones. But applications probably won't like this. There was a huge thread on devel@ in Jan/Feb IIRC debating this, but basically I think activities (the underlying APIs they use, mostly) will vary in how well they deal with IPs changing and their network sockets getting closed. (A) Suppose a kid is communicating with his 'school server' via the mesh. Then he walks so far away that his radio no longer reaches the school. If he happens to be within range of an alternate AP, how would the transfer from 'using mesh addressing for the school' to 'using internet addressing for the school' be handled? [Does the kid ever have to do something manually, such as re-starting Sugar ?] ibid. (B) Suppose a kid is using the Jabber facilities at his school to contact an overseas buddy. Suddenly the communications link between the school and the internet fails. If the kid happens to be within range of an alternate AP, does he have to do something manually (such as entering the name of a non-school Jabber server) to re-establish Jabber contact to the outside world ? No idea, sorry, but I don't think your question is a conventional one. Jabber servers can be federated but I don't know of any that are, nor if and XS's jabber server is. But I think you're mixing up connected to a Jabber server / server-cloud and connected to an AP. The latter is a pre-requisite for the former but doesn't necessarily imply reachability of the former. So if you change your AP, that may have nothing to do with connectivity to the jabber server by which one was chatting to an overseas buddy. pgpdw5lvJLgi6.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
On Mon, Aug 4, 2008 at 16:42, Martin Dengler [EMAIL PROTECTED] wrote: On Sat, Aug 02, 2008 at 10:10:09PM -0400, Mikus Grinbergs wrote: p.s. These may be written down somewhere - but I've not been able to find explanations for how to move a connection : It Just Happens - Network Manager notices a connection is down (somehow? probably device- kernel-specific) and starts looking for new ones. But applications probably won't like this. There was a huge thread on devel@ in Jan/Feb IIRC debating this, but basically I think activities (the underlying APIs they use, mostly) will vary in how well they deal with IPs changing and their network sockets getting closed. Yes, #5620 - activity collaboration can't migrate from one connection to another, and doesn't typically detect a break. Regards Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Currently, only icons from the LOCAL mesh to which I am connected will show up in my Neighborhood view. My question in this topic is: What do I need to do to have icons from REMOTE locations show up ? Sorry for the delay in landing #6995 - there are a number of improvements I keep trying out, delaying the patch. I'm using the latest build versions - as of this morning, the mesh icons are gone from Neighborhood view, but *none* are as yet appearing in Frame. (I see the correct local XO icons in Neighborhood, so the mesh must be working.) What I am particularly interested in was Eben's statement that the user could turn the mesh on/off with the icon in the Frame. I'm getting much too much 'salut' - I'm hoping that turning off the mesh (*all* of its channels) would give more emphasis to 'gabble'. Suddenly the communications link between the school and the internet fails. If the kid happens to be within range of an alternate AP, does he have to do something manually (such as entering the name of a non-school Jabber server) to re-establish Jabber contact to the outside world ? But I think you're mixing up connected to a Jabber server / server-cloud and connected to an AP. I don't think I am. When I go to someplace that has wireless, and check my XO, I'm seeing that it connects fine to websites (meaning that the AP must be working), but whenever I then do 'ps -A' I see 'salut' (meaning that 'gabble' must be giving up). Currently there is only a *single* field for specifying the Jabber server name (and I've tried many names) - so I expect that when the currently specified one is not working, the user has to manually enter the name of a different Jabber server. What my question dealt with was how is use of the 'school server' as the Jabber server specified? [I have not seen an answer.] - If the kid has to manually enter an internet-resolvable name for the 'school server', then obviously while the 'school server' is down, the kid has to enter a different name to continue to use Jabber. - But if the use of the 'school server' as __also__ the Jabber server is *automatic* whenever the XO connects to the 'school server', then my question is When the Jabber server at the school fails, HOW does the XO know to start instead using the specified Jabber server name for Jabber-type connections? [What lay behind my question was the suspicion that while the XO had a working mesh, and was vigorously trying to reach a 'school server' (using that server's mesh-resolvable name), it was giving short shrift to any 'gabble' attempts to reach (through the AP) the Jabber server whose name had been specified in the Control Panel.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] How do I connect to a Jabber server ?
On 4 Aug 2008, at 23:40, Mikus Grinbergs wrote: My _wish_ is simple: I want a chance to contact (for Chat, or for collaboration) another XO at a different location. Basically, for me to initiate that, that other XO's icon needs to be shown in my Neighborhood view. Currently, only icons from the LOCAL mesh to which I am connected will show up in my Neighborhood view. My question in this topic is: What do I need to do to have icons from REMOTE locations show up ? If gabble fails to get to a named jabber server (set in the control panel) it defaults to salute. This may be via an access point (if you've attached to one) or via the mesh (if it has no luck with an AP). Once it's looking at the mesh it tries each of the 3 slices of spectrum available (1, 6 11) looking for a school server. If it find none it seems to default to go sit on mesh, channel 1, hoping to meet another XO there (though it may re-scan occasionally). Now the scanning sequence used to be as stated above (previous official releases), but in recent joyrides I find my XO immediately attaches to my preferred AP and doesn't waist time sniffing the mesh (I like this, but 3 kids under a tree may not). The xochat.org jabber server is the one I seem to reliably attach to for my XO testing, though I'd love to see an official developer jabber server, so as not to pester real G1G1 users with my tests, and so we can 'eat our own dogfood' in a dev environment**. Connecting to a remote jabber server is currently the way to see and share with other remote users*** in the neighborhood. ** perhaps Sugar Labs could run such an environment? *** recently, can even work with non XO jabber clients, though I've not been able to test properly yet. Note: current joyrides past 2241seem to have a broken eth0 networking, allegedly the (local) msh0 is still working but I have no way to test that side of things with a single XO. --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
How do I connect to a Jabber server ?
Albert just filed a ticket saying that when there is an ethernet connection, the user would expect *that* to be used (instead of wireless). I agree. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
How do I connect to a Jabber server ?
Eben wrote: There has been lots of confusion about the difference between mesh and APs. They're really not the same at all, apart from the fact that they both depend on the radio. The new design no longer treats the mesh channels as objects in the Neighborhood view. Instead, there will be (is? not sure if the patch landed yet) a mesh device in the Frame, which you can turn on (and off?) at whim. I am anxiously waiting to *use* some of these improvements. For the last several months, I've __NOT__ been able to connect to a Jabber server. When I look at the running tasks, it's always salut. The XO is supposed to retry reaching the Jabber server every 320 seconds -- but mine (using Joyride) has not had recent success. Last spring, this all worked for me the way it was supposed to work. But since then, new OLPC software versions have been released -- and in my experience my OLPC is no longer connecting to a Jabber server. [I don't have wireless at home, so I have to wait until I go to some sort of establishment that provides an AP. But even when I am able to surf the net from my XO, I'm not connecting to any Jabber server. I've tried many - *surely* at least one should be working.] For people in my situation, what I want is to be able to 'turn off' the XO trying to reach the 'school server' via the mesh (I'm a G1G1 user, and will *never* have a 'school server' where I live). Instead, I want my XO to try HARDER, via the AP to which it is connected, to reach whatever (Jabber) server I've specified. mikus p.s. These may be written down somewhere - but I've not been able to find explanations for how to move a connection : (A) Suppose a kid is communicating with his 'school server' via the mesh. Then he walks so far away that his radio no longer reaches the school. If he happens to be within range of an alternate AP, how would the transfer from 'using mesh addressing for the school' to 'using internet addressing for the school' be handled? [Does the kid ever have to do something manually, such as re-starting Sugar ?] (B) Suppose a kid is using the Jabber facilities at his school to contact an overseas buddy. Suddenly the communications link between the school and the internet fails. If the kid happens to be within range of an alternate AP, does he have to do something manually (such as entering the name of a non-school Jabber server) to re-establish Jabber contact to the outside world ? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
