* [Bluez-devel] DUND features
@ 2004-03-29 11:42 Edouard Lafargue
2004-03-29 11:56 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Edouard Lafargue @ 2004-03-29 11:42 UTC (permalink / raw)
To: BlueZ Mailing List
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1164 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-devel] DUND features
2004-03-29 11:42 [Bluez-devel] DUND features Edouard Lafargue
@ 2004-03-29 11:56 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-03-29 11:56 UTC (permalink / raw)
To: Edouard Lafargue; +Cc: BlueZ Mailing List
Hi Edouard,
> 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...
there is a difference between the DUN and LAN profile on the server side
even if our program for LAN access using PPP is called dund. For the DUN
profile you need a modem emulation (the AT command parser) on the server
side.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-03-29 11:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-29 11:42 [Bluez-devel] DUND features Edouard Lafargue
2004-03-29 11:56 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox