![]() |
N900 bluetooth tethering with Debian PC in 2019?
Hi,
I want to use my N900's mobile data plan on my computer(s) running Debian Buster. On Debian I use Xfce with nm-applet (network-manager-gnome), where I successfully set up a "mobile broadband connection"* with which I can use my N900 as a modem if it is connected via USB. Now I want the same thing not via USB but via Bluetooth (because wireless would be more convenient). So I successfully paired my N900 and my computer(s) with the N900 and set up a "bluetooth connection"* in nm-applet. nm-applet also finds the N900 and tries to connect to it, but fails. When it does, I see these messages in journalctl: Code:
Sep 14 09:20:34 gpd NetworkManager[667]: <info> [1568445634.2093] device (00:BD:3A:F6:C4:71): Activation: starting connection 'Vodafone Vorgabe 2' (3c8e0375-d9ff-4108-b1a0-f8634a0c99e3) Code:
fail (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:124) But two peopIe who have never done this before can establish a connection in nm-applet via bluetooth with their phones (not N900) right away. I on the other hand can reproduce the same problem on three different PCs with different Debian installations. One of them is a very vanilla Debian Xfce installation, to which I only added the bluez and bluetooth packages. So I'm beginning to think, that the problem is not actually on the Debian side, but on the N900's. I once had bluetooth tethering working with wvdial on a Debian PC some 5+ years ago, but I didn't keep my wvdial configuration and I thought, it should be easy to do with nm-applet. I'm pretty sure that nothing of relevance has changed on my N900 since then. As far as I understood, the missing rfcomm socket blueman is complaining about should be something like /dev/rfcomm* on my Debian system. I don't see such a device. Would I need that, and if so, should it somehow be created by/from/via(?) the N900? One of the users at debianforum.de, who has a working connection, says, he sees no such device either. When opening this thread, these threads were suggested to me [2][3][4][5][6], but since they're all very old, I don't know which one(s), if any, to follow. I'm running the latest kernel power on the N900 and bluetooth-dun seems to be working fine. At least I see the rfcomm instance running, that's started by it: Code:
1198 root 1556 S rfcomm -S -- listen -1 1 /usr/bin/pnatd () *) back-translated from German, so probably not the original term [1] https://debianforum.de/forum/viewtop...?f=30&t=174706 [2] http://talk.maemo.org/showthread.php?t=58570 [3] http://talk.maemo.org/showthread.php?t=90063 [4] http://talk.maemo.org/showthread.php?t=37710 [5] http://talk.maemo.org/showthread.php?t=32839 [6] http://talk.maemo.org/showthread.php?t=46140 |
Re: N900 bluetooth tethering with Debian PC in 2019?
|
Re: N900 bluetooth tethering with Debian PC in 2019?
I never used bt tethering, I always used a forwarded bt pan connection.
I got it working with devuan ascii, but laptop is at home and there are some differences compared to debian. I will give you a link how I did it in the past. However with devuan ascii it is different and I will have look and try to remember what I did. In principle you need to initiate a pan connection the rest you do with genwall. http://talk.maemo.org/showpost.php?p...5&postcount=62 Pan and modern bluez: http://blog.fraggod.net/2015/03/28/b...-bluez-5x.html |
Re: N900 bluetooth tethering with Debian PC in 2019?
Quote:
In the 2nd half pppconfig didn't make any sense to me though. Most of the ncurses dialogues didnt seem to be about what I wanted to do and after completing the wizard with largely random/default inputs I couldn't find any config file that I might have adapted manually. Quote:
I guess I wouldn't care about the details as long as it works and is half-way convenient. Quote:
Quote:
Does this mean, that by default whatever kind of "network" won't work on the N900 via bluetooth? If so, that might explain my problems. But then I don't understand why it worked years ago. |
Re: N900 bluetooth tethering with Debian PC in 2019?
Quote:
Quote:
|
Re: N900 bluetooth tethering with Debian PC in 2019?
Instead of bluetooth you can also easily use wireless tethering.
There is an app called "Qt Mobile Hotspot", which I have found to work quite reliably. Of course you want at least the WEP encryption provided. The problem is, many modern wireless devices do not support WEP, my workaround is to carry a Edimax ew-7811un around (very cheap, very little wireless dongle), plug it into any device and it will be able to use your WEP network. (Works also for the native N9 hotspot) WEP is not secure and can be hacked, but because it isn't supported anymore the risk of somebody having a compatible device, the required skills and the urge to hack your hotspot is very negligible. |
Re: N900 bluetooth tethering with Debian PC in 2019?
I don't know if it helps but my setup is atm broken (edit only for one N900). Maybe the bluetooth dbus device has changed. When I try to connect like before I getting now an audio connection.
As far as I remember: N900_1: not working cssu testing maybe other testing stuff from bt N900_2: working cssu stable some packages from cssu devel but not related Have another one with stock but not tested atm. Here my notes(which where working in march 2019 and today): Device must be paired once and should be trusted. (a note I made to the test-network script "changed Network1 to Device1" However try first without modification it is not everytime necessary) This was a hack which was needed because the N900 was identified wrong and needed packages on PC: bluetooth bluez-test-scripts bluez-tools PC as root: bluetoothctl power on agent on pairable on when you need pairing (look for mac): scan on when you need pairing (pair the device): pair 00:00:00:00:00:00 PC as user replace with your N900 mac address(if input/output error do again): cd /usr/share/doc/bluez-test-scripts/examples ./test-network 00:00:00:00:00:00:00 nap in genwall: when the bt icon get blue click fast the start button which resides on route-bt tab(settings on that page should be saved before and select dnsmasq to forward.) PC as root: dhclient bnep0 in genwall: in genwall setup the firewall and forwarding you could do it also before making the connection. {local-basics} 1.:select wan device gprs/usb/wlan 2. I would "accept connection from local machine"... makes live easier (really this should be activated!) 3. If you want to connect from pc->N900 without openning ports. I would also recommend to "Accept connection from local lan". (or allow port for dhcp) {for/out} 4. activate forwarding and set lan device to bnep 5. Masquerade wan device should be active {local-basics} 6.gen rules 7. push the start button Disconnect: PC as user: ctrl+c PC as root: pairable off agent off power off quit EDIT: Oh on another N900 my tutorial is still working And btw with genwall you could also make a wep wifi hotspot in addition with a firewall, also with your own rules. |
Re: N900 bluetooth tethering with Debian PC in 2019?
Quote:
Quote:
Frankly, I'm about to give up here. Networking is really not my strong suit and I'm not really motivated to change that. Now that I know there are multiple "ways" of tethering I discovered, that nm-applet actually uses dun when setting up a bluetooth connection. So I'd rather follow that path, if any. Quote:
Out of desperation I tried it anyways, but by that time I had messed up settings genwall so hard, that I didn't know how to help myself, other than rebooting the device. After the reboot it worked fine though. I still don't feel very comfortable with this solution, and since I already have a fallback via USB I'm not sure I'll use the wifi approach. |
Re: N900 bluetooth tethering with Debian PC in 2019?
Quote:
You can look in genwall local-lsof tab, there you should see dnsmasq listen on port 53 tcp. Does the N900 has a bnep0 IP address (route-ip info tab)? On that tab you could also click on dnsmasq and you will see hopefully two processes running. One for local host 127.0.0.1 and one for your bt ip. |
Re: N900 bluetooth tethering with Debian PC in 2019?
I forgot to say all my tests were made with genwall 1.2.2 from extras-devel sorry for missing this maybe important thing.
|
All times are GMT. The time now is 04:53. |
vBulletin® Version 3.8.8