John, On Sat, May 8, 2010 at 5:40 PM, John W. Linville <linville@xxxxxxxxxxxxx> wrote: > On Sat, May 08, 2010 at 09:34:45AM -0500, pigiron wrote: >> On Fri, 7 May 2010 09:29:18 -0700 Javier Cardona <javier@xxxxxxxxxxx> wrote: > >> > 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)". > >> Really? >> >> Wouldn't that cause a problem for the kids running OLPC? For instance, where >> some of the laptops are running an old level of code where WLAN_EID_MESH_ID=52 >> and others are running new code where WLAN_EID_MESH_ID=X. > > If I'm not mistaken, the mesh done in OLPC is already incompatible w/ > 802.11s anyway. Yes, the currently deployed laptops implement an earlier version of the 802.11s draft that's not compatible with what's in the kernel now. Javier -- Javier Cardona cozybit Inc. http://www.cozybit.com -- 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
