Hi,
On Thu, May 6, 2010 at 7:56 PM, pigiron <pigiron@xxxxxxx> wrote:
> On Thu, 6 May 2010 11:12:15 -0700 Steve deRosier <steve@xxxxxxxxxxx> wrote:
>
>> On Wed, May 5, 2010 at 10:01 AM, pigiron <pigiron@xxxxxxx> wrote:
>> > I noticed that decimal 52 is assigned to WLAN_EID_MESH_ID in the
>> > ieee80211.h file, and recently the same 52 was also assigned to
>> > WLAN_EID_NEIGHBOR_REPORT in the same enumerated ieee80211_eid{} structure.
>> >
>>
>> I can't answer the rest of your question, but AFAIK, the element IDs
>> for 802.11s mesh haven't been approved yet as the 802.11s draft
>> contains a note to that effect. The current ANA database sheet I
>> could find (Feb 2010) does have 52 assigned to Neighbor Report, and
>> the mesh element IDs are nowhere to be found.
>>
> I agree. The 802.11k-2008 standard has already been approved with Element ID
> 52 = Neighbor Report, so it's probably almost a guarantee that 802.11s won't be
> assigning 52 to anything in the future.
>
> I'm kind of stuck on this problem. I could probably find out what's causing the
> failure and create a patch... but the patch wouldn't be "The Right Thing To
> Do(tm)" if the router isn't supposed to be spewing that data to begin with.
I don't know about the router, nor if the IE ID clash is causing your
problem, but moving the mesh codes somewhere else in the unassigned ID
space would be a "A Good Thing To Do (tm)".
Cheers,
Javier
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
