Bugzilla Bug 39464

At the moment /etc/init.d/bluetooth will start and stop hcid, sdpd and
hciattach. 
One bluez-daemon is missing: pand

Why not add handling of pand to the bluetooth script?


Reproducible: Always
Steps to Reproduce:

Actual Results:  
I have to start pand manually, write my own pand start script or have to patch
the  bluetooth script on my own.

Expected Results:  
The bluetooth script should be handle pand like all the other bluez daemons.

A little config file (e.g. in /etc/bluetooth or /etc/conf.d) is needed to tell
the script in which mode (none = only client mode, NAP oder GN) the pand have
to
be started.

Created an attachment (id=24657) [details]
Updated bluetooth init.d script and associated conf.d

I've updated the bluetooth config script to start the dund server and set up
appropriate ip forwarding. Options to turn this off can be found in the
associated conf.d file.

This version should replace the current bluetooth init.d script.

This does not yet start the pand daemon but it does start everything else. I
will include pand once I find the appropriate arguments and can test it.

My configuration for pan is very easy. I added only the following line to
/etc/init.d/bluetooth

start-stop-daemon --start --quiet --exec /usr/bin/pand -- -s -r GN

Ip configuration is done by another script: /etc/init.d/net.bnep0 (a copy of
the net.eth0 script) and firewall configuration is done by /etc/init/iptables.

I think that the user can make enhanced configurations (e.g. bridged ethernet)
in /etc/init.d/net.bnep0, too.

So, in my opinion, /etc/init.d/bluetooth must only look if pand exist, if the
user wants to start pand and if the user wants to use the GN or NAP role.

Michael

Created an attachment (id=24719) [details]
Second update of bluetooth init.d and conf.d files

This bluetooth startup script now optionally starts dund and pand.

dund options and optional forwarding is configurable in the
/etc/conf.d/bluetooth file.

pand startup option in /etc/conf.d/bluetooth file.

This update replaces previous files.

not kernel related

don't actually have any bluetooth devices myself that are capable of pand ..
but will look into this.

hi i recently came across the sames issues
please have a look at my solution bug #60304

*** This bug has been marked as a duplicate of 60304 ***