On Fri, 2017-09-01 at 13:07 -0700, Thomas Pedersen wrote: > On Thu, Aug 31, 2017 at 11:30 PM, Greg Maitz <ghh19622@xxxxxxxxx> > wrote: > > Hi guys, > > > > I'm seeing a problem when I work on the wireless mesh between two > > linux devices. The root node has 3.18 kernel while the next hop > > station runs 2.6.37 kernel. I found the mpath->sn value is > > incorrect > > most of the time on the device having 2.6.37 kernel. After > > examining > > the code, in function hwmp_route_info_get [mesh_hwmp.c], after > > mesh_path_lookup, the sequence number (i.e, mpath->sn) is > > incorrect. > > For instance, I see mpath->sn having value 0x30950000. It should be > > 0x9530, while the orig_sn is having value 0x9531. > > Looks like an endianess bug. Are you testing on two platforms of > different endianess? Even if that's the case, wouldn't it mean some kind of conversion is missing somewhere? johannes
