[CUWiN-Dev] Re: Mesh nodes

[simon at uc.org]

Is there an IRC channel where the developers hang out? I'm very close to
having things running correctly.

I have two nodes up and running, one (A) on a network connected to the
internet, the other standalone (Z).  Everything on (Z) can reach all
(A)'s network and the internet, but not vice-versa.

If I log into (A), I can reach everything on both sides.

If I'm on a system connected to network (A), I add a static route
pointing to (A)'s local IP address, but I still cannot reach anything on
(Z)'s network. When I try to ping anything on Z's network, I get A's IP
address answering back.

i.e.:

A = 192.168.42.22, on 192.168.42.0/24, internet/dhcp from linksys rtr
Z = 10.216.103.254, on 10.216.103.0/24, dhcp from cuw node

mylaptop$ sudo route add -net 10.216.103.0/24 gw 192.168.42.22
mylaptop$
mylaptop$ ping 10.216.103.252
PING 10.216.103.252 (10.216.103.252) 56(84) bytes of data.
64 bytes from 192.168.42.22: icmp_seq=1 ttl=62 time=7.12 ms
64 bytes from 192.168.42.22: icmp_seq=2 ttl=62 time=4.37 ms

Any thoughts?

Cheers,
Simon P. Ditner

On Fri, 13 Jan 2006, Sascha Meinrath wrote:

> Hi Simon,
>
> Simon P. Ditner wrote:
> > Hi Sascha,
> >
> > How does each node handle the clients that are attached to it? Is it
> > similar to something like a residential linksys router doing NAT and
> > DHCP with a single "public" ip address?
> >
> > Cheers,
> > Simon P. Ditner
>
> CUWiN nodes provide DHCP leases to devices connected to them.  I've cc-ed the
> CUWiN development team as participants on the -dev list will be able to answer
> any technical questions you may have.  I know that one of the issues we've been
> facing is how to create fully addressable IP space -- we have several ideas on
> how to do this in a truly ad-hoc manner, but let me know what questions you have
> and folks will be able to provide specific answers.
>
> --Sascha
>
> > On 1/13/06, Andrew Greig <agreig at bell.blackberry.net> wrote:
> >
> >>I think simon figured it out that the mesh nodes run apon a network for their own and that was the reason they were not working.
> >>
> >>Could you Please work with sascha and Jeff and simon D to get the mesh nodes up and running with a thin client on it while I'm gone when you have time.
> >>
> >>Cheers.
> >>
> >>Andrew Greig
> >>905 751 4202
> >>
> >
> >
> >
> > --
> > | First they ignore you, then they laugh at you, then they fight you,
> > | then you win.   -- Mohandas Gandhi
> > |
> > | The Toronto Asterisk Users Group
> > | Join the discussion group by visiting http://taug.ca
> > | or by sending email to asterisk-subscribe at uc.org
> >
> >
>
>
> --
> Sascha Meinrath
> Policy Analyst    *  Project Coordinator  *  President
> Free Press       *** CUWiN               *** Acorn Active Media
> www.freepress.net *  www.cuwireless.net   *  www.acornactivemedia.com
>
>