#9544 NORM 1.5-F11: ad-hoc connection assigns duplicate IP address

[Zarro Boogs per Child]

#9544: ad-hoc connection assigns duplicate IP address
-------------------------------------+--------------------------------------
           Reporter:  mikus          |       Owner:  marco                            
               Type:  defect         |      Status:  reopened                         
           Priority:  normal         |   Milestone:  1.5-F11                          
          Component:  sugar          |     Version:  Development build as of this date
         Resolution:                 |    Keywords:  ad-hoc, F11, OS8, B4             
        Next_action:  test in build  |    Verified:  0                                
Deployment_affected:                 |   Blockedby:                                   
           Blocking:                 |  
-------------------------------------+--------------------------------------
Changes (by mikus):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 I don't have two XO-1.5s.  On an XO-1 (Gaiss, with OS9 plus
 sugar-0.84.5-1.fc11.3.i586) I clicked from Frame on 'Create new wireless
 network'.  That set up a new ad-hoc network, and assigned IP address
 10.42.43.1 to Gaiss.  I then went over to my XO-1.5 (Murga, with OS39 with
 sugar 0.84.5-1.fc11.3.i586) and clicked in Neighborhood View on the icon
 for "Gaiss's network".  That supposedly joined Murga to Gaiss's network --
 but Murga was assigned an IP address of 169.254.4.126.

 I __don't__ want Gaiss and Murga to be on two different IP-address ranges.
 They can't ping each other -- that means there is no wireless network
 connection between those machines [despite the parentheses they show in
 Neighborhood View (and Frame)].

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