[Bug 224389] Re: bluetoothd-service-network fails to bring up the server side bnep interface after reconnection

[Valmantas Palikša]

** Summary changed:

- bluetoothd-service-network fails to execute ifup scripts from network.conf after repeated connection attempts
+ bluetoothd-service-network fails to bring up the server side bnep interface after reconnection

** Description changed:

  Binary package hint: bluez-utils
  
- After connecting to a server once, the relevent scripts in network.conf
- are executed, and pan* and bnep* interfaces come up, but when you disconnect and
- reconnect the second time, neither the script gets executed, nor the
- interface comes up and this makes the connection unusable. (You would have to manually bring it up with "ifconfig bnep0 up" )
- 
- Also PANU role script does not get executed, ever, on incoming
- connections, fixed in patch.
- 
- Example:
- i have /etc/bluetooth/network.conf
- 
- [General]
- 
- [PANU Role]
- Script=/usr/bin/my-ifup
- 
- [GN Role]
- Script=/usr/bin/my-ifup
- 
- [NAP Role]
- Script=/usr/bin/my-ifup
- 
- Connection 1 ( server pan0 (GN) )
-  my-ifup gets executed with pan0 argument
- 
- Disconnect / Connect 2 ( server pan0 (GN) )
-  No execution
- 
- Correct behaviour:
- Connection 1 ( server pan0 (GN) )
-  my-ifup gets executed with pan0 argument
-  my-ifup gets executed with bnep0 argument
- 
- Disconnect / Connect 2 ( server pan0 (GN) )
-  my-ifup gets executed with bnep0 argument
- 
- Disconnect / Connect 3 ( server pan0 (GN) )
-  my-ifup gets executed with bnep0 argument
+ After connecting to a server once, bnep0 is created and brought up,
+ however after disconnecting, bnep0 disappears and after reconnecting is
+ not brought back up, which makes the connection unusable

-- 
bluetoothd-service-network fails to bring up the server side bnep interface after reconnection
https://bugs.launchpad.net/bugs/224389
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez-utils in ubuntu.