On Fri, Jul 24, 2015 at 11:02:30AM +0200, Baptiste Clenet wrote: > 2015-07-24 10:47 GMT+02:00 Baptiste Clenet <bapclenet@xxxxxxxxx>: > > 2015-07-24 10:31 GMT+02:00 Alexander Aring <alex.aring@xxxxxxxxx>: > >> Hi, > >> > >> On Fri, Jul 24, 2015 at 09:56:49AM +0200, Baptiste Clenet wrote: > >>> Hi, > >>> > >>> What is SAM value? I got "ieee802154 phy0 wpan0: SAM value 0x3 not > >>> supported" when I receive a ping from another board. > >>> > >> > >> I think you hit [0]. You got that because we received some 6LoWPAN frame > >> with context based address compression (the source address). See also [1]. > > Yes for [0] > > > >> > >> Your options are: > >> > >> - That the other board use stateless (means SAC = 0, see [1]) address > >> compression. > > How may I check? > > They use both the same settings, they are based on the same source code. > SAC bit is set. Yes SAC bit means context based address compression and we don't support it. We should support it, that's what rfc6282 said. But we don't have support for that now. :-) What do you mean with "they are based on the same source code"? It's a linux<->linux communication? Then SAC bit should not set, if you try to communicate with another 802.15.4 6LoWPAN stack then you need to implement SAC/DAC handling or turn it off on the other side. > > > >> > >> - Implement context based address compression, there was recently a > >> RFC patch series which implemented it. This maybe depends also for > >> handling 6CO field correctly. > > Could you provide a link? Is that ported to Bluetooth-next branch or Linux-4.1? > > http://www.spinics.net/lists/linux-wpan/msg02613.html It's based on bluetooth-next like all others patches which you like to bring into mainline state. Read [0]. - Alex [0] http://wpan.cakelab.org/#_developing -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
