 |
 |
 |
|
 |
You are not logged in.
took me two solid nights to figure it out.
first problem i had, was not being able to pair from my phone. "discovto 0" added to device section of hcid.conf, and i could sucessfully pair. i installed wvdial. changed alot in wvdial.conf. then it worked! but it disconnected after a minute. this is some problem with echo response. edit etc/ppp/options. change the value of lcp-echo-interval and lcp-echo-failure to 0. start connection with "wvdial". works like a charm. now i can work on putting my dongle inside. "wow, there is no way to not make that sound dirty"
wvdial.conf:
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
Baud = 460800
New PPPD = yes
Modem = /dev/rfcomm0
ISDN = 0
Phone = <#777>
Password = <>
Username = <>
Stupid Mode = 1
hcid.conf:
options {
autoinit yes;
security auto;
pairing multi;
passkey "2222";
}
device {
discovto 0
name "%h-%d";
class 0x3e0100;
iscan enable; pscan enable;
lm accept;
lp rswitch,hold,sniff,park;
}
Offline
This looks very promising, but could you please post a step by step on setting up bluetooth, or at least post a link to the bluetooth setup method you used to get this working?
Offline
the general method is outlined here:
http://www.3eportal.com/index.php?optio … p;Itemid=9
you should be able to do it with only default installed software. i, however found wvdial easy to install, and easy to configure. note that that guide, as well as the 8 page thread in this forum are focused on gprs. some things are different with modem commands, etc. i find this config to work great with my sprint pcs phone.
just get started, and see how far you get. learn the tools. don't be lazy and go to windows. windows killed my dog, and slept with my wife.
Offline
Did it!!!
A little of this and that and a few long nights of frustration, but I finally got my Palm Centro and EEE to speak to each other and have been on DUN for about 20 minutes so far. Don't ask how I finally did it cause I can't possibly write a WIKI, but trial and error finally paid off. I'm now going to purchase the Mobile Stream application. Well worth it!
Offline
glad to hear that! there is really no one method that will work for everyone. linux is like this. you spend 2 nights cursing at it, but if you don't give up, you can figure most things out. ... and it's quite satisfying when you do. i also forgot all what i did to make it work. this post was for my own reference as much as anyone else. write down what little i remember before i forget it all.
Offline
One thing I haven't yet figured out is how to gracefully exit the DUN connection. I've tried a number of methods, including quittting the application (USB Modem in Bluetooth mode) on my Centro, unplugging the Bluetooth dongle..what happens is I get a message "Segmentation fault". After that, I cant start wvdial again (I get "Cannot open /dev/rfcomm0: No such device or address") unless I restart the EEE.
Offline
It would be awesome if someone with experience could make a script/graphical program to do all this (pair/unpair phone, dial desired number, etc...). Or at least, if there already is something out there, post easy to follow directions to get it working. As a person coming from Windows who really doesn't know...is this a pie-in-the-sky wish for me to have? I would love to be able to use the stock Xandros on my 4g eee, but one of the reasons I bought it was to be able to use BT DUN. For now I'm stuck with nLite'd Windows XP Pro to make this happen.
Is there nothing available for Linux like Windows' built in bluetooth interface? (Menus, buttons, easy questions for pairing, etc...)
Offline
i usually have a few konsole windows open on one side of my compiz cube. in one, i type "sudo wvdial". to disconnect, i go to that konsole and press <ctrl>+<c>. wvdial exits gracefully, will say disconnected. the bluetooth can be unplugged / replugged, and wvdial will connect again smoothly.
one problem i find is closing the lid of eee causes standby mode. if you are connected, you will get these errors when you try to re-establish connection. same like as pulling out dongle while connected.
there are some programs that try to do the configurations in a "windows like way".
3egprs: http://www.3eportal.com/index.php?optio … p;Itemid=1
did not work for me.
there are some other gui bluetooth front ends. i have not tried them.
you can definately make it work. try one of the guides like post 3 that uses only pre-installed software. see how far you get. when you hit a snag, post the problem here.
Offline
Thanks - ctrl+c works perfectly
Offline
Does anyone know whether this will work with any Sprint phone that has bluetooth or only certain phones. Now that Sprint has the $99 all you can eat voice, texting, and data plan, I'm thinking about signing up, but I'm wondering how carefully I need to select my phone in order to pair it with my laptop.
Thanks
Offline
First of all, these forums/wiki are awesome and very helpful. Anyway, this is how I got BT (Bluetooth) DUN (Dial-up networking) working with my new EEE PC 8G and Sprint Palm Centro running USB Modem (http://www.mobile-stream.com/usbmodem.html).
(Some of tThese steps are also in the Wiki on adding BT devices)
1. Plug in BT adapter
2. run command "dmesg" and look for some lines that have "Bluetooth" in them. If they are there, then your device was most likely discovered.
3. run command "sudo hciconfig" and check what device your adapter got discovered as (most likely hci0)
4. to activate your adapter, run command "sudo hciconfig <device> up" (so I ran "sudo hciconfig hci0 up")
5. (backup first) edit your /etc/bluetooth/hcid.conf file and add options "security auto", "passkey <whatever passkey you want>", and under device, add "discovto 0" after "lm accept". This is what mine looks like (minus the comments):
options {
autoinit yes;
security auto;
pairing multi;
passkey "1234";
}
device {
name "%h-%d";
class 0x3e0100;
iscan enable; pscan enable;
lm accept;
discovto 0;
lp rswitch,hold,sniff,park;
}
6. Get the address of your phone using "sudo hcitool scan"
7. (backup first) edit your /etc/bluetooth/rfcomm.conf file and add your settings. Mine looks like this (minus the comments):
rfcomm0 {
bind yes;
device 00:07:E0:EC:09:CF;
channel 3;
comment "Sprint DUN Connection";
}
8. (assuming you have the extra repositories added) "sudo apt-get install wvdial"
9. edit your /etc/wvdial.conf file with your settings. Mine looks like this:
Modem = /dev/rfcomm0
Phone = <#777>
Username = <insert your user>
Password = <insert your password>
New PPPD = yes
10. "sudo wvdial" and you should be good
P.S. go here and scroll down to the update about fixing the timeout thing: http://stuff.salrok.com/?p=5
Offline
OK, this is annoying.
I've got everything set up basically following the steps given here.
I've created a script that does:
hciconfig hci0 up rfcomm bind /dev/rfcomm0 /etc/init.d/dbus restart /etc/init.d/bluetooth restart
I've successfully paired the Eee and the phone (a Sprint Blackberry 8330, fwiw).
I run the bluetooth initialization script above via sudo, and then do a sudo wvdial.
wvdial does its thing, ending with
--> Using interface ppp0 --> local IP address 70.0.xxx.xxx --> remote IP address 68.28.xxx.xxx --> primary DNS address 68.28.xxx.xxx --> secondary DNS address 68.28.xxx.xxx
If I then open a second terminal, I can do a "sudo ifconfig" and I see entries for ppp0 and lo.
In short, everything looks normal, but nothing goes over the network.
If I try to ping an IP address, I get "connect: network is unreachable"; if I try to ping a hostname, I get "ping: unknown host www.google.com".
Obviously, I'm missing something here. Any suggestions?
Offline
Never mind. Solved it.
I had manually edited resolv.conf and -- contrary to the warning in the file -- it had not been overwritten. The result was that even with the BT/Sprint connection up, it was still trying to use my home DNS server, which is not accessible outside my network.
So, warning: If you hard-code your DNS in resolv.conf, you need to clear it out before launching wvdial.
S.
Offline
