Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bt-network interface naming #17

Open
oliverkurth opened this issue Jun 13, 2017 · 1 comment
Open

bt-network interface naming #17

oliverkurth opened this issue Jun 13, 2017 · 1 comment

Comments

@oliverkurth
Copy link

I want to use bt-network in both server and client mode. Is there a way to create the interfaces with another name than one starting with 'bnep'? For example, in server mode, the bridge interfaces for its clients will be named 'bnep0', 'bnep1' and so on. But if bt-network in client mode is started later, this will make the name for its interface unpredictable. So I would like to use different basenames for the interfaces, one for client mode and another for server mode. I observed that even if the bridge name for server mode is set to 'nap', the client interfaces will get names starting with 'bnep0'.

@oliverkurth
Copy link
Author

I could answer my own question - the answer is no, there is no way to configure the interface name. I looked at the sources in https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/profiles/network/server.c and https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/profiles/network/connection.c and it's hard coded in both as
#define BNEP_INTERFACE "bnep%d"
The only way to change it is by changing the bluez source.

I also investigated using udev to change the interface name, but I found no way to tell the client interface apart from the added interfaces to the bridge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant