Need instructions on how to set up a cluster of computers so they collaborate.

Bug #419240 reported by Caroline
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sugar on a Stick
Triaged
Wishlist
Unassigned

Bug Description

Please create teacher friendly instructions on how to set up a cluster of computers, without internet access, to use Sugar on a Stick and collaborate locally with each other.

Revision history for this message
Caroline (cmeeks) wrote :

I tried this with the 5 port version of this:
http://www.netgear.com/Products/Switches/DesktopSwitches/FS605.aspx

It did not work, the computers did not see each other.

Revision history for this message
bogstad (bogstad) wrote :

After further testing, the problem is that ipv4 link-local address allocation doesn't work
with the Strawberry SoaS.

A workaround for now is to use a cheap cable modem router instead of a simple switch. Cheap consumer routers bundle a DHCP server with the switch/router which works fine.

Revision history for this message
bogstad (bogstad) wrote :

I've done some more investigation and it looks like the avahi-daemon is being
started to register address allocations, but no attempt to run avahi-autoipd every
happens. I think what is going on is that NetworkManager tries to use dhclient to
get an IP address. When this fails, it gives up. It should instead try to run avahi-autoipd
to configure the interface.

I base this on looking at /var/log/messages and manually running the /etc/init.d scripts for avahi and networking manager. If I manually run avahi-autoipd it happily configures the appropriate interface.

I tried a Fedora 11 Live ISO in the same environment and it also fails with the same types of log messages. It appears that Fedora 11 doesn't automatically assign
link-local addresses in the default configuration. I guess this makes this a Fedora 11
bug (or at least lack of feature). If I get the chance I'll try to test the Fedora 12 Alpha ISO to see the problem is still there.

Revision history for this message
bogstad (bogstad) wrote :

I finally got around to trying out the Fedora 12 Alpha ISO, it also seems to not automatically start avahi-autoipd.
For the near future, unless SoaS wants to make some changes to it's Fedora base, it would appear that we will
have to recommend that a DHCP server always be available on the network. Most cheap wireless routers
already do this. Most ethernet switches do not and as a result should not be recommended for for use with SoaS
in wired configurations. It is possible to daisy chain a single wireless router to multiple ethernet switches
if more then (the typically 4) machines need to be connected via wires.

Revision history for this message
Sebastian Dziallas (sdziallas) wrote :

Is there an easy way to start avahi-autoipd automatically and would this make sense? If yes, we might want to do so, I guess.

Changed in soas:
importance: Undecided → Wishlist
Luke Faraone (lfaraone)
Changed in soas:
status: New → Triaged
Revision history for this message
Sebastian Dziallas (sdziallas) wrote :

Ping?

Revision history for this message
Caroline (cmeeks) wrote :

I think we now understand how to do this. We still need someone to write it up in a way that is easy to do for people doing demos at conferences or setting up computer stations in a classroom.

Anurag should be able to help with this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.