You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Guys
Output on Linux ( # iw mesh0 mpath dump) shows something like 0x15 which is in Hex (4 bits) but please look at the detail of this information from site:
Flags
This is a bitmask consisting of the following state flags for this path:
MESH_PATH_ACTIVE = BIT(0),
MESH_PATH_RESOLVING = BIT(1),
MESH_PATH_DSN_VALID = BIT(2),
MESH_PATH_FIXED = BIT(3),
MESH_PATH_RESOLVED = BIT(4),
which seems are using 5 bits.
Regards
The text was updated successfully, but these errors were encountered:
On Thu, Dec 17, 2015 at 03:29:00AM -0800, hesameddin wrote:
Hi Guys
Output on Linux ( # iw mesh0 mpath dump) shows something like 0x15 which is in Hex (4 bits) but please look at the detail of this information from site:
Flags
This is a bitmask consisting of the following state flags for this path:
MESH_PATH_ACTIVE = BIT(0),
MESH_PATH_RESOLVING = BIT(1),
MESH_PATH_DSN_VALID = BIT(2),
MESH_PATH_FIXED = BIT(3),
MESH_PATH_RESOLVED = BIT(4),
Hi Guys
Output on Linux ( # iw mesh0 mpath dump) shows something like 0x15 which is in Hex (4 bits) but please look at the detail of this information from site:
Flags
This is a bitmask consisting of the following state flags for this path:
MESH_PATH_ACTIVE = BIT(0),
MESH_PATH_RESOLVING = BIT(1),
MESH_PATH_DSN_VALID = BIT(2),
MESH_PATH_FIXED = BIT(3),
MESH_PATH_RESOLVED = BIT(4),
which seems are using 5 bits.
Regards
The text was updated successfully, but these errors were encountered: