[WLANware] Community Wireless Networks

[Naman Muley]

Hi Mitar!

Thanks for the reply!

On Sat, Mar 31, 2012 at 12:39 PM, Mitar <mmitar at gmail.com> wrote:

> Hi!
>
> On Thu, Mar 29, 2012 at 12:23 PM, Naman Muley <naman.g.muley at gmail.com>
> wrote:
> > I was looking for the IP allocation scheme. Thank you! The problem with
> > AHCPd is, it is not implemented for windows.
>
> Why it this s problem? You run AHCPd on nodes, not on client
> computers. You use AHCPd to auto-configure nodes, not to delegate IPs
> to client computers connecting to your mesh network.
>
> I understand that by nodes you mean routers. But we over here are looking
at pure adhoc networks. We have not had funds to buy routers. I guess in
adhoc nodes, we can assume a few clients to be running AHCPd in server
mode. These nodes will be able to give IP configuration information to
other nodes running AHCPd in client mode.

Hence, over here, we have students in the campus as nodes. They may have
machines with different operating systems. Some of them might have windows.
AHCPd, either in client or server mode is not available for windows, hence
these nodes won't be able to get configured.

Please correct me if I am wrong here..

>  > I have to come up with an IP allocation scheme. MIT's Roofnet
> Project had a
> > scheme in which they used the last 3 bytes of the MAC address to complete
> > the IP address as : 10.x.x.x.
>
> The problem with this is that you probably do not want to use whole
> 10/8, especially if you want to peer with some other mesh networks.
>

This is right. The larger A class address will cause issues. I have been
thinking about the structure of the network. Only that again, once we get
routers, I will organize the architecture into network communities.
Remember, I am talking about a community wireless network, starting as a
mesh network inside a campus (and currently, restricted to the campus)
covering an area of 50 acres or so.

Once, we have the campus in a mesh network, I hope people after me will
carry this into a true community wireless network.


> You should allocate as little as possible. And one way is to have an
> IP registry.


Can you please explain how could I do this? I will have to have a central
IP registry with all the nodes and there will have to by synchronization
done between them?


> Or use IPv6. Do not try to do some auto-allocation in
> IPv4 because birthday paradox will bite you and you will have IP
> conflicts.
>
> MAC addresses are unique. i doubt there will be IP conflicts?

>
> Mitar
>

Thank you so much Mitar for taking out time. I appreciate it!

> _______________________________________________
> WLANware mailing list
> WLANware at freifunk.net
> Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware
>
> Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung
> unter http://freifunk.net/mailinglisten
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.freifunk.net/pipermail/wlanware-freifunk.net/attachments/20120331/7c20d407/attachment.html>