[WLANware] WLANware Digest, Vol 65, Issue 11
Lolitha Ratnayake
lolitha88 at gmail.com
Thu Mar 29 12:56:38 CEST 2012
Hey everyone,
I just saw this email. It reminded me same like problem I had few months
back. I wanted to implement chat program like this. So what I did was hard
code a common ip address. Then broadcast some special UDP packets. So two
senarios
1) There is existing network
other nodes might welcome me by sending their ip tables so I can
pick a new one.
2) There is no existing network
no other nodes detect me so my guess is no network existing. So I
initiate a new unique IP address that is not the one I used to broadcast.
I just did for fun didn't implement it on large scale. What you think of
it?
On Thu, Mar 29, 2012 at 2:53 PM, <wlanware-request at freifunk.net> wrote:
> Send WLANware mailing list submissions to
> wlanware at freifunk.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://freifunk.net/mailman/listinfo/wlanware
> or, via email, send a message with subject or body 'help' to
> wlanware-request at freifunk.net
>
> You can reach the person managing the list at
> wlanware-owner at freifunk.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WLANware digest..."
>
> Today's Topics:
>
> 1. Community Wireless Networks (Naman Muley)
> 2. Re: Community Wireless Networks (Steini)
> 3. Re: Community Wireless Networks (L. Aaron Kaplan)
> 4. Re: Community Wireless Networks (Naman Muley)
> 5. Re: Community Wireless Networks (Naman Muley)
>
>
> ---------- Forwarded message ----------
> From: Naman Muley <naman.g.muley at gmail.com>
> To: wlanware at freifunk.net
> Cc:
> Date: Wed, 28 Mar 2012 20:06:26 +0530
> Subject: [WLANware] Community Wireless Networks
> Hi,
>
> I am Naman Muley, a final year undergraduate student at DAIICT, India.
>
> I am attempting to create a community wireless mesh network inside my
> institute campus. I wanted some help from freifunk community. I would be
> very grateful if some one could answer my following queries and also how
> does the freifunk mesh network exist?
>
> I am using OLSR as the routing protocol. 7
>
> 1. *IP Address allocation: *Say I started an adhoc network. Others joined
> and they received IP by DHCP from me. Now, if I turn off, how will the new
> comers get IP addresses?
> > During the time I was still in the network, no other node could have
> acted as the DHCP server as that would have created IP conflict.
> > Only option I see is, someone takes up the DHCP leadership after me.
> Say, the network chooses a leader.
>
> > My question is, I read quite a few papers but they don't seem to
> have implementations in linux drivers or any other operating systems for
> that matter
>
> 2. *DHCP and Windows: *One of my friends was running windows and he does
> not seem to be able to obtain IP address. The network is visible to him but
> the prompt only shows "identifying..". On further plumbing we saw that it
> was an IP address problem.
>
> How did you guys manage this? How does the freifunk network work under one
> network? and how are the IP addresses allocated?
> I might be missing a fundamental thing here. Please pardon my noobness ;)
>
> Thank you so much for your patience.
>
> Yours Networkingly,
> Naman
>
>
> ---------- Forwarded message ----------
> From: Steini <freifunk at total-connection.net>
> To: wlanware at freifunk.net
> Cc:
> Date: Wed, 28 Mar 2012 20:29:33 +0200
> Subject: Re: [WLANware] Community Wireless Networks
> Hi Naman,
>
> i'm still a novice in freifunk, but i'll try to answer as accurate as
> possible.
>
> Am 28.03.2012 16:36, schrieb Naman Muley:
>
> Hi,
>
> I am Naman Muley, a final year undergraduate student at DAIICT, India.
>
> I am attempting to create a community wireless mesh network inside my
> institute campus. I wanted some help from freifunk community. I would be
> very grateful if some one could answer my following queries and also how
> does the freifunk mesh network exist?
>
> great thing, go on and don't give up!
>
> I am using OLSR as the routing protocol. 7
>
> 1. *IP Address allocation: *
>
> At my freifunk community we list up all our freifunk nodes, in one ip
> range, let's say 10.27.*.*
> So everybody who set's up a node, adds the nodes' adress to the list and
> olsrd is doing all the routing stuff, if configured properly. Every node is
> running a dhcp server itself for its connected clients. With NAT on every
> node you won't run into trouble with double assigend ip adresses.
>
> 2. *DHCP and Windows: *
>
> uhh there can be so many problems. do you see some dhcp traffic with
> wireshark or etherreal on both ends (client and freifunk node)? Is the
> wireless connection established? Maybe it's a good idea to try it out with
> a properly configured accesspoint you alredy own or to work around all
> adhoc problems (some chipsets fail with this) do some setup for an node
> running in infrastructure mode.
>
>
> Thank you so much for your patience.
>
> Yours Networkingly,
> Naman
>
> kind regards
>
> Steini
>
>
>
> ---------- Forwarded message ----------
> From: L. Aaron Kaplan <aaron at lo-res.org>
> To: WLANware <wlanware at freifunk.net>
> Cc:
> Date: Thu, 29 Mar 2012 01:06:21 +0200
> Subject: Re: [WLANware] Community Wireless Networks
> Hi Naman,
>
>
> On Mar 28, 2012, at 5:36 PM, Naman Muley wrote:
>
> > Hi,
> >
> > I am Naman Muley, a final year undergraduate student at DAIICT, India.
> >
> > I am attempting to create a community wireless mesh network inside my
> institute campus. I wanted some help from freifunk community. I would be
> very grateful if some one could answer my following queries and also how
> does the freifunk mesh network exist?
> >
> > I am using OLSR as the routing protocol. 7
> >
> > 1. IP Address allocation: Say I started an adhoc network. Others joined
> and they received IP by DHCP from me. Now, if I turn off, how will the new
> comers get IP addresses?
>
> Usually our communities use either some IP autoconfig mechanism (such as
> AHCPd or IPv6 autoconfig) or we use a node database.
> This NodeDB most of all is a kind of "registry" which records which node
> has which IP address (similar to the RIPE DB).
> We are currently working on a new NodeDB implementation which aims at
> kickstarting new communities. Think of it as a "setup.exe" for new
> community networks.
> I got the feeling that this is what you are looking for.
>
> >> During the time I was still in the network, no other node could have
> acted as the DHCP server as that would have created IP conflict.
> >> Only option I see is, someone takes up the DHCP leadership after me.
> Say, the network chooses a leader.
> >
> See above... in my opinion that is not needed.
>
> >> My question is, I read quite a few papers but they don't seem to have
> implementations in linux drivers or any other operating systems for that
> matter
> >
> > 2. DHCP and Windows: One of my friends was running windows and he does
> not seem to be able to obtain IP address. The network is visible to him but
> the prompt only shows "identifying..". On further plumbing we saw that it
> was an IP address problem.
> >
>
> In my opinion we would need more info on the wi-fi setup to understand and
> debug this second issue.
>
> > How did you guys manage this? How does the freifunk network work under
> one network? and how are the IP addresses allocated?
> > I might be missing a fundamental thing here. Please pardon my noobness ;)
>
> See above.
>
>
> Aaron
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Naman Muley <naman.g.muley at gmail.com>
> To: freifunk at total-connection.net, WLANware <wlanware at freifunk.net>
> Cc:
> Date: Thu, 29 Mar 2012 14:44:24 +0530
> Subject: Re: [WLANware] Community Wireless Networks
> Hi Steini,
>
> Thanks for taking out time to reply! Appreciate it!
>
> On Wed, Mar 28, 2012 at 11:59 PM, Steini <freifunk at total-connection.net>wrote:
>
>> Hi Naman,
>>
>> i'm still a novice in freifunk, but i'll try to answer as accurate as
>> possible.
>>
>> Am 28.03.2012 16:36, schrieb Naman Muley:
>>
>> Hi,
>>
>> I am Naman Muley, a final year undergraduate student at DAIICT, India.
>>
>> I am attempting to create a community wireless mesh network inside my
>> institute campus. I wanted some help from freifunk community. I would be
>> very grateful if some one could answer my following queries and also how
>> does the freifunk mesh network exist?
>>
>> great thing, go on and don't give up!
>>
>> I am using OLSR as the routing protocol. 7
>>
>> 1. *IP Address allocation: *
>>
>> At my freifunk community we list up all our freifunk nodes, in one ip
>> range, let's say 10.27.*.*
>> So everybody who set's up a node, adds the nodes' adress to the list and
>> olsrd is doing all the routing stuff, if configured properly. Every node is
>> running a dhcp server itself for its connected clients. With NAT on every
>> node you won't run into trouble with double assigend ip adresses.
>>
>
> Ahh! Okay. There is one crucial thing I forgot to tell you. We are
> students trying to set this whole thing up. So due to lack of funds, we
> have not been able to buy routers OR wireless extenders. So, currently
> DAiict Mesh Network (DAMN) is a purely adhoc network. Once, we have enough
> proof of concept that this is a good idea, we shall be able to demand funds
> from the Institute. i'm thinking of buying a mix of Wireless Extenders and
> Routers.
>
> Hmm.. You have a hierarchy in place. Communities, individual NATs. We
> have aroung 1500 people on the campus in a 50 acre land. You think one
> network is a good idea? Will it be stable? OR I could create pockets of
> networks just like you have with NATs.
>
> 2. *DHCP and Windows:*
>>
>> uhh there can be so many problems. do you see some dhcp traffic with
>> wireshark or etherreal on both ends (client and freifunk node)? Is the
>> wireless connection established? Maybe it's a good idea to try it out with
>> a properly configured accesspoint you alredy own or to work around all
>> adhoc problems (some chipsets fail with this) do some setup for an node
>> running in infrastructure mode.
>>
>
> yeah, we're yet to debug this thing properly. We're looking at IP
> allocation schemes currently.
>
> Thank you so much for showing interest!
>
>>
>> Thank you so much for your patience.
>>
>> Yours Networkingly,
>> Naman
>>
>> kind regards
>>
>> Steini
>>
> Yours gratefully,
> Naman
>
>>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> ---------- Forwarded message ----------
> From: Naman Muley <naman.g.muley at gmail.com>
> To: WLANware <wlanware at freifunk.net>
> Cc:
> Date: Thu, 29 Mar 2012 14:53:12 +0530
> Subject: Re: [WLANware] Community Wireless Networks
> Hi Aaron,
>
> Thank you so much for a prompt reply! Appreciate it!
>
> On Thu, Mar 29, 2012 at 4:36 AM, L. Aaron Kaplan <aaron at lo-res.org> wrote:
>
>> Hi Naman,
>>
>>
>> On Mar 28, 2012, at 5:36 PM, Naman Muley wrote:
>>
>> > Hi,
>> >
>> > I am Naman Muley, a final year undergraduate student at DAIICT, India.
>> >
>> > I am attempting to create a community wireless mesh network inside my
>> institute campus. I wanted some help from freifunk community. I would be
>> very grateful if some one could answer my following queries and also how
>> does the freifunk mesh network exist?
>> >
>> > I am using OLSR as the routing protocol. 7
>> >
>> > 1. IP Address allocation: Say I started an adhoc network. Others joined
>> and they received IP by DHCP from me. Now, if I turn off, how will the new
>> comers get IP addresses?
>>
>> Usually our communities use either some IP autoconfig mechanism (such as
>> AHCPd or IPv6 autoconfig) or we use a node database.
>> This NodeDB most of all is a kind of "registry" which records which node
>> has which IP address (similar to the RIPE DB).
>> We are currently working on a new NodeDB implementation which aims at
>> kickstarting new communities. Think of it as a "setup.exe" for new
>> community networks.
>> I got the feeling that this is what you are looking for.
>>
>> Ahh! Okay. There is one crucial thing I forgot to tell you. We are
> students trying to set this whole thing up. So due to lack of funds, we
> have not been able to buy routers OR wireless extenders. So, currently
> DAiict Mesh Network (DAMN) is a purely adhoc network. Once, we have enough
> proof of concept that this is a good idea, we shall be able to demand funds
> from the Institute. i'm thinking of buying a mix of Wireless Extenders and
> Routers.
>
> Hmm.. You have a hierarchy in place. Communities, individual NATs. We
> have aroung 1500 people on the campus in a 50 acre land. You think one
> network is a good idea? Will it be stable? OR I could create pockets of
> networks just like you have with NATs.
>
> I was looking for the IP allocation scheme. Thank you! The problem with
> AHCPd is, it is not implemented for windows. And Gabriel here<http://www.mail-archive.com/babel-users@lists.alioth.debian.org/msg00455.html>says that people with Windows are doomed. Now, because we currently don't
> own routers, I have to come up with an IP allocation scheme. MIT's
> Roofnet Project <http://pdos.csail.mit.edu/roofnet/design/> 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 registry scheme that you pointed out, could I have some kind of link
> where I can study the scheme?
>
> >> During the time I was still in the network, no other node could have
>> acted as the DHCP server as that would have created IP conflict.
>> >> Only option I see is, someone takes up the DHCP leadership after me.
>> Say, the network chooses a leader.
>> >
>> See above... in my opinion that is not needed.
>>
>> >> My question is, I read quite a few papers but they don't seem to have
>> implementations in linux drivers or any other operating systems for that
>> matter
>> >
>> > 2. DHCP and Windows: One of my friends was running windows and he does
>> not seem to be able to obtain IP address. The network is visible to him but
>> the prompt only shows "identifying..". On further plumbing we saw that it
>> was an IP address problem.
>> >
>>
>> In my opinion we would need more info on the wi-fi setup to understand
>> and debug this second issue.
>>
>> I agree. I think we can tackle this problem. The main problem is IP
> allocation.
>
>
>> > How did you guys manage this? How does the freifunk network work under
>> one network? and how are the IP addresses allocated?
>> > I might be missing a fundamental thing here. Please pardon my noobness
>> ;)
>>
>> See above.
>>
>>
>> Thanks again Aaron for your time!
>
>> Aaron
>>
>> Yours gratefully,
> Naman
>
>>
>> _______________________________________________
>> 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
>>
>
>
> _______________________________________________
> WLANware mailing list
> WLANware at freifunk.net
> https://freifunk.net/mailman/listinfo/wlanware
>
>
--
*Lolitha Ratnayake
Department of Statistics and Computer Science
Faculty of Science
University of Kelaniya
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.freifunk.net/pipermail/wlanware-freifunk.net/attachments/20120329/2e893089/attachment.html>
More information about the WLANware
mailing list