On 11 Jan 2011, at 22:57, James Cameron <[email protected]> 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_ successful. > > Caused by conflating two concepts; network interface configured, vs user > perception of a useful network. > >> http://www.mail-archive.com/[email protected]/msg04835.html > > I disagree with Jerone. The connection is not useless, it is ready. > > Once another node joins the network, it will be accessible. However, I > don't think the connection state should be given to the user as a claim > that they have a useful network that will carry their packets to the > internet. That's a fundamental design issue.
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? FWIW: OS X uses a red (no network), amber (a network found), green (can talk to some remote Internet server) visual warning on network status. Regards, --Gary > It can be made to work in our case, just by assigning an IP > automatically, since Sugar can operate well on a network that does not > carry packets to the internet. > > p.s. modern consumer DSL and wireless routers in Australia deal with > this issue by adding an indicator; one LED indicates connected to > provider, another LED indicates success of ping to one of a set of > predefined test IPs on the internet. > > -- > James Cameron > http://quozl.linux.org.au/ > _______________________________________________ > Devel mailing list > [email protected] > http://lists.laptop.org/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
