I have read the Bluetooth DUN specifications, and it appears that devices supporting DUN are supposed to implement a set of AT-compatible commands in order to fully support this profile: so far it does not seem that DUND is supporting anything in particular.

   When using Palm-compatible devices as clients, this is not a problem because it is possible to configure them to start PPP link negotiation independently from link establishment. But in the case of Windows clients, it creates problems because the Windows computer sends AT commands and tries to dial a number to connect to the Linux server offering DUN...

   Are there plans to correct this at the moment? Alternatively, are there known workarounds to enable windows-based clients to connect to Linux servers running dund ? Apparently the option called "msdun" is not enough...

Regards,

Edouard