bt0 interface not showing before connection

[Matt]

I have been able to follow the instructions in the nrf5 iot sdk to connect my nrf52 dk to a raspberry pi, however I am unsure why a connection must first be made before I am able to see the bt0 interface on ifconfig.

For example, on booting my pi, I follow the usual commands to initiate bluetooth 6lowpan, then, when I type the command ifconfig -a, I do not see bt0. However after searching with hcitool lescan and connecting to my dev kit, I am able to see bt0.

Is there a way to get the bt0 interface to display without having to make a connection?

Thanks.

[Stian Røed Hafskjold]

Hi, this is just how the bluez driver in linux works. It does not set up the interface until after a connection is made. I guess it's because it's different interfaces based on the type of link (bt0, bnep0..), so then you would have several interfaces going up when you plugged in the dongle, so they used a more on demand approach, so the interface does not go up until you actually are using it.

I guess you will have to ask the bluez developers (IRC). Or maybe you want to request a change. http://www.bluez.org/contact/