[luau] Hawaii Wi-Fi

[whenever]

	There could be a problem when 2 APs are close to each other when you have  
over laps on the covering area, and most likely they are using the same 
channel, how will your client machine handle this? I think their idea of 
using 24 bits of the mac address to calculate IP is better, this way none of 
the client will have conflict because dhcpd assigning the ip, then change the 
ipfilters to allow traffics, static ip could be a bad idea on this part. I 
have been thinking about doing this a while back, if we have enought people 
working on this project, we could bridge all the AP that's close to each 
other, that way we could eliminate some problems.  Your idea of using only 
one dhcpd to manage all the client sound good.
	I will get an external anntenna and an 1Watt bi-directional AMP if more 
people willing to do this.  Have anybody done any war driving on this island? 
 I had kismet(http://www.kismetwireless.net/index.shtml) setup on my laptop 
but don't have time to do it yet, so all I see is my own AP now. Oh, I am 
still having problems try to get my Garmin GPS to work in Linux.

On Saturday 30 March 2002 12:42 pm, Dustin Cross wrote:
> This sounds kinda cool.  I could be interested.  I was reading their
> NoCatAuth White Paper (http://nocat.net/nocatrfc.txt) and thinking about
> the problem they discuss at the bottom for roaming.  Each site is a gateway
> and when you leave teh range of a site and enter another site's range you
> need a new IP and gateway, etc.  They propose a way to deal with this.
>
> I was thinking of another way to deal with this and wanted some input.
> Just an idea:
>
> Assign each gateway the same IP and network (say 10.0.0.1/8) and have the
> client keep thier IP as they move from gateway to gateway.  I think you
> would have to assign IP statically, because you would need the same DHCP
> table on each gateway to keep track of which IPs are avail and which are
> taken.  So my client's IP is 10.0.0.2/8 when I am in range of "gateway A"
> and stays the same when I move into range of "gateway B".  Both gateways
> are 10.0.0.1/8.  There will be some point at which both gateways are in
> range and might respond, but that shouldn't be a problem?
>
> Need to test this.  Plug two systems into a hub ("gateway A" and "client
> A").  Have "gateway A" acting as the router to the world.  Then
> connect "gateway B" to the hub with the same IP as "gateway A" and see how
> things work.  finially unplug "gateway A" and everything should keep right
> on working.  So what does everyone think?
>
> The real problem is how to dynamically assign IPs to clients?  What if you
> put the DHCP server behind the gateways and did port forwarding from all
> the gateways to the DHCP server?  Then you would just have one DHCP server
> assigning IPs.
>
> anyway just playing around,  what does everyone else think?
>
> Dusty
>
> > A list of Wi-Fi providers is available at
> > http://www.pdqlink.com/WISP/maps.htm
> > Although the map doesn't show Hawaii (or Alaska) the list below it
> > does. I am setting up a NoCat Authentication Server which will be open
> > to anyone that wants to setup a public access gateway. Any volunteers
> > to help me out? NoCat is a cool idea, more information is available at
> > http://nocat.net/
> >
> >
> > _______________________________________________
> > LUAU mailing list
> > LUAU at videl.ics.hawaii.edu
> > http://videl.ics.hawaii.edu/mailman/listinfo/luau
>
> _______________________________________________
> LUAU mailing list
> LUAU at videl.ics.hawaii.edu
> http://videl.ics.hawaii.edu/mailman/listinfo/luau