discuss AT lists.opennicproject.org
Subject: Discuss mailing list
List archive
- From: Alejandro Bonet <albogoal AT gmail.com>
- To: discuss AT lists.opennicproject.org
- Subject: Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations
- Date: Wed, 4 Dec 2013 20:14:45 +0100
It was maked with two TP-LINK TL-WA601G access points, but im sure it
is possible to do it with (almost) any access points.
Nothing to do with kernels: Both wifis can be configured with the ip
mask you choose.
Put the same mask in both, but one with ip adress x.x.x.1 and the
other x.x.x.2 (or whatever you want).
Configure both in BRIDGE MODE, and they will ask you the MAC address
of the other, and the radio channel.
Thats all...
They are conected by cable to two ethernet switches (one at my home,
and the other at my neigbour home)...
Now, the two ethernets segments seems like they are the same...
I can ping or access his computers or routers, and he can do the same
with mines...
http://www.ciudadwireless.com/tp-link_tl-wa601g_108m_wireless_access_point_with_extended_rangetm_super_gtm-_atheros-2-4ghz-_802-11g-b-_ap-ap_client-_repea-p-2648.html?gclid=CPKsm7yhl7sCFRLMtAodwmkAcg
Regards...
PD: These access points also can be configured as repeaters, but we
dont did this yet...
2013/12/3, Quinn Wood <wood.quinn.s AT gmail.com>:
> On Tue, Dec 3, 2013 at 5:23 AM, Alejandro Bonet <albogoal AT gmail.com> wrote:
>> Each wifi only accepts the MAC of the other, and both cable ethernets
>> share the same ip mask.
>>
>> In this way, it is like "join two cable ethernets via wifi" and it can
>> share also broadcast packets, ARP packets, etc...
>>
>> Both ethernets are "virtually the same", but they are linked by wifi...
>>
>> Up to 300 meters, without free vision line or special antennas...
>>
> Is there some documentation on how to do this, and do you need
> anything other than a standard Unix-like kernel+userland and a
> standard wireless interface?
>
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/02/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Coyo, 12/02/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/03/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Quinn Wood, 12/03/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Quinn Wood, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Jon Sparks, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Coyo, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Quinn Wood, 12/05/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Coyo, 12/05/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Jon Sparks, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Quinn Wood, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Coyo, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/04/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Quinn Wood, 12/03/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Alejandro Bonet, 12/03/2013
- Re: [opennic-discuss] Neighborhood Freespace Optic Network DNS Considerations, Coyo, 12/02/2013
Archive powered by MHonArc 2.6.19.