Comments on: The Second Village Telco Workshop http://villagetelco.org/2009/08/the-second-village-telco-workshop/ an easy-to-use, scalable, standards-based, wireless, local, do-it-yourself, telephone company toolkit Tue, 15 May 2012 18:57:59 +0000 hourly 1 http://wordpress.org/?v= By: Steve http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-118 Steve Fri, 22 Jul 2011 11:17:03 +0000 http://villagetelco.org/?p=279#comment-118 It is not a PoS solution on its own but could be used as part of a PoS solution. What kind scenario are you thinking of? It is not a PoS solution on its own but could be used as part of a PoS solution. What kind scenario are you thinking of?

]]> By: marshall anako http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-117 marshall anako Fri, 22 Jul 2011 01:16:07 +0000 http://villagetelco.org/?p=279#comment-117 Please i want to know if the mesh potato caan act as point of sale Please i want to know if the mesh potato caan act as point of sale

]]> By: Beer, Coffee, and a little DSP » Blog Archive » Baboons, Mesh networks, and Community http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-116 Beer, Coffee, and a little DSP » Blog Archive » Baboons, Mesh networks, and Community Tue, 05 Jan 2010 00:39:10 +0000 http://villagetelco.org/?p=279#comment-116 [...] both Village Telco Workshop I had the pleasure of meeting David Carman and Antoine van Gelder, who founded and now administer [...] [...] both Village Telco Workshop I had the pleasure of meeting David Carman and Antoine van Gelder, who founded and now administer [...]

]]> By: Stress Testing the Potato « Village Telco http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-115 Stress Testing the Potato « Village Telco Sat, 05 Dec 2009 15:49:23 +0000 http://villagetelco.org/?p=279#comment-115 [...] or AC to the DC jack, to any pin of the Ethernet port or FXS port. For a couple of weeks before the Capetown workshop I had only one Mesh Potato to perform software development, radio performance and hardware tests. I [...] [...] or AC to the DC jack, to any pin of the Ethernet port or FXS port. For a couple of weeks before the Capetown workshop I had only one Mesh Potato to perform software development, radio performance and hardware tests. I [...]

]]> By: RF Hacking « Village Telco http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-114 RF Hacking « Village Telco Tue, 17 Nov 2009 07:47:31 +0000 http://villagetelco.org/?p=279#comment-114 [...] Hacking Since the 2nd Village Telco Workshop in July we have been working on the Beta release of the Mesh Potatoes. Progress slowed immediately [...] [...] Hacking Since the 2nd Village Telco Workshop in July we have been working on the Beta release of the Mesh Potatoes. Progress slowed immediately [...]

]]> By: Beer, Coffee, and a little DSP » Blog Archive » Second Village Telco Workshop http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-113 Beer, Coffee, and a little DSP » Blog Archive » Second Village Telco Workshop Sun, 09 Aug 2009 23:50:33 +0000 http://villagetelco.org/?p=279#comment-113 [...] July I attended the 2nd VT workshop - there are a couple of blog posts reporting the event from Steve Song and [...] [...] July I attended the 2nd VT workshop – there are a couple of blog posts reporting the event from Steve Song and [...]

]]> By: drowe http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-112 drowe Fri, 07 Aug 2009 01:18:55 +0000 http://villagetelco.org/?p=279#comment-112 Alex - the production target price is under $100. Volume and re-engineering will push it lower and lower over time. Alex – the production target price is under $100. Volume and re-engineering will push it lower and lower over time.

]]> By: Alexander Chemeris http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-111 Alexander Chemeris Thu, 06 Aug 2009 21:38:07 +0000 http://villagetelco.org/?p=279#comment-111 Yet another question. What is an expected cost for the end user? For the gear like this I personally would pay no more then $100-$150. But I see that you allow $50 increase just for safety. Yet another question.
What is an expected cost for the end user? For the gear like this I personally would pay no more then $100-$150. But I see that you allow $50 increase just for safety.

]]> By: Alexander Chemeris http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-110 Alexander Chemeris Thu, 06 Aug 2009 21:34:27 +0000 http://villagetelco.org/?p=279#comment-110 Good answer, thank you. It's clear for me now. Good answer, thank you. It’s clear for me now.

]]> By: elektra http://villagetelco.org/2009/08/the-second-village-telco-workshop/#comment-109 elektra Thu, 06 Aug 2009 19:49:45 +0000 http://villagetelco.org/?p=279#comment-109 If both mesh networks use overlapping IP addresses/range and overlapping channels, overlapping wireless network names (ESSID) and overlapping Cell-IDs (IBSSIDs) then there can be collisions on IP layer. However if both networks use the same parameters but coordinate the IPs in order to maintain using unique IPs for each device then the coverage, size and range of the mesh network increases. Then there will be only one mesh network that just grows. I like the idea of a large common mesh network - the mesh becomes a common communication infrastructure that can be used by everyone - NGOs, individuals, communities, entrepreneurs . On the other hand technically there is no problem separating two or many meshes operating in the same area (using different channels and ESSIDs and IBSSIDs). Things get slightly more complicated if you want to set up gateways that are routing from one mesh into the other and vice versa. Then you clearly want to separate the meshes by using non-overlapping sub-networks. If both mesh networks use overlapping IP addresses/range and overlapping channels, overlapping wireless network names (ESSID) and overlapping Cell-IDs (IBSSIDs) then there can be collisions on IP layer. However if both networks use the same parameters but coordinate the IPs in order to maintain using unique IPs for each device then the coverage, size and range of the mesh network increases. Then there will be only one mesh network that just grows. I like the idea of a large common mesh network – the mesh becomes a common communication infrastructure that can be used by everyone – NGOs, individuals, communities, entrepreneurs .

On the other hand technically there is no problem separating two or many meshes operating in the same area (using different channels and ESSIDs and IBSSIDs).

Things get slightly more complicated if you want to set up gateways that are routing from one mesh into the other and vice versa. Then you clearly want to separate the meshes by using non-overlapping sub-networks.

]]>