Re: OLPC does end run around IP addresses

2010-01-14 Thread Bernie Innocenti
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

Re: OLPC does end run around IP addresses

2010-01-13 Thread David Woodhouse
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).

Re: OLPC does end run around IP addresses

2010-01-13 Thread Mikus Grinbergs
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

Re: OLPC does end run around IP addresses

2010-01-13 Thread David Woodhouse
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

Re: OLPC does end run around IP addresses

2010-01-10 Thread James Cameron
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

Re: OLPC does end run around IP addresses

2010-01-09 Thread C. Scott Ananian
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

Re: OLPC does end run around IP addresses

2010-01-09 Thread Mikus Grinbergs
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

Re: OLPC does end run around IP addresses

2010-01-09 Thread Sascha Silbe
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

Re: OLPC does end run around IP addresses

2010-01-09 Thread Mikus Grinbergs
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

OLPC does end run around IP addresses

2010-01-08 Thread Mikus Grinbergs
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