Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iw mpath dump #46

Open
hesameddin opened this issue Dec 17, 2015 · 1 comment
Open

iw mpath dump #46

hesameddin opened this issue Dec 17, 2015 · 1 comment

Comments

@hesameddin
Copy link

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

@bcopeland
Copy link
Contributor

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),

which seems are using 5 bits
Regards

0x15 is five bits: b10101.

Bob Copeland %% http://bobcopeland.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants