Hi, On Wed, 16 Sep 2020 at 13:01, Michael Richardson <mcr@xxxxxxxxxxxx> wrote: > > > Alexander Aring <alex.aring@xxxxxxxxx> wrote: > > I tried to use BT 6LoWPAN and experienced a lot of races there, sadly > > nobody is fixing it. I sent a RFC some years ago to tackle these > > issues, also that the link-layer address is reconstructed by L3 > > address and not by a ndisc lookup is very weird. I don't know if this > > is fixed or not. However it was nothing related to the new BT mesh > > stuff. > > >> for any BT device. I would love to be wrong!! > >> > >> Running BTLE mesh is something I'd really like to do. > >> My guess is that one could probably prototype this in userspace on top of > >> bluez, and then use Alex' 6lowpan tap interface. > > > I did not do the "6lowpan tap" interface, the bluetooth people did > > that and I complained about it and I never would accept this upstream. > > okay, what did you use to connect the OpenThread native-build processes together? > sorry for the late reply. This was doing L2 and above in user space, it was the Linux driver layer only... I thought it was about using 6LoWPAN until the transport layer in kernel and link-layer in user space. It also had some problems with ack handling and you will not really use Linux then, however I was always thinking about to wrap a whole library around openthread and do some daemon to using Linux then, instead running an OS on an OS. - Alex
