After a quick test, with the olpc 802 build and all the newer ones
(including dextrose), I saw that only on the 802 build, Network Manager
starts autoip after the dhcpclient has given up.
Researching on the web, I found this [1]. Basically autoip was causing
confusion when making the users to
On Tue, Jan 11, 2011 at 02:40:23PM -0300, Martin Abente wrote:
Researching on the web, I found this [1]. Basically autoip was causing
confusion when making the users to believe that the ethernet
connection was _always_ successful.
Caused by conflating two concepts; network interface
On 11 Jan 2011, at 22:57, James Cameron qu...@laptop.org wrote:
On Tue, Jan 11, 2011 at 02:40:23PM -0300, Martin Abente wrote:
Researching on the web, I found this [1]. Basically autoip was causing
confusion when making the users to believe that the ethernet
connection was _always_
On Tue, Jan 11, 2011 at 11:46:24PM +, Gary Martin wrote:
Ooh, interesting. I take it the below 'indicate connected to provider
and, I seem to be able to talk to some Internet servers' is the UI
direction you've seen provided for this before?
On those routers and last mile devices, yes.
Sorry for the delay. Here's my latest update. Did this using only two XO
1.0's, running Build 360. This could all be behaviour by design, and I'm
not reporting any bugs here, just listing what I've done in testing.
Each command entered on one XO, then the other in turn.
Fresh copy-nand
Kevin, here is how my XOs communicate:
1) I haven't seen any reason to ever go to Gnome -- instead I've
written several scripts which I run from Terminal, and which set up
communication between XOs (when it hasn't been setup automatically).
2) Much of my inter-XO communication has been using
Update on the request for testing:
As per below, adaptors and cable have already been verified.
As base desired behaviour, verified XO1 running Build 802 auto-assigns
itself an IPv4 169 address and is able to connect to a Windows machine.
Alas, on the testing phase:
Used two newly refreshed XO
On Sun, Dec 19, 2010 at 02:22:01PM -0500, Kevin Gordon wrote:
All above testing done in root in the terminal from Sugar activity.
Sorry, I dont know how to the step request of : check Sugar frame for
an IP address assignment. I also dont know how to check
collaboration through sharing, Sugar
James wrote:
The frame will have an icon for the USB ethernet adapter.
In my experience this is true *IF* the ethernet adapter has been
assigned an IP address by an external DHCP server. In those cases where
I manually assigned a (non-169.x.x.x) IPv4 address to the adapter, the
Frame did NOT
On Sun, Dec 19, 2010 at 07:18:43PM -0600, Mikus Grinbergs wrote:
James wrote:
The frame will have an icon for the USB ethernet adapter.
In my experience this is true *IF* the ethernet adapter has been
assigned an IP address by an external DHCP server. In those cases where
I manually
Cc: KG Gmail
Cc: devel@lists.laptop.org
Subject: Re: USB Ethernet test
Sent: Dec 19, 2010 20:42
On Sun, Dec 19, 2010 at 07:18:43PM -0600, Mikus Grinbergs wrote:
James wrote:
The frame will have an icon for the USB ethernet adapter.
In my experience this is true *IF* the ethernet adapter has
On Mon, Dec 20, 2010 at 02:27:58AM +, Kevin Gordon wrote:
Have to say I'm seeing the same as Mikus, the auto-assigned icons do
not appear in the frame. The wireless ones, the 3G modems do appear,
and the USB when hooked to a DHCP providing ethernet router do. But
on any of the XO 1s and
Folks:
Just writing to let you know that I'm still working on the test case :
http://dev.laptop.org/ticket/10541#comment:http://dev.laptop.org/ticket/10541#comment:2
I've set up two Windows machines each with a USB/Ethernet connector and a
crossover cable and disabled all networking interfaces
13 matches
Mail list logo
