ZRPd(http://www.zrp.be/) is a full implementation of the Zone Routing Protocol (ZRP) for Linux. It is a compromise between proactive and reactive routing protocols for ad-hoc Wi-Fi networks.
Optimized Link State Routing is one of several protocols under investigation by the IETF for use in ad-hoc wireless networks, where not only the end users are mobile, but also the routers, services, etc. This is an implementation that makes up a component of the Hipercom project(http://hipercom.inria.fr/OOLSR/).
The NIST Implementation(http://w3.antd.nist.gov/wctg/aodv_kernel/) of the Ad-Hoc On Demand Distance Vector protocol is a kernel-level driver for the Linux 2.4.x operating system. It supports the ix86, ARM, and MIPS architectures. Ad-Hoc routing protocols support networks in which both end users and routers can move freely while retaining network connections.
The UniK olsrd(http://www.olsr.org/) is an implementation of the Optimized Link State Routing protocol for mobile ad-hoc networks (MANETs). The protocol is described in RFC3626. The daemon supports IPv4 and IPv6. A GUI front-end that uses GTK2 is included.
Qolyester(http://qolsr.lri.fr/) is a C++ implementation of the OLSR protocol for mobile wireless ad hoc networks. It is meant to be enhanced with QoS features from the QOLSR research group.
AODV-UU(http://user.it.uu.se/~henrikl/aodv/) (Ad-hoc On-demand Distance Vector Routing, from Uppsala University) is a routing protocol under investigation by the IETF for use in ad-hoc networks, where both end-users and routers are mobile. This implementation supports IPv6 and multicasting and is compliant with AODV Draft v.13.
MIPL(http://www.mobile-ipv6.org/) Mobile IPv6 for Linux is an implementation of Mobility support in IPv6. Mobility support allows a mobile device to be tracked as it migrates between networks or even ISPs, allowing packets to be forwarded to where the device is currently located. The software is now mostly compliant with RFC 3775.
NRL OLSR(http://pf.itd.nrl.navy.mil/olsr/) is the NRL's implementation of the OLSR ad-hoc mobile network routing protocol, using RFC 3626 packet formats. It supports IPv4 and IPv6. Support for Ethereal and NS2 exists but may not be current. NRL's implementation is derived from INRIA's OLSR software router, which is also available.
ad-tolk(http://www.mit.edu/~ypod/software/) enables Wi-Fi enabled machines that are within range of each other to automatically setup their wireless interfaces by calculating IP addresses based on their MAC addresses (in the range 10.0.0.0/8) and joining an ad-hoc cell called "livefolio". Afterwards, all nodes can discover their neighbors and start exchanging text messages without any manual network configuration.
XIAN(http://xian.sourceforge.net/) (a cross-layer Interface for wireless ad-hoc networks) is a generic interface for experimenting cross-layer designs with legacy 802.11 networking cards using the MadWifi driver on Linux platforms. It can be used as a service by other network layers or system components to access information about the configuration and performance of MAC/PHY layers. The interface is fully implemented and is available for Linux over the MadWifi 802.11 driver.
AWDS (Ad-hoc Wireless Distribution Service)(http://awds.berlios.de/) is a layer 2 routing protocol for wireless mesh networks. It provides transparent Ethernet-like access to all participating nodes, thus easily allowing the employment of different higher level protocols like IP (with DHCP), IPv6, AppleTalk, etc.
Babel(http://www.pps.jussieu.fr/~jch/software/babel/) is a distance-vector routing protocol for IPv6. It is designed to be robust and work efficiently on both wired networks and wireless mesh networks.
Ahcpd(http://www.pps.jussieu.fr/~jch/software/ahcp/) is an implementation of the Ad-Hoc Configuration Protocol (AHCP), an IPv6 stateless configuration protocol for cases where standard auto-configuration and DHCPv6 don't work, such as mesh networks.
open80211s(http://www.open80211s.org/index.html) is a consortium of companies who are sponsoring (and collaborating in) the creation of an open-source implementation of the emerging IEEE 802.11s wireless mesh standard. The resulting software will run on Linux on commodity PC hardware.
B.A.T.M.A.N.(https://dev.open-mesh.net/batman) (better approach to mobile ad-hoc networking) is a routing protocol for multi-hop ad-hoc mesh networks.
A Singapore-based startup called Fonemesh(http://linuxdevices.com/news/NS9852477088.html) is preparing a mesh networking client for mobile phones, starting with the Linux-based OpenMoko Neo FreeRunner platform. The Fonemesh software identifies other Fonemesh users who are in WiFi range to set up a direct mesh connection for IM chat, VoIP, and file transfer.
Nightwing(http://nightwing.lugro-mesh.org.ar/) allows the creation of quickly deployed wireless networks without the need to make complicated configurations. With the implementation of a Mesh technology called B.A.T.M.A.N, Nightwing allows the extension of wireless networks with a simple way of adding devices that works with minimal human intervention. It has public and private connection interfaces, and the ability to filter content using OpenDNS. It is designed with security in mind, and has low hardware requirements.
The idea behind meshnode(http://www.meshnode.org) is (as the name suggests) - meshing. Based on OLSR (Optimized Link State Routing protocol) your network get more possibilities than ever before. The main feature of meshing is that every node automatically connects to each other. With this feature you easily can build cost-effective large scale wireless lan networks. Meshing does the dirty work for you - the dynamic routing saves you a lot of work and time because it's done on its own. Meshnode comes with two wireless lan cards which give you the possibility to build a strong infrastructure between the nodes. You can use the second card for what ever you like - for example provinding clients accesspoint services.
The MeshCube is a new hardware platform dedicated to WirelessLAN mesh routing, developed by 4G Systems, Hamburg. With a 400MHz MIPS processor, 64MB RAM and 32MB flash and up to 8 MiniPci cards, it is strong enough to provide excellent security and encryption, and flexible enough for custom applications and modifications.
The MeshCubeDistribution(http://www.meshcube.org/) is the Linux distribution running on the MeshCube. It's main features are MeshRouting, autoconfiguration of networking, security (IpSec, VPN) and the reduction in size to fit on the 32MB flash.