#6624 BLOC Never A: ejabberd requires internet connection for collaboration to work

[Zarro Boogs per Child]

#6624: ejabberd requires internet connection for collaboration to work
------------------------------------+---------------------------------------
 Reporter:  wad                     |       Owner:  Collabora     
     Type:  defect                  |      Status:  new           
 Priority:  blocker                 |   Milestone:  Never Assigned
Component:  presence-service        |     Version:                
 Keywords:  schoolserver, ejabberd  |    Verified:  0             
 Blocking:                          |   Blockedby:                
------------------------------------+---------------------------------------
 In a number of the planned deployments, we intend on placing a school
 server in the school to minimize multicast traffic over the mesh.  Some
 large number of these deployments will not have internet connectivity in
 the beginning.   ejabberd must work in these situations.

 Right now, if the host running ejabberd cannot be found from the root DNS
 servers, collaboration does not work.   The school server does provide a
 local DNS service, which correctly resolves the hostname/domain name of
 the ejabberd node (schoolserver.random.xs.laptop.org by default).
 /etc/resolv.conf is configured to point to this local server.

 I followed the instructions at:

  http://comments.gmane.org/gmane.network.jabber.ejabberd/1305

 and manually checked erlang's nameserver configuration using
 ets:tab2list(inet_db).  It was pointing to localhost.
 I also tried adding relevant host and domain information to
 /etc/hosts.conf and changed /etc/ejabberd/ejabberd.inetrc to load it in,
 to no avail.

 When I say that collaboration is failing, I mean that the laptops connect
 to the jabber server fine, but no other users are visible in the
 neighborhood view.

 daf doublechecked my shared roster configurations.   I have successfully
 configured a half-dozen servers using the same set of instructions.  The
 failure is definitely triggered by inability to access the ejabberd server
 when traversing down from the root DNS servers.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6624>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system