[WLANware] Community Wireless Networks

Naman Muley naman.g.muley at gmail.com
Mon Apr 2 06:33:52 CEST 2012


Hi!

On Mon, Apr 2, 2012 at 3:26 AM, Mitar <mmitar at gmail.com> wrote:

> Hi!
>
> On Sat, Mar 31, 2012 at 11:15 AM, Naman Muley <naman.g.muley at gmail.com>
> wrote:
> > 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.
>
> You can always port it to Windows. :-)
>
:-) I agree. The more I get deeper into this project, the more
possibilities I see for work! Sadly, I have only 1 month left at this
institute. I will try this in the summer vacations. I want to get this
network up and running, at the most basic state, before I leave.

>
> Or use less dynamic allocation scheme. So that each user/maintainer of
> the node registers first at some central web interface and then
> configures the node accordingly. We are using such scheme in our
> network. For that we are using our own software called nodewatcher:
>
> https://nodes.wlan-si.net/
>
> whoaaa! you have exhaustive monitoring going on! nodewatcher, Is it
opensource? I've been looking at nmap and a few others for the network
monitoring.

yeah, probably such an IP scheme will work. I'll try looking at that. We
wrote scripts for the 10.x.x.x ip allocation for windows and linux over the
weekend. But I think your method is still better. I'll have a look.

> 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?
>
> Synchronization? No. Just for each node you register it so that IP is
> not reused.
>
> Hmm... yeah, offline allocation tables could be used. I thought this
registry was to be dynamically managed between the nodes.


> > MAC addresses are unique. i doubt there will be IP conflicts?
>
> MAC addresses are in theory unique, sadly it is not always so. But
> this is not what I had in mind here anyway. The problem is that you
> are not using whole MAC addresses but just part of it. And parts of
> MAC addresses are not unique. In IPv6 such autoconfiguration works
> because you can use the whole MAC address, but in IPV4 it does not. Or
> it does, if you are lucky, but then sometimes it does not. And you
> will have unpredictability in stability of your network.
>
> True! I was relying on probabilities to rescue me.
I cannot thank you enough! Thank you for the insights. I'll be in touch
time and again. Hope it won't bug you. btw, exactly how much time did it
take you people to set up your freifunk community?


>
> Mitar
> _______________________________________________
> 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
>

- Naman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.freifunk.net/pipermail/wlanware-freifunk.net/attachments/20120402/8a999e07/attachment.html>


More information about the WLANware mailing list