Goal: Wireless IPs
I have a goal to be a wireless IP provider, and I already started to buy equipment to acheieve this goal. When I researched how to obtain IP numbers to use, I found out I had to buy a bank of 1024 of them and prove that they are being used. I thought how could I accomplish such goals. One idea was to use the data from wigle.net to find those who already have wireless equipment that would like to connect directly instead of buy dial-up.
This thread is just to gather ideas on how to promote wireless to wireless connections in the communities and to figure out what is needed to support it.
This thread is just to gather ideas on how to promote wireless to wireless connections in the communities and to figure out what is needed to support it.
I have started to make a wireless map of the area. If I showed the community how dense the wireless networks are, they may see the light and want to connect to each other.
Could this be used to geographically group wireless APs with the advantage to allow roaming within neighborhoods?
It could be done with a set of IPs set aside as mobile IPs. Each AP would have to support a feature to host mobile IP and allow them to roam.
With geographic IP data, we could allow any AP to query its MAC number [on wigle.net, perhaps] and determine an appropriate subnet which would easily allow neighbors to roam. An appropriate subnet would mean a subnet that the neighbors share. The query database would render neighbors within a geoprahic area the same subnet. That would work until smarter APs come about.
With geographic IP data, we could allow any AP to query its MAC number [on wigle.net, perhaps] and determine an appropriate subnet which would easily allow neighbors to roam. An appropriate subnet would mean a subnet that the neighbors share. The query database would render neighbors within a geoprahic area the same subnet. That would work until smarter APs come about.
That seems like the server would have to be massive to support all the queries against the MAC addresses.
What about a NAT that would distribute its allocation database to other NATs? There is some software that already does that: google distributed NAT.
Such queries could be routed to the nearest NAT server instead of a server like wigle.net or nodedb.com.
What about a NAT that would distribute its allocation database to other NATs? There is some software that already does that: google distributed NAT.
Such queries could be routed to the nearest NAT server instead of a server like wigle.net or nodedb.com.
Whoa, neo... prior art... wagle the dog
I helped out a project that could distribute the databases. I see some open source projects that lets internet connection be shared. I have put together some software that works as a virtual machine. If needed, we could run linux on windows to keep a common base. Just got to put it all together!
I helped out a project that could distribute the databases. I see some open source projects that lets internet connection be shared. I have put together some software that works as a virtual machine. If needed, we could run linux on windows to keep a common base. Just got to put it all together!
as entertaining as this monologue is (mmmm, view ip of poster button)...
wigle is NOT a list of points you can use for internet access.
wigle is NOT a list of points you can use for internet access.
MMmmm... that IP button gives the address of a NAT system.
Points for Internet Access... no. More like, wigle could be used to help on the allocation.
uhtu, ever thought about a system that could act as a distributed wigle? If wigle gets used often enough (lets say in the future), the process time may increase.
Points for Internet Access... no. More like, wigle could be used to help on the allocation.
uhtu, ever thought about a system that could act as a distributed wigle? If wigle gets used often enough (lets say in the future), the process time may increase.
Return to “WiGLE Project Suggestions”
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 5 guests