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.
T
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
> 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 forwar
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). W
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 no
> 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
__
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 multica
>> 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.
>>
>> M
On Sat, Jan 9, 2010 at 1:35 AM, 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.
>
> Just now I've been testing wit
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 com
10 matches
Mail list logo