Justyn,
You can see this flag set in the FLAGS field of the RANN message (IEEE
802.11 broadcast Action frame) if you capture it in the air using, say,
Wireshark.
The FLAGS field from your iw mpath dump is something else. Depending on
your kernel and iw versions you can find their definitions, for example,
here:
/**
* enum mesh_path_flags - mac80211 mesh path flags
*
*
*
* @MESH_PATH_ACTIVE: the mesh path can be used for forwarding
* @MESH_PATH_RESOLVING: the discovery process is running for this mesh path
* @MESH_PATH_SN_VALID: the mesh path contains a valid destination sequence
* number
* @MESH_PATH_FIXED: the mesh path has been manually set and should not be
* modified
* @MESH_PATH_RESOLVED: the mesh path can has been resolved
* @MESH_PATH_REQ_QUEUED: there is an unsent path request for this
destination
* already queued up, waiting for the discovery process to start.
*
* MESH_PATH_RESOLVED is used by the mesh path timer to
* decide when to stop or cancel the mesh path discovery.
*/
enum mesh_path_flags {
MESH_PATH_ACTIVE = BIT(0),
MESH_PATH_RESOLVING = BIT(1),
MESH_PATH_SN_VALID = BIT(2),
MESH_PATH_FIXED = BIT(3),
MESH_PATH_RESOLVED = BIT(4),
MESH_PATH_REQ_QUEUED = BIT(5),
};
/**
* enum mesh_deferred_task_flags - mac80211 mesh deferred tasks
*
*
*
"nextgen/source/kernel/linux-next-20120905/working/linux-next-20120905/net/mac80211/mesh.h"
line 66 of 370 --1
7%-- col 2
...
/**
* enum nl80211_mpath_flags - nl80211 mesh path flags
*
* @NL80211_MPATH_FLAG_ACTIVE: the mesh path is active
* @NL80211_MPATH_FLAG_RESOLVING: the mesh path discovery process is running
* @NL80211_MPATH_FLAG_SN_VALID: the mesh path contains a valid SN
* @NL80211_MPATH_FLAG_FIXED: the mesh path has been manually set
* @NL80211_MPATH_FLAG_RESOLVED: the mesh path discovery process succeeded
*/
enum nl80211_mpath_flags {
NL80211_MPATH_FLAG_ACTIVE = 1<<0,
NL80211_MPATH_FLAG_RESOLVING = 1<<1,
NL80211_MPATH_FLAG_SN_VALID = 1<<2,
NL80211_MPATH_FLAG_FIXED = 1<<3,
NL80211_MPATH_FLAG_RESOLVED = 1<<4,
};
/**
"nextgen/source/app/app_opensource/iw/src/iw-3.6/nl80211.h" line 1735 of
3026 --57%-- col 9
I am out of context as to what you're trying to accomplish, so I am not
sure I can help with your particular problem.
Good luck,
Vadim
On Thu, Jan 24, 2013 at 1:55 PM, Justyn Bell <[email protected]> wrote:
> Vadim,
>
> Thank you for answering my question, but I have another, simpler one.
>
> How can I *see* this flag set? If I set the mesh_gate_announcements and
> mesh_hwmp_rootmode=1 on my gateway, then log into another node and do a "iw
> mesh0 mpath dump" nothing shows up under "FLAGS." Am I looking in the
> wrong place?
>
> I would like to somehow scrape some output, and resolve the mac address to
> an IP address so I can set the routing table accordingly.
>
> --
> Justyn
>
>
>
>
> On 01/23/2013 06:27 PM, Vadim Ivlev wrote:
>
> Hello Justyn.
>
> There is no need to send that information in the Beacon frame. It is
> sent in RANN Action broadcast frame with Gateway bit set in Flags field.
>
> Cheers,
>
> Vadim
>
> On Wed, Jan 23, 2013 at 7:57 PM, Justyn Bell <[email protected]> wrote:
>
>> Hello list,
>>
>> Is there a way in which you can get information about gateway nodes, ie,
>> nodes that have mesh_hwmp_rootmode and mesh_gate_announcements set = 1?
>>
>> I'm considering a project in which gateways can come and go, and all
>> other nodes will need to somehow get information about which nodes on the
>> mesh network are gateways. I have considered writing a program in which a
>> beacon is sent out at about once every 5 seconds from a gateway node, where
>> all other nodes can use the source address of this beacon to know the
>> address of the gateway. But since a node that is enabled with
>> mesh_gate_announcements is probably sending out some sort of beacon anyway,
>> I thought there was an easier way.
>>
>> It seems like there should be an iw dev MESH_INTF gateway dump, but
>> either I'm completely blind, or nothing is implemented.
>>
>> --
>> Justyn
>>
>> _______________________________________________
>> Devel mailing list
>> [email protected]
>> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
>>
>
>
>
> _______________________________________________
> Devel mailing
> [email protected]http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
>
>
> _______________________________________________
> Devel mailing list
> [email protected]
> http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
>
>
_______________________________________________
Devel mailing list
[email protected]
http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
