Mesh Network feature XO-XS

[Ricardo Carrano]

Hi Solochan,

It seems correct. Repeater is the correct mode for msh0.
For eth0 you will have ad-hoc or managed (if the interface is associated to
an access point).

Think of the school server with an active antenna attached as a gateway
between the mesh and the infrasctructured network. The active antenna is the
interface to the mesh, while the wired ethernet is the interface to the
infrasctruture. I believe this will help understand the modes you see.

On Thu, Feb 21, 2008 at 7:06 AM, sulochan acharya <sulochan at gmail.com>
wrote:

> Hi Ricardo,
> I don't know if this is major problem but when i run
> #iwconifg msh0
> it shows that the msh0 mode=repeater
> I am running firmware version 3107. if i try to iwconfig msh0 ap any or
> any other iwconfig command on msh0 it does not work.
> My eth0 is on ad-hoc mode.
> I tried unplugging the antenna and replugging it but when i do service
> network restart it never comes up.
>
> Is that the right mode for eth0 and msh0. Is there a way to manually
> change the mode on msh0??
>
> However, i can ping the internet through the antenna. Should i be able to
> do that on a repeater mode?
>
> P.S: I did manage to find the iwpriv msh0 fwt_list on the xo's and the
> laptop.
>
> best,
> Sulochan.
>
>
> On Wed, Feb 20, 2008 at 7:42 PM, Ricardo Carrano <
> carrano at ricardocarrano.com> wrote:
>
> > Hi Sulochan!
> >
> > Assuming it is your XO2 fwt_list, it should be populated with paths to
> > XO1 (via XO1) and XS (via XO1 or XS, depending whether the XS is in reach).
> > The way it is (empty) this means your XO has no path for any other XO.
> > It is lonely and sad ;-)
> > But, please keep in mind that these entries expiry (I don't recall how
> > long does it take - but it's not long), so you should check them during the
> > test. Is that the case?
> >
> > On Feb 20, 2008 9:20 AM, sulochan acharya <sulochan at gmail.com> wrote:
> >
> > > Hi Ricardo,
> > > I have iwpriv showing
> > > NULL on all the fwt_list .
> > > What should it be set to?
> > >
> > > best,
> > > Sulochan.
> > >
> > >
> > >
> > > On Feb 19, 2008 5:41 PM, Ricardo Carrano <carrano at ricardocarrano.com>
> > > wrote:
> > >
> > > > Sulochan,
> > > >
> > > > You should check your forwarding (layer two) table with : iwpriv
> > > > msh0 fwt_list <index> (<index> is 0,1,2,...)
> > > >
> > > > Look for an entry that forwards the frames destined to the anycast
> > > > mac address of the server (c0:27:c0:27:c0:00) via the mac address of the
> > > > first XO.
> > > >
> > > > Traceroute/path will show you layer three (IP) routes.
> > > >
> > > > Regards,
> > > > Ricardo Carrano
> > > >
> > > > 2008/2/19 sulochan acharya <sulochan at gmail.com>:
> > > >
> > > > > Folks,
> > > > > I can not hop from xo to xo to xs.
> > > > > Here is what I did:
> > > > >
> > > > > One XO closer to the server with active antenna.....and i can ping
> > > > > the server from this laptop.
> > > > >
> > > > > Another XO closer to the first laptop ( i can chat with this XO)
> > > > > but further away from the server.
> > > > >
> > > > > Now technically i should be able to ping the server through the
> > > > > first laptop, but I cant :(
> > > > >
> > > > > Is there some additional things i need to (like adding packages)
> > > > > go through to get this to work?
> > > > >
> > > > > Or is it just out of range? If so how it is different from one
> > > > > laptop talking to another laptop?
> > > > >
> > > > > Is there a way i can check that the packet is being relayed (other
> > > > > than doing trace rout ) ?
> > > > >
> > > > > Also, can i for test purposes change the mesh DHCP to give out
> > > > > ipv4 and not ipv6? Would this make
> > > > > some other features not work?
> > > > >
> > > > > best,
> > > > > -Sulochan
> > > > >
> > > > > _______________________________________________
> > > > > Devel mailing list
> > > > > Devel at lists.laptop.org
> > > > > http://lists.laptop.org/listinfo/devel
> > > > >
> > > > >
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080221/7ad2d185/attachment.html>