maemo.org - Talk - View Single Post - N900 bluetooth tethering with Debian PC in 2019?

sulu	2019-09-17 , 21:05
Posts: 915 \| Thanked: 3,209 times \| Joined on Jan 2011 @ Germany	#21

@Halftux:
Thanks for your efforts with the btpan app! Unfortunately it doesn't change my outcome.

In Debian I have the packages installed and the N900 is paired with my PC. Then I run btpan on the N900 and see a window popping up with this line in it:

Code:

BT connection 0

After I run the test-network call on the PC this line stays unchanged and a 2nd line is added:

Code:

connected to: [MAC of my PC]

But if I then run dhclient bnep0, it still can't get an IP.

In the meantime I've tried to resurrect my old wvdial DUN connection and got a but further but wasn't totally successful.
(fyi, what I'm about to write now is a translation of a post I just wrote at debianforum.de. [1] So If your German is better than your (or my) English it's probably best to read the original.)

My /etc/wvdial.conf:

Code:

[Dialer Defaults]
Phone =
Username =
Password =
New PPPD = yes

[Dialer bt]
Modem = /dev/rfcomm0
ISDN = off
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = AT+CGDCONT=1,"IP","web.vodafone.de"
Phone = *99#
Dial Prefix =
Dial Attempts = 5
Dial Command = ATM1L3DT
Ask Password = off
Password = vodafone
Username = vodafone
Auto Reconnect = on
Abort on Busy = off
Carrier Check = on
Check Def Route = on
Abort on No Dialtone = on
Stupid Mode = off
Idle Seconds = 0
Auto DNS = on

In advance I had created /dev/rfcomm0 manually for the MAC address of my paired N900:

Code:

# rfcomm bind 0 XX:XX:XX:XX:XX:XX
# rfcomm -a
rfcomm0: XX:XX:XX:XX:XX:XX channel 1 clean

The wvdial output looks fine according to my memory:

Code:

# wvdial bt
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
--> Sending: ATQ0
ATQ0
OK
--> Re-Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","web.vodafone.de"
AT+CGDCONT=1,"IP","web.vodafone.de"
OK
--> Modem initialized.
--> Sending: ATM1L3DT*99#
--> Waiting for carrier.
ATM1L3DT*99#
CONNECT
~[7f]}#@!}!} } }2}#}$@#}!}$}%\}"}&} }*} } g}%~
--> Carrier detected.  Waiting for prompt.
~[7f]}#@!}!} } }2}#}$@#}!}$}%\}"}&} }*} } g}%~
--> PPP negotiation detected.
--> Starting pppd at Tue Sep 17 21:40:49 2019
--> Pid of pppd: 6890
--> Using interface ppp0
--> pppd: p��
--> pppd: p��
--> pppd: p��
--> pppd: p��
--> local  IP address 100.67.154.185
--> pppd: p��
--> remote IP address 10.6.6.6
--> pppd: p��
--> primary   DNS address 139.7.30.126
--> pppd: p��
--> secondary DNS address 139.7.30.125
--> pppd: p��

I also get an IP address:

Code:

# ip a
[..]
7: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 3
    link/ppp 
    inet 100.105.81.150 peer 10.6.6.6/32 scope global ppp0
       valid_lft forever preferred_lft forever

But something seems to be wrong with the routing, because I can't even ping public IP addresses (e.g. Google's 8.8.8.8 ), let alone reach websites via DNS.

Somewhere I picked up that route might help me, but it sems I already have the correct route (10.6.6.6)?:

Code:

# route -n
Kernel-IP-Routentabelle
Ziel            Router          Genmask         Flags Metric Ref    Use Iface
0.0.0.0         0.0.0.0         0.0.0.0         U     1002   0        0 enp4s0
10.6.6.6        0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 enp4s0
root@eee:~# route add default ppp0

Is the PC the right place to set this up at all or do I have to do this on the N900?

[1] https://debianforum.de/forum/viewtop...74706#p1217285

Quote & Reply |

The Following User Says Thank You to sulu For This Useful Post:
Halftux