Wireless Driver Required Changes

This page lists known issues related to the Wireless Driver, pointing to track numbers and suggested driver patches (where applicable) to fix the issues.

Probe Retry Limit

Probe Request/Response exchange between XOs is maintained for the sole reason of not breaking ad-hoc mode (which can be implemented passively and, in the end, brings no obvious advantages over the mesh mode). As it is a very bursty and demanding control traffic, particularly in dense networks, the number of retries, currently set to 2, should be reduced, if not removed altogether.

5.110.22.p6 allows probe response retries to be set from driver, from 0 (no probe response) to 15.

But a driver patch is required and can be found here.

Not responding to RREQs

In this bug, the XO stops responding to mesh path requests frames (RREQs). The main cause seems to be that the driver is not waiting long enough for the firmware to download.

A suggested fix can be found here.

Active antenna programming

Currently it is not possible to change mesh parameters in the standalone (active) antennae. In order to support this we need both a new firmware and driver support. Both can be found attached to this ticket

ethtool -S msh0 returning noise

The command ethtool -S eth0 should return useful NIC statistics, but it is dumping senseless numbers instead.

This is described in this ticket and is believed to be related to the driver. A patch/fix is attached to the ticket.

mesh view not working with 22.p8/p9

Due to http://dev.laptop.org/ticket/6818 mesh view does not work with firmware version 5.110.22.p8/9.

A patch for implementing the populating of the mesh filter is proposed here