Bluez has two parts: one for kernel and another for user. We added a routing layer in the kernel part, so whenever a package is received the node will route accordingly. To achieve this, routing information needs to be send when a connection is setup. So the user modules of Bluez also needs to be extended.

Routing information is stored in bnep sessions. Every session is corresponding to one slave node. One of our major consideration is to make it easy for different routing methods to be used. The routing information can be anything depend on different methods. We provided a solution, but much more work still needs to be done.

(More to come ...)