Thanks
Drew
drew wrote:
Heh, just done all that on a Sony Clie. Quick tips:
On linux side:
Use kernel 2.4.21 or above,
Install the BlueZ packages (http://bluez.sourceforge.net/, RTFM),
Install the latest pilot-link (http://www.pilot-link.org/),
You'll need to make the /dev/rfcomm? nodes (RTF-bluez-M again)
Create a file /etc/ppp/peers/dun with the following
noauth
local
debug
115200
noipdefault
noipx
idle 0
ms-dns <DNS-SERVER-IP>
netmask 255.255.255.0
Create a file /etc/ppp/options.rfcomm0
<PCS_IP_ADDRESS>:<PALMS_IP_ADDRESS>
Finally run the following (as root)
hcid -f /etc/bluetooth/hcid.conf
sdpd
dund --listen --channel 1 call dun
pi-csd -H <PC_NAME> -a <PC_IP_ADDRESS> -n 255.255.255.0 &
On Palm side:
In prefs/Bluetooth add you're PC to the trusted device list (Pass key is
found in /etc/bluetooth/pin default is "BlueZ")
In prefs/Connection create a new entry (Connect to: PC, Via: Bluetooth,
Device $YOUR_PC)
In prefs/Network create a new service (Username/password same as your normal
linux login, Connection to whatever you created in the previous step, no
need to change details)
Tap 'Connect', if all's well you should see the palm connecting (check the
end of /var/log/messages to see the ppp log) tap 'Disconnect'.
In Hotsync:
Change the ModemSync pref to Network,
Fill in your PC details in Primary PC setup (as setup on the pi-csd line
above)
Change the type hotsync to Modem and select the Network you created above.
In you user account on the linux box, type "pilot-xfer -p net: -l"
Tap the on screen hotsync button and you should see it connecting like
before then on the linux box you should see a list of stuff appearing from
the pilot-xfer program.
You're done! Do whatever syncing you need using pilot-link software via the
'net:' port (as opposed to /dev/pilot or whatever). Networking should also
work whilst you're connected (HTTP, telnet, SSH, etc), you may need to
fiddle with firewalling/routing issues first.
Of course YMMV, but thats how I did it :)
Blumf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/KNtkMid3IcxolsoRArfIAJ9Fhbt0UkPEgzECxx1Z/+STWXxOQwCfa14K
oyrCtjJUegGb4lm8XXrgfVo=
=lDV4
-----END PGP SIGNATURE-----
Drew
Drew wrote:
> After posting I hit up google and found a couple good pages, which were
> darn close to what you posted! I appreciate the feedback. I've got
> everything installed and setup and the Palm can see the PC and vice versa
> but the PDA can't login to the machine for some reason, It lets me try to
> setup the PC as a trusted device and then bombs out with "unable to
> connect to PC" ... and nothing shows up in syslog or messages.. I'm sure
> its just something resulting from PEBCAK syndrome.. waiting to get off
> work and go mess around with it when I get home =-)
Can the PC see the palm?
Took me about half a day fiddling around. The hardest part was getting
hotsync to work as nothing mentioned the "pi-csd" and "net:" stuff until I
started digging through some mailing lists/forums. Documentation needs
updating on the pilot-link suite me-thinks.
Thing I've learned this week:
A little about bluetooth and BlueZ
A bit more about the pilot-link suite
A fair bit about the ppp system (I think I'm getting a hang of it now)
The Zire 71 is called that because Palm marketing did a focus group and
thats what they liked :)
Blumf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/KQuuMid3IcxolsoRAvGSAJ0UdVX9gymcvalJ8+4kjRT4kOuv8ACePAWq
cuO8qCrnuaidoer6ddoIo5Y=
=ZQ+b
-----END PGP SIGNATURE-----
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Drew wrote:
>
>> After posting I hit up google and found a couple good pages, which were
>> darn close to what you posted! I appreciate the feedback. I've got
>> everything installed and setup and the Palm can see the PC and vice versa
>> but the PDA can't login to the machine for some reason, It lets me try to
>> setup the PC as a trusted device and then bombs out with "unable to
>> connect to PC" ... and nothing shows up in syslog or messages.. I'm sure
>> its just something resulting from PEBCAK syndrome.. waiting to get off
>> work and go mess around with it when I get home =-)
>
> Can the PC see the palm?
>
> Took me about half a day fiddling around. The hardest part was getting
> hotsync to work as nothing mentioned the "pi-csd" and "net:" stuff until I
> started digging through some mailing lists/forums. Documentation needs
> updating on the pilot-link suite me-thinks.
>
> Thing I've learned this week:
> A little about bluetooth and BlueZ
> A bit more about the pilot-link suite
> A fair bit about the ppp system (I think I'm getting a hang of it now)
> The Zire 71 is called that because Palm marketing did a focus group and
> thats what they liked :)
>
> Blumf
>
Well what I thought I might be doing wrong (not calling hcid with the -f
switch) wasn't correct as I'm still unable to add the PC as a trusted
device :( It can see the PC, the PC can see it, but it can't attach, it
never prompts for a password or anything of the sort. I'm going to dig
around and see what I can find, chances are its permissions or something
else silly.
Turns out it was the kernel bluetooth drivers ;) I found out after this
post that it "could" see the palm and vice versa but not communicate
correctly which led me to believe it was a module issue. So I downloaded
and built the newest bluez-kernel modules and boom it works =) too bad I
had to dump a bunch of ish in the testing process from the palm =( But I'm
sure I can get it back heh.. it kept seeing "laptop" at first as a trusted
device so to ensure the proper config I flatlined the palm *I know its an
old windows habit heh* I'm gonna do a small write up for getting it setup
under Slackware.. hopefully it'll be of some use to someone someday ;)
Drew
drew wrote:
> But I'm
> sure I can get it back heh.. it kept seeing "laptop" at first as a trusted
> device so to ensure the proper config I flatlined the palm *I know its an
> old windows habit heh*
Yeah the palms name cache is a pain, seems to hold back even when you select
the "disable name cache" option on the prefs/bluetooth menu.
> I'm gonna do a small write up for getting it setup
> under Slackware.. hopefully it'll be of some use to someone someday ;)
Good, I'm too lazy to write docs myself :), but I'll give yours a quick once
over and make a few suggestions if you want.
Blumf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/KimoMid3IcxolsoRAmsvAJ9l/KBfC+7IkjpIe6QEfcGnk36LcwCgje6f
XkkZ3PugaPZqrfWtXeyTJ40=
=1o59
-----END PGP SIGNATURE-----
Ok here's the last booger I'm fighting.
from /var/log/messages
Aug 1 16:52:54 aristotle pppd[4446]: pppd 2.4.1 started by root, uid 0
Aug 1 16:52:54 aristotle pppd[4446]: Using interface ppp0
Aug 1 16:52:54 aristotle pppd[4446]: Connect: ppp0 <--> /dev/pts/1
Aug 1 16:52:54 aristotle /etc/hotplug/net.agent: assuming ppp0 is already up
Aug 1 16:54:05 aristotle sudo: drew : TTY=pts/2 ; PWD=/home/drew ; USER=root ; COMMAND=/usr/bin/tail -f /var/log/syslog
Aug 1 16:54:24 aristotle rfcommd[4444]: Exit
Aug 1 16:54:24 aristotle pppd[4446]: Modem hangup
Aug 1 16:54:24 aristotle pppd[4446]: Connection terminated.
Aug 1 16:54:24 aristotle pppd[4446]: Exit.
from syslog
Aug 1 16:54:24 aristotle rfcommd[4444]: select() failed: Bad file
descriptor (9
I can't figure out which file its looking for and why it would have a bad
descriptor either.. bleh. Any ideas you might have would be greatly
appreciated.
Drew
drew wrote:
> Ok here's the last booger I'm fighting.
>
> from /var/log/messages
>
> Aug 1 16:52:54 aristotle pppd[4446]: pppd 2.4.1 started by root, uid 0
> Aug 1 16:52:54 aristotle pppd[4446]: Using interface ppp0
> Aug 1 16:52:54 aristotle pppd[4446]: Connect: ppp0 <--> /dev/pts/1
I get "ppp0 <--> /dev/rfcomm0" are you using devfs or something?
> Aug 1 16:52:54 aristotle /etc/hotplug/net.agent: assuming ppp0 is already
> up
> Aug 1 16:54:05 aristotle sudo: drew : TTY=pts/2 ; PWD=/home/drew ;
> USER=root ; COMMAND=/usr/bin/tail -f /var/log/syslog
> Aug 1 16:54:24 aristotle rfcommd[4444]: Exit
I don't get any of this, looks like the pppd system is setup wrong. Check
the; /etc/ppp/options and /etc/ppp/peers/dun files amongst others (you
should be running the dund deamon)
> from syslog
>
> Aug 1 16:54:24 aristotle rfcommd[4444]: select() failed: Bad file
> descriptor (9
May be because it's looking at the /dev/pts/1 file when it shouldn't.
> I can't figure out which file its looking for and why it would have a bad
> descriptor either.. bleh. Any ideas you might have would be greatly
> appreciated.
Do you use dial-up networking? That is, do you already have a ppp setup? I
had to fiddle about with mine because it was a bit of a mess and getting in
the way of the palm ppp session.
Blumf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/K6L4Mid3IcxolsoRAlZ/AJ9cKFfHGiEpgRUB7L8Q16HQBCXrJgCfb1eh
unHAOUqrBr0pcX/fXeQJefE=
=yni+
-----END PGP SIGNATURE-----
I don't currently use DUN ... I have an ether connection to my cable modem
and DSL connection. I've tried using dund and rfcommd -s as well, the
output from above shows what happens when I use rfcommd, it connects as
you can see and then times out, ppp0 is brought up but an interface IP is
never setup, even though its in the conf file. I know its a config
somewhere but for the life of me I can't figure out where. I've seen other
instances of google searches where it shows connecting to /dev/pts, which
I do have enabled in the kernel. Think thats something I should disable?
At this point I'm at a total loss grrr. I've tried diff configs, different
daemons ect. But nothing is coming up good for me. I'm thinking about
sending a help request to the bluez-user mailing list and seeing what
those guys have to say =)
Drew
Regards.
Jack
--
Vlad, Heisenberg & Thomas: The originators of FUD.