Mesh TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Updated after firmware 5.220.10 release.)
 
Line 16: Line 16:


Separate wireless extensions ethX and mshX (b83)
Separate wireless extensions ethX and mshX (b83)
* Depends on reliable and independen mesh start
* Depends on reliable and independent mesh start
* Define attributes mshX should have (with Dan, Marcelo)
* Define attributes mshX should have (with Dan, Marcelo)
* Implement
* Implement

Latest revision as of 16:00, 9 April 2007

Next Release

Autonomous operation

  • Design
  • Implement
  • Test

Real fix for t914 -> joseph

Polish MPP scripts

  • auto-generate ANYCAST_MPP_IP
  • recognize interfaces
  • update masquerade with latest kernel

In the near future

Separate wireless extensions ethX and mshX (b83)

  • Depends on reliable and independent mesh start
  • Define attributes mshX should have (with Dan, Marcelo)
  • Implement

Mesh Beacons (b105)

  • Add Mesh IEs to Ad-Hoc beacons to advertise mesh capabilities.
  • Known limitation, cannot send beacons in infra.

Measure Performance

  • Improve FWT? Worth it?
  • Route clean-up time. Locks needed?
  • Start-up time.
  • Tune route costs

Slow Down RREQs.

  • Don't trigger many RREQ to the same node before the first one could

have been resolved.

Improve Stability/Reliability

Support for Monitor Mode (t886)

Wake-on-WLAN

Tune mesh parameters (t968)

Battery aware routing

Mesh auto-start on firmware load (b82)

  • Investigate netif_carrier_on behavior


Per-connection Mesh TTL

Driver Work

Distribution

rpm of MPP, lsmesh and other utils (fwt_list)


Legend

bXX -> bug in cozybit's bugzilla

tXX -> ticket in trac