Active Topics
-
Firefox with Leste (5)
to Maemo 7 / Leste by teroyk - 1 day, 3 hrs ago -
Handbook (2)
to Maemo 7 / Leste by teroyk - 2 days, 2 hrs ago - more...
|
2010-08-16
, 03:31
|
|
Posts: 45 |
Thanked: 3 times |
Joined on Jun 2010
|
#22
|
I am using Windows 7 with no software for my bluetooth (it came without) so I have the bluetooth device in Devices and Printers.
There I have the pairing with my N900 and I press Connect -> Direct Connection.
After it says "successful" in Network Connections the Bluetooth PAN shows "Connected to WorldKaoss", IP is set-up manually packets are sent but none recieved.
PC Connectivity in my settings (on the phone) by default was set on "None" so all the settings (Internet, Wlan, Bluetooth,etc) are disabled. Should I use the "Default" profile for the PC Connectivity Manager?
There I have the pairing with my N900 and I press Connect -> Direct Connection.
After it says "successful" in Network Connections the Bluetooth PAN shows "Connected to WorldKaoss", IP is set-up manually packets are sent but none recieved.
PC Connectivity in my settings (on the phone) by default was set on "None" so all the settings (Internet, Wlan, Bluetooth,etc) are disabled. Should I use the "Default" profile for the PC Connectivity Manager?
|
|
2010-08-16
, 03:36
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#23
|
Originally Posted by WorldKaoss
You should select None in PC connectivity. I just make use of its PAN support only. No configuration on it is needed.
I am using Windows 7 with no software for my bluetooth (it came without) so I have the bluetooth device in Devices and Printers.
There I have the pairing with my N900 and I press Connect -> Direct Connection.
After it says "successful" in Network Connections the Bluetooth PAN shows "Connected to WorldKaoss", IP is set-up manually packets are sent but none recieved.
PC Connectivity in my settings (on the phone) by default was set on "None" so all the settings (Internet, Wlan, Bluetooth,etc) are disabled. Should I use the "Default" profile for the PC Connectivity Manager?
Make sure you don't have firewall (blah blah) blocking your way. Please show me the following outputs for investigation:
On client side:
Code:
ipconfig /all route print
Code:
root ifconfig bnep0 route iptables -L -t nat cat /proc/sys/net/ipv4/ip_forward
|
|
2010-08-16
, 03:52
|
|
Posts: 45 |
Thanked: 3 times |
Joined on Jun 2010
|
#24
|
ipconfig /all
route print:
cat /.../... (blah blah) returns "1"
the rest from the n900 is here:
http://img191.imageshack.us/g/47073285.png/
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\WorldKaoss>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : WorldKaoss-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-22-5A-16-DA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 11-11-11-11-11-11
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4407:c5ba:5ccb:9aa%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 252776721
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-D8-31-DF-00-1E-33-D9-9E-DA
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Adapter
Physical Address. . . . . . . . . : 00-24-D2-D3-4A-24
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d1bb:499b:9f3a:cd30%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, August 15, 2010 3:27:15 PM
Lease Expires . . . . . . . . . . : Monday, August 16, 2010 7:41:09 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 234890450
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-D8-31-DF-00-1E-33-D9-9E-DA
DNS Servers . . . . . . . . . . . : 208.67.222.222
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8102E/RTL8103E Family PCI-E Fa
st Ethernet NIC (NDIS 6.20)
Physical Address. . . . . . . . . : 00-1E-33-D9-9E-DA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-48-BD
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::287a:8e64:bf3c:55f3%30(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 738721831
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-D8-31-DF-00-1E-33-D9-9E-DA
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{449A6FED-3483-4A81-8FD3-67E8317D2482}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{225A16DA-B328-4E81-A21F-90D764B89B54}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{187D96D0-31A0-49BA-AE91-CFCAD5BB9F76}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{9621A8B4-AD2F-4337-B427-8469910DBDBC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{8A4EB57C-D2FB-4C61-9FE8-5EEE6015CE62}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #6
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\WorldKaoss>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\WorldKaoss>route print
================================================== =========================
Interface List
23...00 ff 22 5a 16 da ......TAP-Win32 Adapter V9
14...11 11 11 11 11 11 ......Bluetooth Device (Personal Area Network)
13...00 24 d2 d3 4a 24 ......Atheros AR5007EG Wireless Network Adapter
12...00 1e 33 d9 9e da ......Realtek RTL8102E/RTL8103E Family PCI-E Fast Ethern
et NIC (NDIS 6.20)
30...08 00 27 00 48 bd ......VirtualBox Host-Only Ethernet Adapter
1...........................Software Loopback Interface 1
21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
11...00 00 00 00 00 00 00 e0 Microsoft Teredo Tunneling Adapter
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
22...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
34...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #6
================================================== =========================
IPv4 Route Table
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.10 25
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 296
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.0.0 255.255.255.0 On-link 192.168.0.10 281
192.168.0.10 255.255.255.255 On-link 192.168.0.10 281
192.168.0.255 255.255.255.255 On-link 192.168.0.10 281
192.168.1.0 255.255.255.0 On-link 192.168.1.2 296
192.168.1.2 255.255.255.255 On-link 192.168.1.2 296
192.168.1.255 255.255.255.255 On-link 192.168.1.2 296
192.168.56.0 255.255.255.0 On-link 192.168.56.1 276
192.168.56.1 255.255.255.255 On-link 192.168.56.1 276
192.168.56.255 255.255.255.255 On-link 192.168.56.1 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.56.1 276
224.0.0.0 240.0.0.0 On-link 192.168.0.10 281
224.0.0.0 240.0.0.0 On-link 192.168.1.2 296
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.56.1 276
255.255.255.255 255.255.255.255 On-link 192.168.0.10 281
255.255.255.255 255.255.255.255 On-link 192.168.1.2 296
================================================== =========================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.1.1 Default
================================================== =========================
IPv6 Route Table
================================================== =========================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
30 276 fe80::/64 On-link
13 281 fe80::/64 On-link
14 296 fe80::/64 On-link
30 276 fe80::287a:8e64:bf3c:55f3/128
On-link
14 296 fe80::4407:c5ba:5ccb:9aa/128
On-link
13 281 fe80::d1bb:499b:9f3a:cd30/128
On-link
1 306 ff00::/8 On-link
30 276 ff00::/8 On-link
13 281 ff00::/8 On-link
14 296 ff00::/8 On-link
================================================== =========================
Persistent Routes:
None
C:\Users\WorldKaoss>
the rest from the n900 is here:
http://img191.imageshack.us/g/47073285.png/
|
|
2010-08-16
, 04:01
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#25
|
Man you've quite a lot of networks in one system you know that. ^^
First thing I saw is that the WiFi get in the way in the default routing:
Such that the PAN (0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 296) is never reached.
To make the case more complicated, you've wifi routing activated in your N900, such that you've two default routes in your N900: (http://img190.imageshack.us/i/87881079.png/)
If you're not that familiar with tcp/ip routing, you should really turn off everything else before connecting to another network you've never got it worked.
Try again and let me know the result.
First thing I saw is that the WiFi get in the way in the default routing:
Code:
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.10 25
To make the case more complicated, you've wifi routing activated in your N900, such that you've two default routes in your N900: (http://img190.imageshack.us/i/87881079.png/)
If you're not that familiar with tcp/ip routing, you should really turn off everything else before connecting to another network you've never got it worked.
Try again and let me know the result.
|
|
2010-08-16
, 04:11
|
|
Posts: 45 |
Thanked: 3 times |
Joined on Jun 2010
|
#26
|
I disabled every connection and tried again but it's still the same.
One thing I noticed is that in "Status" for the Bluetooth PAN (on my PC) it says:
IPv4: No Internet Connectivity
IPv6: No Network Connectivity
I will try again when I wake up as I haven't slept at all and it's 7:11 AM.
I will post the progress
thanks
One thing I noticed is that in "Status" for the Bluetooth PAN (on my PC) it says:
IPv4: No Internet Connectivity
IPv6: No Network Connectivity
I will try again when I wake up as I haven't slept at all and it's 7:11 AM.
I will post the progress
thanks
|
|
2010-08-16
, 04:18
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#27
|
Also I found that you have not set the IP of the client right:
Shouldn't you set the client as 192.168.1.2 instead?
Good night. Have a nice dream and don't fall into Limbo.
Code:
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 296
Good night. Have a nice dream and don't fall into Limbo.
|
|
2010-08-16
, 04:21
|
|
Posts: 45 |
Thanked: 3 times |
Joined on Jun 2010
|
#28
|
I've set the client IP 192.168.1.2 and the Gateway 192.168.1.1 (the settings are still the same now).
I will check more on this when I wake up.
I will check more on this when I wake up.
|
|
2010-08-16
, 04:29
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#29
|
Originally Posted by WorldKaoss
I see. I'd probable asleep with you awake. Just few thing to note:
I've set the client IP 192.168.1.2 and the Gateway 192.168.1.1 (the settings are still the same now).
I will check more on this when I wake up.
1) Make sure not other default route (0.0.0.0 0.0.0.0) on top of your PAN in route print
2) After paring up and join PAN, activate the script on N900 again
Have a nice dream.
|
|
2010-08-16
, 09:36
|
|
Posts: 1,425 |
Thanked: 983 times |
Joined on May 2010
@ Hong Kong
|
#30
|
Although setting sudoers is better, but it seems to confuse a lot of people. I've made change to the procedure section 4.3.3 to run the script directly with root privilege:
Code:
echo "/home/user/bluetooth-pan.sh" | sudo gainroot
 |
| Tags |
| bluetooth-pan, tethering |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 13:52.
Did you join PAN on client side? It must be done after pairing up. You may see bluetooth has lots of function, it doesn't activate all functions by default, you need to trigger it manually on client side.
Also, depends on some client platform, you need to activate the script *after* client pairing up and join PAN.
In your case, please follow:
1) Pair up Bluetooth
2) Join Bluetooth PAN on client side
3) Choose Internal connection manually on N900
4) Activate the script on N900
5) Setup DNS on client (as shown the the procedure)
6) ping yahoo.com, or browse the web directly on the client side to see it works
Hope this help.