Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote:
> And why would we want more than one one net_dev per hci_dev, the
> rfc7668 only talks about star topology:
> https://tools.ietf.org/html/rfc7668#section-2.2
> Bluetooth currently don't have support for a mesh topology, and anyway
> I don't think the userspace would need to be involved in the selection
> of the netdev since this is beyond the Bluetooth interface. In PAN for
> example we end up doing one netdev per connection and the which the
> userspace managing using a bridge.
BTLE 4.2 moves quite far to supporting a mesh, but doesn't yet get there.
I'm told that it will come. BTLE 4.2 does support switching to which
star one belongs quickly enough that one could actually route, but it's
probably not practical yet.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@xxxxxxxxxxxx http://www.sandelman.ca/ | ruby on rails [
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
