Date: Mon, 01 Aug 2005 13:28:41 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-bluetooth@FreeBSD.org, pav@FreeBSD.org Subject: Re: Palm sync over bluetooth? Message-ID: <42EE85F9.50008@savvis.net> In-Reply-To: <42EE7C76.2090904@centtech.com> 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> <42EE4F64.7040002@centtech.com> <42EE6438.9080209@savvis.net> <42EE7C76.2090904@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric,
[...]
>>>>> That's exactly how it is with serial and USB - computer connects to
>>>>> Palm, then you start Hotsync application on Palm.
>>
>> does rfcomm_sppd(1) work for you?
>
> Well, not really. rfcomm_sppd requires that the palm be the server of
> the serial port service (if I understand correctly, and I may not!),
> which means I would have to hit the sync button, then quickly start
> rfcomm_sppd with the correct channel number (which I don't know), and
> then start my sync right after that. I have not been able to get this
> trickery to work. Even so, if I did get it working, I'm not sure this
> is the best solution.
what palm model do you have? is it possible to simple turn on bluetooth
without doing anything on palm? if so, then could you please run
% sdpcontrol -a palm_bd_addr browse
and/or
% sdpcontrol -a palm_bd_addr search SP
if you palm has serial port (SP) service then you should be able to just
connect to it without hitting sync button first.
it is also trivial to extend rfcomm_sppd(1) to make it work as server.
you could use either nmdm(4) or pty(4) to emulate serial port. i could
put it on my to do list, but i need to know how palm expects this to
work (sorry never owned a palm :)
[...]
>>> Any ideas what I may be missing?
>>
>> 1) check 'default' section in your /etc/ppp/ppp.conf and make sure it
>> only contains commands that applied to _all_ other sections in your
>> ppp.conf file. i always have 'default' section empty and move all the
>> commands to the appropriate section.
>
> I've removed everything in the default section, with no changes (I
> barely had anything in it).
good. do you have a dropdown box on your palm that specifies remote
system access type, i.e. something like PPP (unix), RAS (microsoft) or
something like this? i recall that earlier versions of palm had such
dropdown box. you need to use "PPP (unix)".
you might want to try to add something like
enable force-scripts
set dial "CLIENT CLIENTSERVER"
to your bluetooth section in /etc/ppp/ppp.conf. this should make ppp
compatible with microsoft RAS style clients :)
>> 2) add 'set log all' to the 'bluetooth' section. then try again. now
>> /var/log/ppp.log should have tons of information that will tell you
>> what is going all.
>
> Done - now I have lots more logged info I don't understand. :)
could you post it somewhere?
>> 3) since you are _not_ using ppp authentication make sure your palm
>> does not require one
>
> Pretty sure it doesn't - no place to put in the info, and I connect up
> to my cellphone over bluetooth for surfing, etc using a similar method.
do you mean you connect your palm to your cellphone?
> Any more ideas? What should I be looking for in the ppp logs? I did
> see this though:
>
> Aug 1 14:38:02 neutrino ppp[17496]: tun0: Phase: deflink: closed ->
> opening
> Aug 1 14:38:02 neutrino ppp[17496]: tun0: Debug: deflink: Link is
> SOCK_STREAM, but not inet
> Aug 1 14:38:02 neutrino ppp[17496]: tun0: Debug: deflink: stdin is
> unidentified
those are fine (i think). i'd like to see full log. i suspect there is
something is wrong at ppp level. you also might want to run hcidump
(from ports comms/hcidump) as root
# hcidump -w palm.dump -- it will block
then try to connect. then terminate hcidump with ^c and send me the
palm.dump file. also what is the freebsd version?
thanks,
max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42EE85F9.50008>