Date: Fri, 26 Aug 2005 15:17:16 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Bakul Shah <bakul@bitblocks.com> Cc: freebsd-bluetooth@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: sprintpcs treo 650 & blutooth & dialup networking Message-ID: <bb4a86c705082615172dba5c3d@mail.gmail.com> In-Reply-To: <200508262157.j7QLvDQi054574@gate.bitblocks.com> References: <bb4a86c7050826141449e646ad@mail.gmail.com> <200508262157.j7QLvDQi054574@gate.bitblocks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > i'm not exactly sure how this work in your case (never had a cdma > > phone :) you need to have some sort of wireless internet access plan > > activated on your phone. you will probably use 1xRTT (instead of > > gprs) on cdma network. you also need to make sure that wireless > > internet access plan you have allows you to use your treo as wireless > > modem. in other words you need to make sure that access point you are > > connecting to talk ppp and ip and not wap/whatever. then you will need > > to use something called "bluetooth dun profile" on treo (and > > rfcomm_pppd(8) on pc). > > > > it seems earlier versions of treo shipped to sprint pcs have bluetooth > > dun profile disabled. you need to check with sprint and make sure your > > treo supports it - you may need firmware upgrade. >=20 > I have the firmware upgrade that does DUN. >=20 > # sdpcontrol -a mytreo search DUN >=20 > Record Handle: 0x00010001 > Service Class ID List: > Dial-Up Networking (0x1103) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 1 looks fine to me. > Here is what I use to connect to the net via the treo >=20 > rfcomm_pppd -a mytreo -c -C dun -d -l rfcomm-dialup >=20 > [mytreo has an entry in /etc/bluetooth/hosts] >=20 > My ppp.conf script is pretty much the same as yours (except > that right now I log everything but timer events). From > ppp.log I see that the phone does not respond to the initial > AT<cr> with OK as it should. So it seems the treo never > really sees any communicaiton. hmmm... strange... what freebsd version are you using (uname -a)? did you try to use rfcomm_sppd(1)? something like # rfcomm_sppd -a mytreo -c 1 -t /dev/ttyp1 then in another window=20 # cu -l /dev/ttyp1 and try to type "AT" to see if the phone returns "OK" back? note: you might need to try different tty number to find free one, i.e. /dev/ttyp2, /dev/ttyp3 etc. tty name must match in both commands. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c705082615172dba5c3d>