Change History (25)

In 802.11s, there are mesh nodes, mesh portals (MPP), and also mesh access points (MAP). A mesh access point is the inverse of a mesh portal. It provides non-mesh wireless devices (like normal laptops) with an access point into the mesh, and potentially an internet connection, if the mesh also has a mesh portal.

Mesh access points could be useful. Once mesh portals are working, we should see how much more work they would require.

In 802.11s, there are mesh nodes, mesh portals (MPP), and also mesh access points (MAP). A mesh access point is the inverse of a mesh portal. It provides non-mesh wireless devices (like normal laptops) with an access point into the mesh, and potentially an internet connection, if the mesh also has a mesh portal.

Mesh access points could be useful. Once mesh portals are working, we should see how much more work they would require.

I believe MAPs would need RA-OLSR (or similar) and a whole bunch of new frame formats to be implemented.

mpp.py lives in the root of the NetworkManager src rpm, so this change involves updating that file and rebuilding, and then modifying pilgrim to mark the script executable rather than disabling it.

Ed/Kim, can someone confirm that this (moving MPP from off by default to on by default) is an accepted ECO for 8.2.1, and that it's okay to include it without a test plan having been provided?

As far as I am concerned, the script can be remain disabled. It just needs to be updated so that it can be enabled! So no pilgrim modifications required, just put the correct version of the script in the build!

If it takes us that long to do something that simple, we should all pack and go home now!!!!!!