On Thu, Aug 31, 2017 at 11:30 PM, Greg Maitz <[email protected]> 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? > This results in the > last hop metric to become zero in function mesh_rx_path_sel_frame and > hwmp_preq_frame_process doesn't get called. Is this a known problem? > Can anyone provide suggestions to debug further? -- thomas
