I'm not sure if it's installed on a default XO build (I'll check when I get home)
but running avahi-autoipd -D msh0 Will assign you some automatic link local address love. Cheers, Trent On Sun, Mar 18, 2007 at 09:57:15PM -0500, Rafael Enrique Ortiz Guerrero wrote: > Hi everyone, > > These are the exact steps that work for mesh. (Especial thanks to the > Cozybit people) > Doing thos the laptops should see each other in the neighbourhood view. > > iwconfig msh0 mode ad-hoc essid "any_ssid" > ifconfig msh0 <any_IP_address> > > The mesh ignores the ssid, so there's no need to pick matching SSIDs > for all laptops in the mesh. The IP addresses should belong to the > same subnet. So, for two laptops, this will do the trick: > > -- xo1 -- > iwconfig msh0 mode ad-hoc essid "xo1" > ifconfig msh0 [1]10.0.0.1 > > -- xo2 -- > iwconfig msh0 mode ad-hoc essid "xo2" > ifconfig msh0 [2]10.0.0.2 > ping [3]10.0.0.1 # should work > > On 3/18/07, MBurns <[EMAIL PROTECTED]> wrote: > > On 3/17/07, Mike Usmar <[EMAIL PROTECTED]> wrote: > > On the new build 303 it mentions the P2P and browser is working; We > are > > picking the Access Points up on the BTest-2 and can ping the > Wireless > > routers from the DV console but it seems the auto configure isn't > working on > > the browser, or are we missing some key info here!!!! > > To get laptop-to-laptop mesh working, you currently need to do 2 things. > 1. with iwconfig, put the laptops into adhoc mode with an arbitrary > essid > 2. assign the laptop a unique IP address (in the same subnet as all > other OLPC laptops you wish to mesh with). > > 1. Will eventually be a non-manual operation.* > 2. Either via 169.254/16 (with Avahi) or as part of the standard > config will also be a non-manual fallback. > > This is just an In The Mean Time fix. I have successfully pinged and > networked with 2 B2 machines using the above steps. > > * Will the operating be a "Connect to network if you can see one, > otherwise create an ad-hoc network and sit patiently", or is there > some more intelligence to joining networks still in the works? > > > We also can't see > > other XO's in the neighbourhood view > > > > > > > > Mike Usmar > > > > OLPC NZ/Pacific Development Group > > > > Phone 64 9 271-1907 > > > > Mobile 64 21-111-5376 > > > > SKYPE : mikeusmar > > > > > > > > > > > > > > _______________________________________________ > > Devel mailing list > > [EMAIL PROTECTED] > > [7]http://mailman.laptop.org/mailman/listinfo/devel > > > > > > -- > Michael Burns * Security Student > NET * Oregon State University > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > [9]http://mailman.laptop.org/mailman/listinfo/devel > > -- > Rafael Enrique Ortiz Guerrero > OLPC Colombia > [10]http://wiki.laptop.org/go/OLPC_Colombia > Grupo de robotica libre DROZ > [11]http://www.el-directorio.org/DrozConfluence > [12]http://el-directorio.org > El sitio de software Libre en Colombia > > References > > Visible links > 1. http://10.0.0.1/ > 2. http://10.0.0.2/ > 3. http://10.0.0.1/ > 4. mailto:[EMAIL PROTECTED] > 5. mailto:[EMAIL PROTECTED] > 6. mailto:[email protected] > 7. http://mailman.laptop.org/mailman/listinfo/devel > 8. mailto:[email protected] > 9. http://mailman.laptop.org/mailman/listinfo/devel > 10. http://wiki.laptop.org/go/OLPC_Colombia > 11. http://www.el-directorio.org/DrozConfluence > 12. http://el-directorio.org/ > _______________________________________________ > Devel mailing list > [email protected] > http://mailman.laptop.org/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/devel
