Conundrum - XO connected to AP + Mesh?

[Ian Daniher]

On 11/24/08, pgf at laptop.org <pgf at laptop.org> wrote:
> erik wrote:
>  > On Mon, Nov 24, 2008 at 12:07:03AM -0500, John Watlington wrote:
>  > >
>  > > With release 8.2, the mesh interface is still up and available when
>  > > connected to an AP.
>  > > Address the laptops on a mesh network on the same channel via their
>  > > self-assigned
>  > > addresses (169.254.x.x) and you can ping and ssh them from an AP
>  > > connected XO
>  > > without problems.
>
> but can the zeroconf'ed machines access what's behind the AP?  i.e.,
> how do they learn of a default gateway?  i assume this is the real
> intent behind the question.
>
>  >
>  > I for one would very much like to understand the dependencies of this
>  > setup...
>  >
>  > For instance, where are the self-assigned IP addresses coming from?  How
>
> RFC 3297
>
> paul
>
>  > do you get a list of XOs -> IPs in the mesh neighborhood from the
>  > command line?  (There was a script floating around the ml to do the
>  > latter but I can't find it now.)
>  >
>  > Erik
>
> =---------------------
>  paul fox, pgf at laptop.org
>  give one laptop, get one laptop --- http://www.amazon.com/xo
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
Hi all,
Do you think this is possible to do without network manager and the
standard sugar interface? I'm running debxo. I got standard mesh
(without NM) working fine, but so far I haven't had any luck
associating to an AP and to a MeshNW simultaneously.
Thanks!
-- 
Ian Daniher
--
OLPC Support Volunteer
OLPCinci Repair Center Coordinator
--
it.daniher at gmail.com
Skype : it.daniher
irc.freenode.net: Ian_Daniher