On 07/28/2016 12:19 AM, Abhishek Sharma wrote: > > > Hi Anupam > > >> Case 1: ED1 (BT) <--> GW1(IP\BT\NFC...) <---> ED2 (BT ) > > Are you able to replicate this scenario with commercially available devices ? > > As far as i know its piconet only with GW1 getting role of master and ED1 can > scan as well as connect with ED2. > > >> Case 2: ED1 (BT) <--> GW1(IP\BT\NFC...) <---> GW2(IP\BT\NFC...) <---> ED2 >> (BT) > > What is the connectivity between GW1 and GW2 ? > > If its anything other than BT then RM will be able to route packets. > > If its BT then ED1 shall be able to directly connect with ED2. > > If you are referring to a scenario when there are too many BT devices and > hardware is overwhelmed, I am not sure even RM can do anything to help. > > RM implements application layer routing, which comes into picture where l2 / > l3 routing is not supported. > > >> I think BTLE over 6lowpan can help solve the above issue as it will >> eventually boil down to IP routing that is already handled by IP protocol in >> Linux. > > Correct.
would running a Thread mesh help with this?
