#5818 BLOC Update.: Something in Update1-670 Breaks Unix Sockets over Stream Tubes

Zarro Boogs per Child bugtracker at laptop.org
Sun Jan 6 05:33:53 EST 2008


#5818: Something in Update1-670 Breaks Unix Sockets over Stream Tubes
-----------------------+----------------------------------------------------
  Reporter:  bemasc    |       Owner:  mbletsas
      Type:  defect    |      Status:  new     
  Priority:  blocker   |   Milestone:  Update.1
 Component:  wireless  |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |    Blocking:          
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by sjoerd):

 Replying to [comment:24 mbletsas]:
 > Rainbow tries to control access to the network device, correct?
 > I can't see why we have to start from wireless when your description is
 that
 > it works with security disabled.

 Because:
   0. Rainbow does _not_ control network access at all. Or to our best
 knownledge
      influence the setup of the network.
   1. Even if it did, one side doesn't receive replies to its arp requests,
 although
      the replies are being sent out according tcpdump. Which to me
 indicates a
      problem below userspace.
   2. And even if it did in some way prevent arp replies from being either
 sent or
      received either directly (impossible afaik) or indirectly (by causing
 some
      misconfiguration that's not apparent from userspace or triggering
 some race
      condition). The Wireless people should be able to at least do the
 next step
      in debugging..

 So please stop purely blaming Rainbow. It might be a innocent bystander or
 a triggering factor, but we just can't know at this point.. Instead try to
 reproduce this and answer questions like why doesn't one side see the arp
 replies the other side sends out. When we know that, then we can start
 figuring out what is causing this and who is to blame.

 I'm prefectly happy to provide more info when asked for. But i won't do
 any further debugging at this point, because i don't know enough about the
 lowlevel mesh stuff
 to do the next few usefull steps in hunting it down.

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



More information about the Bugs mailing list