Re: OLPC does end run around IP addresses
On Wed, 2010-01-13 at 09:02 -0600, Mikus Grinbergs wrote: Surely all your machines can communicate quite happily using IPv6 link-local addresses? Why this fascination with Legacy IP? Because none of my facilities (including my desktops) are set up to use IPv6. You'd be surprised. These days, many modern Linux distributions -- and even crap like Windows and OS X -- will setup a link-local IPv6 address automatically in the default configuration. So, if you really do hate IPv6, you'll have to work quite hard to completely turn it off on all your facilities :-) -- // 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: OLPC does end run around IP addresses
On Sat, 2010-01-09 at 04:03 -0600, Mikus Grinbergs wrote: What I see the XOs doing is an end run around my concept of how remote nodes are supposed to be accessed. I believe 'ping' is behaving the standards-compliant way (192.168.1.0/24 does not access 169.254.0.0/16, and vice versa). Whereas what shows up in the XO Neighborhood View (and in 'olpc-xos') appears to ignore standards-compliance. Surely all your machines can communicate quite happily using IPv6 link-local addresses? Why this fascination with Legacy IP? -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
Surely all your machines can communicate quite happily using IPv6 link-local addresses? Why this fascination with Legacy IP? Because none of my facilities (including my desktops) are set up to use IPv6. More to the point -- I have an emotional prejudice against IPv6 -- I am NOT looking forward to the day when my refrigerator has its own IPv6 address, and reports to third parties how much beer I have downed. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
On Wed, 2010-01-13 at 09:02 -0600, Mikus Grinbergs wrote: Because none of my facilities (including my desktops) are set up to use IPv6. If you're running any recent OS, I strongly suspect you'll find that they are. More to the point -- I have an emotional prejudice against IPv6 -- I am NOT looking forward to the day when my refrigerator has its own IPv6 address, and reports to third parties how much beer I have downed. Nothing prevents it from doing that with Legacy IP either :) -- David WoodhouseOpen Source Technology Centre david.woodho...@intel.com Intel Corporation ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
On Sat, Jan 09, 2010 at 12:35:41AM -0600, Mikus Grinbergs wrote: I don't have wireless - my XOs are on ethernet (using interface eth1). Currently I am running without a DNS server - meaning that I need to issue explicit commands at each XO to set its eth1 IP address. A DNS server does not normally assist much with assigning IPv4 addresses ... I think you mean DHCP server. To correct running without DHCP server, you could configure dnsmasq, which is installed on current builds by default, or can be installed using yum. Edit the file /etc/dnsmasq.conf . Use /etc/init.d/dnsmasq start to start a temporary server. Use chkconfig to ask for the server to be started on boot. References: http://www.thekelleys.org.uk/dnsmasq/doc.html -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
On Sat, Jan 9, 2010 at 1:35 AM, Mikus Grinbergs mi...@bga.com wrote: I don't have wireless - my XOs are on ethernet (using interface eth1). Currently I am running without a DNS server - meaning that I need to issue explicit commands at each XO to set its eth1 IP address. Just now I've been testing with a deliberately non-customized XO-1 -- I have NOT issued any commands to it to set its IP address. It is running build 802B1, and has by default set IP addresses of 169.254... for its eth0 and msh0 interfaces (its ethernet eth1 interface has only a default IPv6 address). Netstat at that XO shows only the 169.254 routes. The other XOs on the ethernet have IPv4 IP addresses only on eth1, in the 192.168.1.. range. They have no IPv4 addresses for their radios. Netstat at those XOs shows only the 168.192.1 route. What I find interesting is that Neighborhood View at every XO shows *all* other XOs (plus their names) physically attached to the ethernet. 'olpc-xos' shows the non-customized XO with its eth0 (radio) IP address; the other XOs are shown with their eth1 (ethernet) IP addresses. My conclusion: The XOs are recognizing each other over the ethernet, despite having non-pingable IP address identities activated. The 169.x.x.x subnet is reserved for link-local addresses, which is what these are. They are pingable from the local link. It's all standards-compliant and kosher, be not afraid. http://en.wikipedia.org/wiki/Link-local_address --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
What I find interesting is that Neighborhood View at every XO shows *all* other XOs (plus their names) physically attached to the ethernet. 'olpc-xos' shows the non-customized XO with its eth0 (radio) IP address; the other XOs are shown with their eth1 (ethernet) IP addresses. My conclusion: The XOs are recognizing each other over the ethernet, despite having non-pingable IP address identities activated. The 169.x.x.x subnet is reserved for link-local addresses, which is what these are. They are pingable from the local link. It's all standards-compliant and kosher, be not afraid. http://en.wikipedia.org/wiki/Link-local_address I'm not afraid (nor am I looking for help). I understand whence the 169.x.x.x subnet comes from. My point is that ALL the XOs show up in each Neighborhood View, even though the other XOs (192.168.1..) cannot ping the non-customized XO (169.254...), nor can the non-customized XO ping the others. What I see the XOs doing is an end run around my concept of how remote nodes are supposed to be accessed. I believe 'ping' is behaving the standards-compliant way (192.168.1.0/24 does not access 169.254.0.0/16, and vice versa). Whereas what shows up in the XO Neighborhood View (and in 'olpc-xos') appears to ignore standards-compliance. As I said, I am not looking for help. I am sharing an observation, which I believe would not occur if I were not using XOs. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
On Sat, Jan 09, 2010 at 04:03:27AM -0600, Mikus Grinbergs wrote: My point is that ALL the XOs show up in each Neighborhood View, even though the other XOs (192.168.1..) cannot ping the non-customized XO (169.254...), nor can the non-customized XO ping the others. IIRC Salut is using some multicast protocol. Multicast has its own set of IP addresses [1], with Salut most likely using one from the link-local range (224./24). So Salut should work IFF all machines are on the same ethernet segment. [1] http://en.wikipedia.org/wiki/IP_multicast#IP_multicast_addressing_assignments CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC does end run around IP addresses
IIRC Salut is using some multicast protocol. Multicast has its own set of IP addresses [1], with Salut most likely using one from the link-local range (224./24). So Salut should work IFF all machines are on the same ethernet segment. Thank you -- now it makes sense. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OLPC does end run around IP addresses
I don't have wireless - my XOs are on ethernet (using interface eth1). Currently I am running without a DNS server - meaning that I need to issue explicit commands at each XO to set its eth1 IP address. Just now I've been testing with a deliberately non-customized XO-1 -- I have NOT issued any commands to it to set its IP address. It is running build 802B1, and has by default set IP addresses of 169.254... for its eth0 and msh0 interfaces (its ethernet eth1 interface has only a default IPv6 address). Netstat at that XO shows only the 169.254 routes. The other XOs on the ethernet have IPv4 IP addresses only on eth1, in the 192.168.1.. range. They have no IPv4 addresses for their radios. Netstat at those XOs shows only the 168.192.1 route. What I find interesting is that Neighborhood View at every XO shows *all* other XOs (plus their names) physically attached to the ethernet. 'olpc-xos' shows the non-customized XO with its eth0 (radio) IP address; the other XOs are shown with their eth1 (ethernet) IP addresses. My conclusion: The XOs are recognizing each other over the ethernet, despite having non-pingable IP address identities activated. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
