* [Bluez-devel] WindowsCE and DUND
@ 2004-01-22 11:48 Ronny Bremer
2004-01-22 12:24 ` Marcel Holtmann
0 siblings, 1 reply; 2+ messages in thread
From: Ronny Bremer @ 2004-01-22 11:48 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]
Hi folks,
I am using RedHat Fedora Core 1 with the latest updates. I remember from earlier on, that in order to provide connectivity to a WindowsCE device I need to run
dund --listen --msdun call synce-device
which will register with SDP automatically.
2 questions
1) I created a section in /etc/bluetooth/rfcommd.conf called rfcomm1, pointing to channel 1. If I then use
dund --listen --msdun -P rfcomm1 call synce-device
will it always listen on channel 1 so once configured devices are connecting to the right channel?
2) In order to sync you need to create an ActiveSync session. This is searching for SP (serial port) service on the linux host, but dund registers LAN service only. Is there any option to have dund register both LAN and SP? Or am I mistaken? And why does calling
sdptool add SP
works afterwards, how does it route the request for the SP to dund?
Sorry, but I haven't found the right answers to that one.
Ronny
[-- Attachment #1.2.1: Type: text/html, Size: 1003 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 2705 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bluez-devel] WindowsCE and DUND
2004-01-22 11:48 [Bluez-devel] WindowsCE and DUND Ronny Bremer
@ 2004-01-22 12:24 ` Marcel Holtmann
0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-01-22 12:24 UTC (permalink / raw)
To: Ronny Bremer; +Cc: BlueZ Mailing List
Hi Ronny,
> I am using RedHat Fedora Core 1 with the latest updates. I remember
> from earlier on, that in order to provide connectivity to a WindowsCE
> device I need to run
> dund --listen --msdun call synce-device
>
> which will register with SDP automatically.
>
> 2 questions
>
> 1) I created a section in /etc/bluetooth/rfcommd.conf called rfcomm1,
> pointing to channel 1. If I then use
> dund --listen --msdun -P rfcomm1 call synce-device
> will it always listen on channel 1 so once configured devices are
> connecting to the right channel?
the config file rfcomm.conf has nothing to do with dund. Both are
different applications and also an outgoing connection to channel 1 and
an incoming connection to channel 1 results in two different DLCI's.
And the argument for -P is the only channel number.
> 2) In order to sync you need to create an ActiveSync session. This is
> searching for SP (serial port) service on the linux host, but dund
> registers LAN service only. Is there any option to have dund register
> both LAN and SP? Or am I mistaken? And why does calling
> sdptool add SP
> works afterwards, how does it route the request for the SP to dund?
Go ahead and modify the dund application to take another argument like
--spp, so it will add a serial port record instead of a LAN service. You
don't need both. If you had done this send me a patch.
SDP is like DNS only a lookup database. You can also do anything without
it, if you know where and how to connect.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-22 12:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-22 11:48 [Bluez-devel] WindowsCE and DUND Ronny Bremer
2004-01-22 12:24 ` Marcel Holtmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox