Date: Mon, 01 Aug 2005 11:35:48 -0500 From: Eric Anderson <anderson@centtech.com> To: "Alexandre \"Sunny\" Kovalenko" <Alex.Kovalenko@verizon.net> Cc: freebsd-bluetooth@FreeBSD.org, pav@FreeBSD.org Subject: Re: Palm sync over bluetooth? Message-ID: <42EE4F64.7040002@centtech.com> In-Reply-To: <1122863179.663.22.camel@RabbitsDen> References: <42D558B3.1060603@centtech.com> <42D55B3D.50605@savvis.net> <42D55D5D.8030604@centtech.com> <42D57496.2050102@savvis.net> <42D57C67.7020500@centtech.com> <1121287483.60360.21.camel@hood.oook.cz> <1122863179.663.22.camel@RabbitsDen>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexandre "Sunny" Kovalenko wrote:
> On Wed, 2005-07-13 at 22:44 +0200, Pav Lucistnik wrote:
>=20
>>Eric Anderson p=ED=A8e v st 13. 07. 2005 v 15:41 -0500:
>>
>>>Maksim Yevmenkin wrote:
>>>
>>>>Eric,
>>>>
>>>>
>>>>>>>Does anyone have a cookbook, or howto on this? I think I'm missin=
g=20
>>>>>>>a piece somewhere..
>>>>>>
>>>>>>
>>>>>>depends on what do you mean by "sync" :) intelligent sync, i.e=20
>>>>>>something like syncml etc. is not supported at the moment. its not =
>>>>>>really a bluetooth fault, its just no one wrote a tool (or at least=
i=20
>>>>>>do not know of any) that properly does syncml over obex over=20
>>>>>>bluetooth (or whatever palm supports). i'd like to add syncml suppo=
rt=20
>>>>>>to obexapp(1), but not have much free time at the moment.
>>>>>>
>>>>>>it should be possible to transfer files/etc. from/to palm using obe=
x=20
>>>>>>with obexapp(1) from ports (comms/obexapp).
>>>>>
>>>>>
>>>>>:) ok, I'll try to state more clearly..
>>>>>
>>>>>I'd like to get my palm t5 to sync (using the 'hotsync' in the palm)=
=20
>>>>>over bluetooth, instead of serial cable, or even usb, using jpilot (=
or=20
>>>>>pilot-xfer which jpilot uses I believe). pilot-xfer can use a seria=
l=20
>>>>>port (/dev/something) or network (net:any for ip).
>>>>>
>>>>>I was thinking that since my palm supports syncing over bluetooth=20
>>>>>(uses it like a serial port), I should be able to make my FreeBSD bo=
x=20
>>>>>connect the bluetooth to a pseudo tty device, which I could then hav=
e=20
>>>>>pilot-xfer use. Does this seem reasonable?
>>>>
>>>>
>>>>man rfcomm_sppd(1)
>>>
>>> From the man page, I was under the impression that would allow me to =
do=20
>>>the opposite. For instance, connect to another computer's serial devi=
ce=20
>>>over bluetooth, instead of the palm connecting to the computer.
>>
>>That's exactly how it is with serial and USB - computer connects to
>>Palm, then you start Hotsync application on Palm.
>>
>>
>=20
> I do mine slightly roundabout way -- using network sync. Setup is as
> follows:
>=20
> -- working bluetooth hardware ;) in my case D-Link DBT-120
> -- load USB stack + ng_ubt
> -- optionally (?) configure /etc/bluetooth/hosts
> -- rc.bluetooth start ubt0
> -- configure /etc/bluetooth/hcsecd.conf with proper PIN and start hcsec=
d
> -- start sdpd
> -- start rfcomm_pppd -d -s -C 1 -l bluetooth
> -- in /etc/ppp/pppd.conf
> bluetooth:
> set dial "\"\" READY GO"
> set ifaddr 192.168.1.1 192.168.1.2
> disable chap
> disable deflate
> disable mppe
> disable pred1
> disable shortseq
> disable vjcomp
> disable ipv6cp
> set timeout 0
> set lqrperiod 10
> enable lqr
> accept lqr
> # Do not use PPP authentication. Assume that
> # Bluetooth connection was authenticated already
> disable pap
> deny pap
> disable chap
> deny chap
>=20
> -- start pi-csd for network sync=20
> nohup /usr/local/bin/pi-csd -q -H <your host here> -a 192.168.1.1 -n
> 255.255.255.0 &
>=20
> Only quirky thing there is "dial" line in ppp configuration -- I use it=
> on USB since it seems that some characters are being dropped between
> ucom being created and devd starting necessary application, so I kept
> it here for consistency as well.
>=20
> You will have to configure your Palm for network sync (provided that it=
> knows how ;) and set your target computer (not necessarily one you have=
> bluetooth on). This is pretty straightforward on my Clie T615C.
>=20
> PILOTPORT has to be set to "net:any", same setting could be used in
> jPilot. I have not had much luck with Evolution, but that might have
> been due to the lack of motivation.
>=20
> If you need more detail, just ask. Any suggestions on improving this
> setup is more then welcome.
Thanks! I've done the above steps, and here's what I see:
After starting the rfcomm_pppd program, I see a tun0 interface via ifconf=
ig:
tun0: flags=3D8010<POINTOPOINT,MULTICAST> mtu 1500
Running the pi-csd tool (which I'm not sure what that is supposed to do, =
really) seems to run, but I don't see any output or anything, so I'm not =
certain if it is doing the 'right thing'.
Now, I set up my palm like so:
Created new Connection, setting "Connect to" to "Local Network", and=20
"Via" set to "Bluetooth" with <my-bluetooth-hostname> in the "Device"=20
box. I have my Palm set for "Local" sync (not "Modem").
When I hit the sync button, I don't see the tun0 device get an IP (from=20
ppp), nor do I see a pid associated with the tun0 device. On my palm,=20
nearly immediately I get this message:
"Unable to initiate HotSync operation because the port is in use by=20
another application."
Now, if I kill rfcomm_pppd, and restart with the addition of the -S=20
command line option, and attempt the same sync, I get a pid attached to=20
tun0, and tun0 is now 'UP':
tun0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
Opened by PID 11613
but it never gets the IP address (set in the ppp conf), and the palm=20
sits for some time (a minute or two) before finally giving up with: "The =
connection between your device and the desktop could not be established. =
Please check your setup and try again." at which point my tun0 goes=20
back to it's normal state and the ppp process disappears.
Any ideas what I may be missing?
Thanks for the help so far!
Eric
--=20
------------------------------------------------------------------------
Eric Anderson Sr. Systems Administrator Centaur Technology
Anything that works is better than anything that doesn't.
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42EE4F64.7040002>