Re: [Testing] os240py - collaboration over wireless
El Mon, 31-05-2010 a las 15:42 +0200, Tomeu Vizoso escribió: I was referring to the local firewall, would be good to be able to rule out that the iptables firewall wasn't configured correctly on these images (has happened before). Both the iptables and ip6tables sysvinit services are disabled in osXXXpy. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
bernie wrote: El Mon, 31-05-2010 a las 15:42 +0200, Tomeu Vizoso escribió: I was referring to the local firewall, would be good to be able to rule out that the iptables firewall wasn't configured correctly on these images (has happened before). Both the iptables and ip6tables sysvinit services are disabled in osXXXpy. a bit off-topic, but just fyi -- i know you have power management disabled, but when enabled, powerd wants to use iptables to do network activity tracking. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
El Tue, 01-06-2010 a las 10:42 +1000, James Cameron escribió: On Mon, May 31, 2010 at 06:54:28PM -0500, Daniel Drake wrote: I'm pretty sure this will be another case of there being no default multicast route. Yep, that's it. Sugar is entirely relying on the existence of this multicast route, and it is not present on os240py. It can temporarily be added after mesh is started: ip route add 224.0.0.0/4 dev msh0 And after that, I've tested that Chat activity when shared appears in Neighbourhood View of other laptops, and that another laptop running os240py can join it. Conversation works fine. Bernie, modules/base/kspost.10.core.inc in olpc-os-builder handles this for ad-hoc. Presumably it needs a similar thing for mesh. Thanks for catching it! I wonder how it was done back in build 801. I'll be traveling around until Friday night. Daniel, could you apply a patch to olpc-os-builder? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
El Wed, 02-06-2010 a las 16:00 -0400, Paul Fox escribió: a bit off-topic, but just fyi -- i know you have power management disabled, but when enabled, powerd wants to use iptables to do network activity tracking. Oh, this explains what those odd iptables rules were for :-) Anyway, none of the active iptables rules seems to be blocking incoming or outgoing network traffic on os240py. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On Thu, Jun 03, 2010 at 12:34:30AM -0400, Bernie Innocenti wrote: I'll be traveling around until Friday night. Daniel, could you apply a patch to olpc-os-builder? Here's a simple patch. Could be better, but it works for me. Tested on os240py, but not tested through a complete build using olpc-os-builder. From 3ab33d16f6e9aa1ee384f93a3fd458db8581ee6c Mon Sep 17 00:00:00 2001 From: James Cameron qu...@laptop.org Date: Thu, 3 Jun 2010 15:41:14 +1000 Subject: [PATCH] add multicast route for mesh collaboration Add a multicast route when msh0 is raised by Network Manager. Fix a minor backslash quoting issue on eth0. Tested by creating the file on os240py and starting mesh, then checking with ip route list command and confirming that a Chat activity shared from an os802 laptop causes an icon to appear in the Neighbourhood View of the os240py laptop. --- modules/base/kspost.10.core.inc | 19 ++- 1 files changed, 14 insertions(+), 5 deletions(-) diff --git a/modules/base/kspost.10.core.inc b/modules/base/kspost.10.core.inc index 40c7483..03e2345 100644 --- a/modules/base/kspost.10.core.inc +++ b/modules/base/kspost.10.core.inc @@ -96,12 +96,21 @@ echo NM_IGNORE_HOSTNAME_LOCALHOST=yes /etc/sysconfig/network cat /etc/NetworkManager/dispatcher.d/adhoc-route EOF #!/bin/sh # workaround for http://dev.laptop.org/ticket/9669 -[ \$1 = eth0 ] || exit 0 -if [ \$2 = down ]; then - /sbin/ip route del 224.0.0.0/4 dev eth0 /dev/null +if [ \$1 = eth0 ]; then +if [ \$2 = down ]; then +/sbin/ip route del 224.0.0.0/4 dev eth0 /dev/null else - /sbin/iwconfig \$1 | /bin/grep -q Mode:Ad-Hoc \ - /sbin/ip route add 224.0.0.0/4 dev eth0 /dev/null +else +/sbin/iwconfig eth0 | /bin/grep -q Mode:Ad-Hoc \\ +/sbin/ip route add 224.0.0.0/4 dev eth0 /dev/null +fi +fi +if [ \$1 = msh0 ]; then +if [ \$2 = down ]; then +/sbin/ip route del 224.0.0.0/4 dev msh0 /dev/null +else +/sbin/ip route add 224.0.0.0/4 dev msh0 /dev/null +fi fi exit 0 EOF -- 1.7.1 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
multicast route missing on ad-hoc+mesh (was: Re: [Testing] os240py - collaboration over wireless)
Excerpts from James Cameron's message of Tue Jun 01 00:42:38 + 2010: Yep, that's it. Sugar is entirely relying on the existence of this multicast route, and it is not present on os240py. It can temporarily be added after mesh is started: ip route add 224.0.0.0/4 dev msh0 [...] Bernie, modules/base/kspost.10.core.inc in olpc-os-builder handles this for ad-hoc. Presumably it needs a similar thing for mesh. What's the upstream ticket for this bug (the multicast route being missing)? This might explain quite a bit of the trouble I had with collaboration (though not all of it). Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: multicast route missing on ad-hoc+mesh (was: Re: [Testing] os240py - collaboration over wireless)
On 1 June 2010 02:55, Sascha Silbe sascha-ml-ui-sugar-olpc-de...@silbe.org wrote: Excerpts from James Cameron's message of Tue Jun 01 00:42:38 + 2010: Yep, that's it. Sugar is entirely relying on the existence of this multicast route, and it is not present on os240py. It can temporarily be added after mesh is started: ip route add 224.0.0.0/4 dev msh0 [...] Bernie, modules/base/kspost.10.core.inc in olpc-os-builder handles this for ad-hoc. Presumably it needs a similar thing for mesh. What's the upstream ticket for this bug (the multicast route being missing)? This might explain quite a bit of the trouble I had with collaboration (though not all of it). You can find the discussion on the NetworkManager list. It wasn't concluded, Dan Williams needs to be prodded more so that we can come up with a solution. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On Mon, May 31, 2010 at 07:03, James Cameron qu...@laptop.org wrote: I've reproduced no sharing over mesh on os240py. Activity sharing works via access point. Activity sharing works via Create new wireless network aka ad-hoc. I can only think of two reasons for sharing not working in mesh but presence yes: - network congestion, - different link-local address setup, - firewall settings. Debug logs for telepathy-salut and the output of /var/log/messages would help diagnosing this. Regards, Tomeu -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
I can only think of two reasons for sharing not working in mesh but presence yes: - network congestion, In my case, there appear to be no other radio signals present. If there is network congestion, the XOs are generating it themselves. - different link-local address setup, What I found interesting (by hovering over the respective icons in Frame), was that the SAME IP-address was assigned when connecting to the ad-hoc wireless network as had been assigned (before there was an ad-hoc network) when connecting using the mesh icons in Neighborhood View. - firewall settings. In my case, I'm connecting XO-to-XO. There is no firewall. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On Mon, May 31, 2010 at 15:35, Mikus Grinbergs mi...@bga.com wrote: I can only think of two reasons for sharing not working in mesh but presence yes: - network congestion, In my case, there appear to be no other radio signals present. If there is network congestion, the XOs are generating it themselves. Would be good to be able to rule that out, but I don't think that's too probable in your case. - different link-local address setup, What I found interesting (by hovering over the respective icons in Frame), was that the SAME IP-address was assigned when connecting to the ad-hoc wireless network as had been assigned (before there was an ad-hoc network) when connecting using the mesh icons in Neighborhood View. - firewall settings. In my case, I'm connecting XO-to-XO. There is no firewall. I was referring to the local firewall, would be good to be able to rule out that the iptables firewall wasn't configured correctly on these images (has happened before). Regards, Tomeu mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On 31 May 2010 00:03, James Cameron qu...@laptop.org wrote: I've reproduced no sharing over mesh on os240py. Activity sharing works via access point. Activity sharing works via Create new wireless network aka ad-hoc. I'm pretty sure this will be another case of there being no default multicast route. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On Mon, May 31, 2010 at 06:54:28PM -0500, Daniel Drake wrote: I'm pretty sure this will be another case of there being no default multicast route. Yep, that's it. Sugar is entirely relying on the existence of this multicast route, and it is not present on os240py. It can temporarily be added after mesh is started: ip route add 224.0.0.0/4 dev msh0 And after that, I've tested that Chat activity when shared appears in Neighbourhood View of other laptops, and that another laptop running os240py can join it. Conversation works fine. Bernie, modules/base/kspost.10.core.inc in olpc-os-builder handles this for ad-hoc. Presumably it needs a similar thing for mesh. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
Activity sharing works via access point. Activity sharing works via Create new wireless network aka ad-hoc. I'm pretty sure this will be another case of there being no default multicast route. I normally use wired ethernet, not wireless. Back some months, I asked how come all the XOs on my ethernet saw each other (i.e., there were icons for all the XOs in every system's Neighborhood View), when some systems had static ethernet IP-addresses (192.168...) and other systems had ad-hoc network IP-addresses (at that time, the ad-hoc network was assigning IP-addresses in the 10... range). The answer I got was that the presence detection (or something) capability used multicast, rather than depending upon standard interface defined IP-addresses. What I noticed with os240py was that as soon as both system had connected to the same wireless Mesh channel, each saw the other (i.e., Neighborhood View at both systems showed the icons for both systems). Are you saying that the multicast capability that was explained to me months ago was NOT active in os240py with only Mesh connected ? [ Is there a command that I can manually enter at a Mesh-connected os240py system to activate such a 'default multicast route' ? ] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
os240py is based on Sugar 0.88, but months ago we were talking to you about Sugar 0.84, so chances are there is a change to how presence is transported. os240py unmodified, without a multicast route, associated with mesh does show XO icons in the neighbourhood view. Yet it does not show shared activities. Therefore it can't be using the same underlying technique. We may have to unlearn things we had learned. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
On Mon, May 31, 2010 at 08:59:49PM -0500, Mikus Grinbergs wrote: The answer I got was that the presence detection (or something) capability used multicast, rather than depending upon standard interface defined IP-addresses. I've just booted one laptop on os240py to use mesh, but with packet capturing on one that was already booted. The captured packets were interesting. After the booting laptop established an IP address, there was a multicast DNS exchange, followed by an explicit connection to the presence service on TCP port 5298 on the already booted laptop. What I noticed with os240py was that as soon as both system had connected to the same wireless Mesh channel, each saw the other (i.e., Neighborhood View at both systems showed the icons for both systems). I see that too. Are you saying that the multicast capability that was explained to me months ago was NOT active in os240py with only Mesh connected ? Yes, you can verify this by using ip route list, and on os240py there is no multicast route, but in the same network configuration on os802 there is. [ Is there a command that I can manually enter at a Mesh-connected os240py system to activate such a 'default multicast route' ? ] The ip route add command I gave will do this. The ip route list command will show the change. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] os240py - collaboration over wireless
I've reproduced no sharing over mesh on os240py. Activity sharing works via access point. Activity sharing works via Create new wireless network aka ad-hoc. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
