http://pool.wiki.guifi.net/w/index.php?title=Special:NewPages&feed=atom&hideredirs=1&limit=50&offset=&namespace=0&username=&tagfilter=Guifi - Media-pool Common Repository - New pages [en]2024-03-29T10:16:38ZFrom Guifi - Media-pool Common RepositoryMediaWiki 1.22.0http://pool.wiki.guifi.net/wiki/Comparison_of_miniboardsComparison of miniboards2018-02-15T10:51:07Z<p>Al: </p>
<hr />
<div>{| class="wikitable" style="text-align: left;"<br />
! Photo<br />
! Brand<br />
! Model & Version<br />
! Target/subtarget<br />
! OpenWrt support<br />
! Chipset/s<br />
! CPU MHz<br />
! Flash MB<br />
! RAM MB<br />
! Radio 1<br />
! Radio 2<br />
! Eth 100M<br />
! Eth GBit<br />
! Antenna<br />
! USB<br />
! GPIO<br />
! Power input<br />
! Power consumption high use<br />
! Power consumption minimum use<br />
! Price<br />
! Size<br />
! Release date<br />
! Comments<br />
! Known Issues<br />
|-<br />
| <br />
| [http://oolite.cn/ Gainstrong]<br />
| [http://oolite.cn/category/qualcomm/qca9531/minibox-v3-2 minibox v3.2]<br />
| ar71xx/generic<br />
| style="font-size: 86%;"| [https://github.com/openwrt/openwrt/pull/645#pullrequestreview-89386143 waiting merge pull request]<br />
| Atheros: QCA9531, QCA9887<br />
| 560<br />
| 8/16<br />
| 64/128<br />
| 2.4GHz <small>BGN MiMo QCA9531</small><br />
| 5GHz <small>AC QCA9887</small><br />
| 2<br />
| No<br />
| 3 x Hirose U.FL <small>(2x2 MIMO 2.4GHz + 1x1 MIMO 5GHz)</small><br />
| 1 x USB 2.0<br />
| <br />
| 5V<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| style="white-space: nowrap; font-size: 86%;"|<br />
* Same chipsets than Oolite 5.2 & GL-Inet AR300MD <br />
| <br />
|-<br />
| [[File:Oolite v5.2.jpg|50px]]<br />
| [http://oolite.cn/ Gainstrong]<br />
| [http://oolite.cn/category/qualcomm/qca9531/oolite-v5-2 Oolite v5.2]<br />
| ar71xx/generic<br />
| style="font-size: 86%;"| [https://openwrt.org/toh/views/toh_fwdownload?dataflt%5BBrand*%7E%5D=gainstrong Yes, from 18.06]<br />
| Atheros: QCA9531, QCA9887<br />
| 560<br />
| 8/16<br />
| 64/128<br />
| 2.4GHz <small>BGN MiMo QCA9531</small><br />
| 5GHz <small>AC QCA9887</small><br />
| 5 port <small>Switch with MAC/PHY (w/o connector)</small><br />
| No<br />
| 3 x Hirose U.FL <small>(2x2 MIMO 2.4GHz + 1x1 MIMO 5GHz)</small><br />
| 1 x USB 2.0 <small>(w/o connector)</small><br />
| 18<br />
| 3.3V and 5V at the same time<br />
| <br />
| <br />
| [https://spanish.alibaba.com/product-detail/qca9531-and-qca9887-chipset-733mbps-module-60670267750.html 10-16$]<br />
| 39.5x78mm<br />
| 2017-04-12<br />
| style="white-space: nowrap; font-size: 86%;"|<br />
* Same chipsets than [http://oolite.cn/category/qualcomm/qca9531/minibox-v3-2 Minibox v3.2] & GL-Inet AR300MD <br />
* [http://oolite.cn/oolite-v5-2-upgrade.html#2.tftp%20upgrade dev board available]<br />
* WiFi enabled by factory defaults<br />
* [https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=8c64824576598117958691853de68bf4dcfc3c06 commitdiff of this support]<br />
| style="white-space: nowrap; font-size: 86%;"|<br />
* Has not input power regulator, it needs exactly 3.3V or 5V.<br />
* Sometimes radio1 without MAC address<br />
* General cheap and bad electric components<br />
|-<br />
| <br />
| [https://www.8devices.com 8devices]<br />
| [https://www.8devices.com/products/jalapeno Jalapeno]<br />
| <br />
| <br />
| <br />
| <br />
| 128 MB NAND and 8 MB NOR<br />
| 256 MB DDR3<br />
| dual band<br />
| ---<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| 3.3V or 5V<br />
| 12.75W (5V 2.55A)<br />
| 2.05W (5V 0.41A)<br />
| 59$<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| [https://labs.mediatek.com/en LinkIt]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}</div>Alhttp://pool.wiki.guifi.net/wiki/Ninux.orgNinux.org2015-05-16T17:17:36Z<p>Al: </p>
<hr />
<div>{{Infobox Server<br />
|Place=Italy<br />
|Domain name=No Domain Name yet<br />
|Map=Has not map yet<br />
|Nodes URL=https://ninux.nodeshot.org/api/v1/nodes.geojson<br />
|Links URL=https://ninux.nodeshot.org/api/v1/links.geojson<br />
|Traffic URL=Traffic URL<br />
|Status=Unknow<br />
|Network model=Unknow<br />
|Protocol=Unknow<br />
|Physical layer technology=Unknow<br />
|Frequency band or cable=2.4GHz<br />
|Management model=Unknow<br />
}}<br />
<br />
[[Category:Wireless network]]<br />
[[Wireless network::open]]</div>Alhttp://pool.wiki.guifi.net/wiki/Comparison_of_descriptions_modelsComparison of descriptions models2015-05-12T06:20:08Z<p>Al: </p>
<hr />
<div>[[:en:CNML|CNML]] was designed for a lot of elements that described each zone, node, links and traffic from a Community Network, but finally only was implemented from guifi.net for hierarchy based on this schema:<br />
<br />
[[File:cnml-tree.png]]<br />
<br />
NetJSON is designed and implemented just for elements described below that include metric and topology values. You can get NetJSON from [[https://github.com/ninuxorg/netdiff Netdiff Netdiff parser]. ''Netdiff provide parsers for [[OLSR]] 0.6.x jsoninfo plugin, [[BATMAN-adv]] [[alfred]] tool, [[CNML]] and recently a beta version for [[BMX6]] b6m plugin<ref>https://github.com/gabri94/netdiff/commit/718ddbbde9ab9f3170c34d3f58e1f9f82a3c91d8</ref>.<br />
<br />
Also you can get NetJSON directly from nodes with [http://netengine.rtfd.org Netengine] tool (python library) which provide a single API to extract common information from network devices using different protocols (eg: SNMP, SSH, HTTP) and different firwmares (OpenWRT and AirOS).<br />
<br />
= NetJSON Network Device Configuration =<br />
<br />
{| border="1" cellspacing="0"<br />
! NetJSON<br />
! CNML proposed standard<br />
! CNML from guifi.net<br />
|-<br />
| general<br />
| ''cnml''<br />
| cnml<br />
|-<br />
| hardware<br />
| ''hardware capability''<br />
| -<br />
|-<br />
| operating_system<br />
| -<br />
| -<br />
|-<br />
| resources<br />
| -<br />
| -<br />
|-<br />
| interfaces<br />
| -<br />
| interface<br />
|-<br />
| physical_devices<br />
| ''devices''<br />
| -<br />
|-<br />
| routing<br />
| -<br />
| -<br />
|-<br />
| dns_servers<br />
| -<br />
| -<br />
|-<br />
| dns_search<br />
| -<br />
| -<br />
|}<br />
<br />
= NetJSON Device Monitoring Data =<br />
<br />
{| border="1" cellspacing="0"<br />
! NetJSON<br />
! CNML proposed standard<br />
! CNML from guifi.net<br />
|-<br />
| general<br />
| ''not for monitoring''<br />
| ''N/A (available from SNMP)''<br />
|-<br />
| interfaces<br />
| ''not for monitoring''<br />
| ''N/A (available from SNMP)''<br />
|-<br />
| resources<br />
| ''not for monitoring''<br />
| ''N/A''<br />
|}<br />
<br />
= NetJSON Network Routes =<br />
<br />
{| border="1" cellspacing="0"<br />
! NetJSON<br />
! CNML proposed standard<br />
! CNML from guifi.net<br />
|-<br />
| protocol<br />
| ''not for routes''<br />
| ''N/A''<br />
|-<br />
| version<br />
| ''not for routes''<br />
| ''N/A''<br />
|-<br />
| metric<br />
| ''not for routes''<br />
| ''N/A''<br />
|}<br />
<br />
= NetJSON Network Graph =<br />
<br />
{| border="1" cellspacing="0"<br />
! NetJSON<br />
! CNML proposed standard<br />
! CNML from guifi.net<br />
|- <br />
| version<br />
| cnml<br />
| cnml<br />
|-<br />
| metric<br />
| -<br />
| -<br />
|-<br />
| nodes<br />
| node information<br />
| node<br />
|-<br />
| links<br />
| -<br />
| link<br />
|-<br />
| revision (opt)<br />
| -<br />
| -<br />
|-<br />
| router_id (opt)<br />
| -<br />
| -<br />
|}<br />
<br />
= CNML =<br />
<br />
{| border="1" cellspacing="0"<br />
! Proposed standard CNML element<br />
! Used CNML element<br />
! Attributes<br />
|-<br />
|''cnml''<br />
|cnml<br />
|generated, server_id, server_url, version<br />
|-<br />
|''hardware capability''<br />
|<br />
|<br />
|-<br />
|''mapping''<br />
|class<br />
|mapping, network_description<br />
|-<br />
|''network environment''<br />
|network<br />
|ap, client, devices, links, nodes, services <br />
|-<br />
|''content sharing''<br />
|<br />
|<br />
|-<br />
|<br />
|zone<br />
|access_points, box, clients, created, devices, dns_servers, graph_server, id, links, ntp_servers, parent_id, services, time_zone, title, updated, zone_nodes <br />
|-<br />
|''node information''<br />
|node<br />
|access_points, antenna_elevation, clients, created, devices, graph_server, id, lat, links, lon, services, status, title, updated <br />
|-<br />
|''devices''<br />
|device<br />
|created, firmware, graph_server, id, name, snmp_index, status, title, type, updated <br />
|-<br />
|<br />
|radio<br />
|antenna_angle, antenna_azimuth, antenna_gain, channel, device_id, id, mode, protocol, snmp_index, snmp_name, ssid <br />
|-<br />
|<br />
|service<br />
|created, id, status, title, type, updated <br />
|-<br />
|<br />
|interface<br />
|id, ipv4, mac, mask, type <br />
|-<br />
|<br />
|link<br />
|id, link_status, link_type, linked_device_id, linked_interface_id, linked_node_id <br />
|-<br />
|''owner of device''<br />
|<br />
|<br />
|-<br />
|''picopeer''<br />
|<br />
|<br />
|-<br />
|''traffic''<br />
|<br />
|<br />
|-<br />
|''scale of interest to the network''<br />
|<br />
|<br />
|-<br />
|''personal keyring''<br />
|<br />
|<br />
|}<br />
<br />
= See Also =<br />
*[[NetJSON]]<br />
*[[:en:CNML]]<br />
<br />
= Notes =<br />
<references /><br />
<br />
[[Category:CNML]]<br />
[[Category:NetJSON]]</div>Alhttp://pool.wiki.guifi.net/wiki/NetJSONNetJSON2015-05-11T18:57:13Z<p>Al: </p>
<hr />
<div>= NetJSON: data interchange format for networks =<br />
[[image:netjson-logo.png]]<br />
<br />
NetJSON is a data interchange format for encoding the basic building blocks of networking:<br />
<br />
* [https://github.com/interop-dev/json-for-networks#network-device-configuration devices]<br />
* [https://github.com/interop-dev/json-for-networks#device-monitoring-data monitoring data]<br />
* [https://github.com/interop-dev/json-for-networks#network-routes routes]<br />
* [https://github.com/interop-dev/json-for-networks#network-graph network topology]<br />
<br />
[https://lists.funkfeuer.at/mailman/listinfo/interop-dev Reach us on the Mailing List] - [https://lists.funkfeuer.at/pipermail/interop-dev/ Consult the ML Archives]<br />
<br />
== Goals ==<br />
<br />
Define simple JSON data structures that contain the lowest common denominator of:<br />
<br />
* network device configurations<br />
* monitoring data extracted from devices<br />
* routes of a routing protocol<br />
<br />
The resulting JSON structures should follow these general principles:<br />
<br />
* [[wikipedia:KISS_principle|KISS]]: keep it simple, proceed one step at time<br />
* [[wikipedia:Principle_of_least_astonishment|Principle of least astonishment]]: use accepted terminology<br />
* '''Explicit names''': prefer verbose explicit names, eg: &quot;operating_system&quot; is better than &quot;os&quot;<br />
<br />
Once we get to a first version, we should implement these formats in software like:<br />
<br />
* Firwmares and linux modules<br />
* Routing protocols<br />
* Monitoring agents<br />
* Node databases<br />
* Monitoring tools<br />
<br />
== Motivations ==<br />
<br />
Developing software that deals with networks is harder than it should.<br />
<br />
Developers have to take into account all the differences between vendors, operating systems, routing protocols, hardware and (when working with community networks) with the different approaches of each community.<br />
<br />
Very often, each vendor develops an entire stack that works exclusively with its own hardware and software.<br />
<br />
There exist many libraries and web apps for networking, but it is very hard to make them interoperable, that is, making them talk and understand one another with minimum effort.<br />
<br />
Instead of creating an ecosystem, we have been creating silos that hardly talk to each other.<br />
<br />
This is an attempt to invert this trend, following the successful example of the [[wikipedia:GeoJSON|GeoJSON]] open standard.<br />
<br />
By defining common data structures we can allow developers to focus on their goals instead of having to struggle with the differences of each vendor, firmware, routing protocol or community.<br />
<br />
Moreover, we will lay the groundwork for an '''ecosystem''' to grow organically: once the standard JSON structures are defined and adopted it will be easier to write systems that work together, instead of creating silos.<br />
<br />
== Definitions ==<br />
<br />
* JavaScript Object Notation (JSON), and the terms object, name, value, array, and number, are defined in [http://www.ietf.org/rfc/rfc4627.txt IETF RTC 4627].<br />
* The key words &quot;MUST&quot;, &quot;MUST NOT&quot;, &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;, &quot;SHOULD&quot;, &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;, &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this document are to be interpreted as described in [http://www.ietf.org/rfc/rfc2119.txt IETF RFC 2119].<br />
<br />
= Network Device Configuration =<br />
<br />
'''Definition''': configuration and properties of a network device.<br />
<br />
'''Example''': [https://github.com/interop-dev/json-for-networks/blob/master/examples/device-configuration.json device-configuration.json]<br />
<br />
A <code>Network Device Configuration</code> object must have a member with the name <code>type</code> and value <code>DeviceConfiguration</code>.<br />
<br />
The object should be composed of the following members:<br />
<br />
* <code>general</code><br />
* <code>hardware</code><br />
* <code>operating_system</code><br />
* <code>resources</code><br />
* <code>interfaces</code><br />
* <code>physical_devices</code><br />
* <code>routing</code><br />
* <code>dns_servers</code><br />
* <code>dns_search</code><br />
<br />
All the values of each member must be objects which further describe each component of a network device.<br />
<br />
'''Each object will be described more in detail in the future iterations of this project'''.<br />
<br />
Software providing this JSON format to should return all the information it is able to access from the system, according to security and privacy rules defined by the device owner or network administrator.<br />
<br />
Software consuming this JSON format must be able to handle missing attributes.<br />
<br />
Software consuming this JSON format must ignore unrecognized attributes.<br />
<br />
= Device Monitoring Data =<br />
<br />
'''Definition''': information that indicates the behaviour of a device that changes over time.<br />
<br />
'''Example''': [https://github.com/interop-dev/network-device-schema/blob/master/examples/monitoring-data.json monitoring-data.json]<br />
<br />
A <code>Device Monitoring</code> object must have a member with the name <code>type</code> and value <code>DeviceMonitoring</code>.<br />
<br />
The object should be composed of the following members:<br />
<br />
* <code>general</code><br />
* <code>interfaces</code><br />
* <code>resources</code><br />
<br />
'''Each object will be described more in detail in the future iterations of this project'''.<br />
<br />
= Network Routes =<br />
<br />
'''Definition''': a list of routes of a dynamic routing protocol or statically configured on the device. May be contained in a <code>DeviceConfiguration</code> object.<br />
<br />
'''Example''': [https://github.com/interop-dev/network-device-schema/blob/master/examples/network-routes.json network-routes.json]<br />
<br />
A <code>Network Routes</code> object must have a member with the name <code>type</code> and value <code>NetworkRoutes</code>.<br />
<br />
It must define the following members:<br />
<br />
* <code>protocol</code>: the name of the routing protocol, can be <code>static</code> when representing static routes<br />
* <code>version</code>: the version of the routing protocol, can be <code>null</code> when representing static routes<br />
* <code>metric</code>: a string which indicates the name of main routing metric used by the routing protocol to determine the best routes when sending packets, can be <code>null</code> when representing static routes<br />
<br />
It may also define the following optional members:<br />
<br />
* <code>revision</code>: the revision from which the routing protocol binary was built (eg: git hash, svn revision)<br />
* <code>router_id</code>: ID of the router on which the protocol is running<br />
<br />
When contained in a <code>DeviceConfiguration</code>, a <code>Network Routes</code> object indicates either that a routing protocol is running on the device or that static routes have been set; in this case the member <code>routes</code> is required only for static routes.<br />
<br />
When self contained, a <code>NetworkRoutes</code> object represents a routing table and must define a <code>routes</code> member, which contains a list of route objects.<br />
<br />
Each <code>route</code> object must define the following members:<br />
<br />
* <code>destination</code>: a string indicating the ip address, prefix or mac address that will be matched to the destination of the traffic<br />
* <code>next</code>: a string indicating the ip address, prefix or mac address of the next hop<br />
* <code>device</code>: a string indicating the interface the traffic will be going to, '''it can be omitted when representing static routes'''<br />
* <code>cost</code>: the numeric value of the routing metric; lower cost is better, '''it can be omitted when representing static routes'''<br />
<br />
A <code>route</code> object may also define a <code>source</code> member indicating the source (necessary for source-specific routing).<br />
<br />
= Network Graph =<br />
<br />
'''Definition''': a list of nodes and links that represent the topology of a network.<br />
<br />
'''Example''': [https://github.com/interop-dev/network-device-schema/blob/master/examples/network-graph.json network-graph.json]<br />
<br />
A <code>Network Graph</code> object must have a member with the name <code>type</code> and value <code>NetworkGraph</code>.<br />
<br />
It must define the following members:<br />
<br />
* <code>protocol</code>: the name of the routing protocol, can be <code>static</code> when representing static routes<br />
* <code>version</code>: the version of the routing protocol, can be <code>null</code> when representing static routes<br />
* <code>metric</code>: a string which indicates the name of main routing metric used by the routing protocol to determine the best routes when sending packets, can be <code>null</code> when representing static routes<br />
* <code>nodes</code>: a list of nodes<br />
* <code>links</code>: a list of links<br />
<br />
It may also define the following optional members:<br />
<br />
* <code>revision</code>: the revision from which the routing protocol binary was built (eg: git hash, svn revision)<br />
* <code>router_id</code>: ID of the router on which the protocol is running<br />
<br />
Each <code>node</code> object must define an <code>id</code> member and may define the following optional members:<br />
<br />
* <code>label</code>: a label for the node<br />
* <code>properties</code>: an object to store additional / custom metadata<br />
<br />
Each <code>link</code> object must define the following members:<br />
<br />
* <code>source</code>: id of the <code>target</code> node<br />
* <code>target</code>: id of the <code>source</code> node<br />
* <code>weight</code>: metric value for the link<br />
<br />
Each <code>link</code> object may also define a <code>properties</code> object to store additional / custom metadata.<br />
<br />
= FAQs =<br />
Frequentedly Asked Questions.<br />
<br />
== Is this some kind of new [[wikipedia:SNMP|SNMP]]? ==<br />
Not exactly. Think about NetJSON as a possible common language that libraries and applications can adopt in order to interoperate on different levels.<br />
<br />
NetJSON does not aim to define how the data is exchanged, it could be exposed via an HTTP API, it could be sent through UDP packets, it could be copied from application A and pasted into application B.<br />
<br />
= See also =<br />
* [[:en:CNML]] <br />
<br />
= Links =<br />
* [http://netjson.org NetJSON] official page.<br />
<br />
[[Category:Standards]]</div>Alhttp://pool.wiki.guifi.net/wiki/SchleuderSchleuder2014-11-09T20:05:31Z<p>Al: </p>
<hr />
<div>Install all dependences:<br />
On Debian stable (wheezy):<br />
apt-get install ruby libmagic-dev ruby-gpgme gnupg libgpgme11 libgpgme11-dev build-essential ruby-dev<br />
<br />
Install schleuder with gem:<br />
gem install schleuder<br />
<br />
After finish installation, if you get a note with one dependency missing execute:<br />
schleuder-fix-gem-dependencies<br />
<br />
== Create a list ==<br />
schleuder-newlist listname@gpg.marsupi.org -adminaddress anemail@domain.cc -initmember firstmember@domain.cc -initmemberkey /tmp/firstmember.pub</div>Alhttp://pool.wiki.guifi.net/wiki/Comparison_of_mapsComparison of maps2014-05-01T18:45:51Z<p>Al: </p>
<hr />
<div>=== Software ===<br />
<br />
{| class="wikitable sortable"<br />
|- style="background:#ececec;"<br />
! Map software / Link<br />
! Source code<br />
! Development contact<br />
! Community Network/s<br />
! Location<br />
! Software license<br />
! Content license<br />
! Development status<br />
! Sustainability model<br />
! Last release<br />
! Programming language<br />
! Data backend<br />
|-<br />
| [http://guifi.net/maps Guifimaps]<br />
| https://gitorious.org/guifi/guifimaps<br />
| [https://llistes.guifi.net/sympa/info/guifi-dev Guifi-dev mailing list]<br />
| [http://guifi.net Guifi.net], [http://qmp.cat qMp]<br />
| WorldWide, specially Catalonia<br />
|<br />
|<br />
| Stable - Slow<br />
|<br />
| 2013-08-05<br />
| PHP<br />
| MySQL<br />
|-<br />
| [http://libremap.net LibreMap]<br />
| https://github.com/libremap<br />
| [https://lists.libremap.net/mailman/listinfo/discussion Libremap mailing list]<br />
| [http://www.quintanalibre.org.ar/ Quintana Libre], [http://deltalibre.org.ar/ Delta Libre], [http://freifunk.net/ Freifunk], [http://qmp.cat qMp]<br />
| Argentina, Germany, Catalonia<br />
| GPLv3<br />
| [http://opendatacommons.org/licenses/odbl/summary/ ODbL]<br />
| Alpha - Slow<br />
| Volunteers<br />
| 2013-10-03 backbone, 2014-08-05 agent<br />
| JavaScript<br />
| CouchDB<br />
|-<br />
|[http://map.ninux.org/ Nodeshot 0.9]<br />
|rowspan="2"| https://github.com/ninuxorg/nodeshot<br />
|rowspan="2"| [http://ml.ninux.org/mailman/listinfo/nodeshot Nodeshot mailing list]<br />
|rowspan="2"| [http://map.ninux.org/ Ninux]<br />
|rowspan="2"| Italy<br />
| <br />
| <br />
| 0.9.x stable slow<br />
| [http://blog.ninux.org/2011/09/06/gsoc-2011-nodeshot/ Grant]<br />
| 2013-12-03<br />
| Python<br />
| MySQL<br />
|-<br />
| [https://ninux.nodeshot.org Nodeshot 1.0 alpha]<br />
| TBA (FOSS)<br />
| <br />
| 1.0 alpha quick<br />
| [http://blog.ninux.org/2014/04/23/gsoc-2014-si-parte-con-netengine/ Grant] + Reusable business model (Cineca Consortium)<br />
| 2014-10-13<br />
| Python<br />
| PostgreSQL<br />
|-<br />
| WiND<br />
| https://github.com/wind-project/wind<br />
|<br />
| [http://www.awmn.net Athens Wireless Metropolitan Network (AWMN)]<br />
| Greece<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| [https://nodes.wlan-si.net/network/map/ Nodewatcher]<br />
| https://github.com/wlanslovenija/nodewatcher<br />
| [https://dev.wlan-si.net/wiki/Nodewatcher Website]<br> [https://wlan-si.net/lists/info/nodewatcher nodewatcher mailing list]<br />
| [https://wlan-si.net/ wlan slovenija]<br />
| Slovenia<br />
| Affero GPL v3<br />
|<br />
| 3.0&nbsp;(Development) <br> 2.0 (Stable)<br />
|<br />
|<br />
| Python / Django<br />
| GeoDjango<br />
|-<br />
|olsrmap ([http://➡.ws/ejklrhw4 one instance], [http://➡.ws/eyt6st other instance])<br />
|https://github.com/Pitxyoki/olsrmap/<br />
|<br />
|[http://unimos.net Unimos]<br />
|Portugal<br />
|[https://github.com/Pitxyoki/olsrmap/blob/master/LICENSE Mixed licences]<br />
|<br />
|Slow<br />
|<br />
|<br />
|PHP + Javascript<br />
|Reads directly from OLSR nodes' latlon.js file (javascript spit by the OLSR daemon)<br />
|}<br />
<br />
=== Features list ===<br />
<br />
{| class="wikitable sortable"<br />
|- style="background:#ececec;"<br />
! Map software / Link<br />
! Push from nodes<br />
! Pull from nodes<br />
! Interoperability mode (with others maps)<br />
! Export<br />
! Import<br />
! API<br />
! Wired links (Optic Fiber,...)<br />
! OpenLayers<br />
! Interactive extended data on map<br />
! History<br />
! Multilingual<br />
! Provisioning<br />
! Comments<br />
|-<br />
| Guifimaps<br />
| No, map shows direct human drawing in database<br />
|<br />
| Not supported<br />
| Yes,via CNML and GML<br />
|<br />
| [[:es:API|Yes]]<br />
| Not supported<br />
| Supported<br />
| No<br />
| [http://guifi.net/ca/guifi/menu/stats/growthmap External supported (via graph SNMP servers)]<br />
| Partially<br />
| Yes, via justoneclick ([http://dev.qmp.cat/projects/qmp/wiki/Guifi_oneclick or automatized in qMp])<br />
| -<br />
|-<br />
| LibreMap<br />
| [https://github.com/libremap/libremap-agent-openwrt libremap openwrt agent]<br />
|<br />
| [https://github.com/libremap/libremap-adapter-openwifimap openwifimap adapter]<br />
| Yes (CouchDB replication)<br />
| Yes (CouchDB replication)<br />
| [https://github.com/libremap/libremap-api/blob/master/doc-api.md Yes]<br />
| Yes (supports arbitrary link types)<br />
| Not supported <br />
| Only JSON not complete data<br />
| Not supported <br />
| No<br />
|<br />
| Unlimited scalability; Decentralized via CouchDB's replication<br />
|-<br />
| Nodeshot 0.9<br />
|<br />
|<br />
| Not supported<br />
| KML<br />
| Supported<br />
|<br />
|<br />
|<br />
| Yes<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Nodeshot 1.0 alpha<br />
| Work in progress<br />
| [https://github.com/ninuxorg/netengine Supported]<br />
| [http://nodeshot.readthedocs.org/en/latest/topics/interoperability.html Work in progress]<br />
| GeoJSON API / Django Fixtures<br />
| Supported<br />
|<br />
| [https://github.com/ninuxorg/nodeshot/blob/master/nodeshot/networking/links/models/choices.py#L14 In development]<br />
| [https://github.com/ninuxorg/nodeshot/issues/122 Leaflet + configurable tileserver]<br />
| Yes<br />
| Planned<br />
| Only UI<br />
|<br />
|<br />
|-<br />
| WiND<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Nodewatcher<br />
| [https://github.com/wlanslovenija/nodewatcher-agent nodewatcher openwrt agent]<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|Yes, OLSR data and "animated links"<br />
|<br />
|<br />
|<br />
|Contains a distance measurement tool, and a terrain profile analysis tool (by an external provider [inspired by Guifi's])<br />
|-<br />
| olsrmap<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== Features for mapping not implemented in any map software (yet, work in progress) ==<br />
* [http://trac.guifi.net/ticket/16 Profiles with buildings]<br />
* Node picture vision<br />
<br />
== Simple maps ==<br />
* [http://www.pilsfree.net/mapa/ PilsFree network] (Czech Republic)<br />
<br />
[[category:comparision]]<br />
[[category:map]]</div>Alhttp://pool.wiki.guifi.net/wiki/Fr%C3%A9ttinga/caFréttinga/ca2014-01-07T05:50:54Z<p>Al: </p>
<hr />
<div><languages /><br />
Fréttinga es una municipalitat petita. I poc més.<br />
<br />
== Serveis ==<br />
<br />
No hi ha massa serveis. Hi ha una botiga i un ferry de cotxes visita la isla des del continent un cop al dia.</div>Alhttp://pool.wiki.guifi.net/wiki/Fr%C3%A9ttingaFréttinga2014-01-07T05:46:30Z<p>Al: </p>
<hr />
<div><languages /><br />
<translate><br />
<!--T:1--><br />
Fréttinga is a small municipality in MungoLand, located on the BaMungo island.<br />
It hosts a population of about 400 people. It has some agriculture and fishing.<br />
Tourists like to visit it in the summer time.<br />
<br />
== Services == <!--T:2--><br />
<br />
<!--T:3--><br />
It doesn't have many services. There is a shop and car ferry visits the island<br />
from mainland once a day.<br />
</translate></div>Alhttp://pool.wiki.guifi.net/wiki/Main_PageMain Page2009-03-23T15:01:20Z<p>Al: </p>
<hr />
<div>__NOTITLE__<br />
__NOTOC__<br />
<br />
<div style="width: 600px; margin: 0 auto; background-color: #fcfcfc; border: 1px solid #ccc; border-bottom: 5px groove #999999; border-right:5px groove #999999; text-align: center; padding: 0.4em;"><br />
<div style="font-size: 162%; padding: 0.1em;">Welcome to the '''Guifi.net''' Open Documentation Wiki</div><br />
<div style="font-size: 95%;">Documentation about the open, free and neutral network.</div><br />
<div style="font-size: 120%; padding: 0.1em;">[[Special:Upload|Puja media! - Upload Media! - ¡Sube media!]]</div><br />
<div style="font-size: 120%; padding: 0.1em;">[[Special:ListFiles|Veure tot el media - View All Media - Ver todo el media]]</div><br />
</div><br />
<br />
===== es =====<br />
Siéntete libre de [[Special:Upload|subir archivos]] ya sean fotos, vídeos, documentos de texto, en cualquier idioma. Ten en cuenta que deben subirse con una licencia libre. Los archivos serán accesibles desde [http://guifi.net/es Guifi.net], no es necesario que sean sobre la temática Guifi.net en este wiki, pero deben ser útiles a la comunidad.<br />
<br />
===== en =====<br />
Feel free to [[Special: Upload|upload files]] like photos, videos or documents in any language. Keep in mind that must upload with one free license. The files will be accessible from [http://guifi.net/en Guifi.net], is not necessary that they are on thematic Guifi.net in this wiki, but must be useful to the community.<br />
<br />
{| id="mp-upper" style="width: 100%; margin:6px 0 0 0; background:none; border-spacing: 0px;"<br />
| style="width:50%; style="background:#f5faff;border:1px solid #cedff2;padding:10px;margin-bottom:7px; vertical-align:top;-moz-border-radius:1em;-webkit-border-radius:1em;border-radius:1em; " | <br />
<div id="mp-dyk"><br />
<div style="font-size: 162%; padding: 0.1em;">Migración de contenidos del wiki en curso</div><br />
El sistema de múltiples idiomas en los wikis de Guifi.net está siendo substituido desde el actual modelo “interwiki” donde diferentes instancias de Mediawiki se enlazan unas a otras hacia la [https://www.mediawiki.org/wiki/Extension:Translate extensión “Translate”] que permite mantener actualizaciones de las traducciones y traducir por bloques de texto.<br />
<br />
En estos momentos están conviviendo ambos modelos pero sólo en los wikis català, español y português, siendo el inglés y el resto ya pasados a este que actualmente se llama “pool.wiki.guifi.net”.<br />
<br />
Actualmente, para traducir un artículo de un idioma a otro con esta extensión el artículo primeramente debe estar en inglés y, de ahí traducir al resto de idiomas. Cambiaremos el ''idioma fuente'' a medida que vayamos importando de cada uno del resto de idiomas.<br />
<br />
El cambio manual ya no será necesario en un futuro, cuando se solucione una propuesta de [https://www.mediawiki.org/wiki/Extension:Translate/Usability_improvements_2014 feature o bug] que permite que cada artículo tenga un ''idioma fuente'' diferente (source language). Por favor, subscríbete y comenta en estas 3 propuestas de features/bugs que, una vez resueltos, permitirán esta función.<br />
* [https://phabricator.wikimedia.org/T37489 The source language of a page should be arbitrary]<br />
* [https://phabricator.wikimedia.org/T89637 Automatically blacklist the page's source language without manual $wgTranslateBlacklist]<br />
* [https://phabricator.wikimedia.org/T69223 Schema change for page content language]<br />
<br />
Para comentarios y propuestas sobre la migración que estamos realizando, utilicen la [[Talk:Main_Page|página de discusión]].<br />
<br />
<br />
<div style="font-size: 162%; padding: 0.1em;">Breve manual de traducción</div><br />
Pasamos a explicar brevemente cómo traducir artículos con esta extensión. Para una explicación más detallada puedes leer el [https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example manual en varios idiomas].<br />
<br />
Escribe o edita una página normalmente. Para hacerla traducible con esta extensión coloca al principio y al final del artículo:<br />
<nowiki>&lt;languages /><br />
&lt;translate><br />
...<br />
&lt;/translate></nowiki><br />
<br />
''en desarrollo''<br />
|}</div>MediaWiki default