Hi,

In good old days the only action needed to enable DUT mode was "hcitool 
cmd 0x06 0x0003" or similar. However now after having full connection 
tracking also for incoming connection this doesn't work anymore.

At least R&S tester does only ACL link to the device and therefore BlueZ 
disconnects it after 10 secs. Connection tracking needs to be disabled 
somehow. I prepared one proposal how to deal with it. The disable DUT 
mode command is missing because the Spec says the DUT mode is disabled 
by resetting the chip. Thus it can be done with "hciconfig hci0 reset" 
command.

With this patch against bluetooth-2.6 tree the DUT mode is enabled by 
echoing "enabled\n" to new sysfs entry. Maybe some other interface 
should be used instead?

Any comments?

-- 
Ville