[HOWTO] N900 Bluetooth-PAN Tethering (N900 supplies Internet Access for PC) - Page 9 - maemo.org

Active Topics

TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 1 hr, 49 mins ago
Error after installing Leste on sdcard (12)
to Maemo 7 / Leste by teroyk - 2 hrs, 37 mins ago
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 10 hrs ago
Maemo repository (3)
to Community by torsen - 4 days, 3 hrs ago
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 7 hrs ago
more...

Page 9 of 31

Thread Tools

	anapospastos	2011-02-10 , 14:30
	Posts: 553 \| Thanked: 183 times \| Joined on Oct 2009 @ Not decided	#81

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

&

bnep0 Link encap:Ethernet HWaddr C0:38:F9:18:40:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:161 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37112 (36.2 KiB) TX bytes:0 (0.0 B)

__________________
My name was Maemo, then it became Meego and now I'm getting a third one. I am Sailfish.

Quote & Reply |

9000	2011-02-10 , 16:16
Posts: 1,425 \| Thanked: 983 times \| Joined on May 2010 @ Hong Kong	#82

Let see if you can ping to your 850. In your N900:

Code:

ping 192.168.1.2

Quote & Reply |

	anapospastos	2011-02-10 , 17:00
	Posts: 553 \| Thanked: 183 times \| Joined on Oct 2009 @ Not decided	#83

No it doesn't answer. Something is wrong with the N900 I think. I tried with proxy enabled on k850 but again no luck.

__________________
My name was Maemo, then it became Meego and now I'm getting a third one. I am Sailfish.

Quote & Reply |

9000	2011-02-10 , 17:21
Posts: 1,425 \| Thanked: 983 times \| Joined on May 2010 @ Hong Kong	#84

I just notice that there isn't any IP address in the 'ifconfig bnep0' output, and your iptables queue is empty, which means the script isn't even run properly. It's required in section 4.3.3 that you must have root privilege to run the script.

Do you have rootsh installed? If so, please enter run and run the script again to see if the IP address has been setup correctly.

Quote & Reply |

	anapospastos	2011-02-10 , 18:54
	Posts: 553 \| Thanked: 183 times \| Joined on Oct 2009 @ Not decided	#85

Ok now the script is working but ip tables are still empty. "ifconfig bnep0" output is

Code:

bnep0     Link encap:Ethernet  HWaddr C0:38:F9:18:40:FF  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::c238:f9ff:fe18:40ff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1822 (1.7 KiB)  TX bytes:766 (766.0 B)

The k850 should get a new ip or it shares this from N900?

__________________
My name was Maemo, then it became Meego and now I'm getting a third one. I am Sailfish.

Quote & Reply |

9000	2011-02-10 , 23:18
Posts: 1,425 \| Thanked: 983 times \| Joined on May 2010 @ Hong Kong	#86

Originally Posted by anapospastos

Ok now the script is working but ip tables are still empty. "ifconfig bnep0" output is

Code:

bnep0     Link encap:Ethernet  HWaddr C0:38:F9:18:40:FF  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::c238:f9ff:fe18:40ff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1822 (1.7 KiB)  TX bytes:766 (766.0 B)

The k850 should get a new ip or it shares this from N900?

The script has not (yet) handle dhcp, so you must setup the IP address on your k850 manually.

Quote & Reply |

	anapospastos	2011-02-11 , 09:15
	Posts: 553 \| Thanked: 183 times \| Joined on Oct 2009 @ Not decided	#87

I 've set manually the ip as also dns, gateway etc but it refusing to connect.

__________________
My name was Maemo, then it became Meego and now I'm getting a third one. I am Sailfish.

Quote & Reply |

9000	2011-02-11 , 11:46
Posts: 1,425 \| Thanked: 983 times \| Joined on May 2010 @ Hong Kong	#88

no ping to peer side? Is there any way to check whether the PAN has successfully establish on your 850 side? Have you tried to pair up PAN with you N900 to other device like a PC?

Just to make sure, are you sure you setup the IP of the correct interface on your 850? In N900 it is bnep0, which is setup by my script.

Quote & Reply |

eezo	2011-02-11 , 20:01
Posts: 22 \| Thanked: 6 times \| Joined on Dec 2009	#89

Thanks for the tutorial, it works for me with Gentoo on my notebook.

However, although I'm not "afraid" to use the terminal, there still is a huge drawback in comparison to tethering via DUN: I can't seem to get it working without running something in the terminal. I understand that bnep0 is created dynamically on the N900 when I'm establishing the connection, but bnep0 doesn't have an IP after the connection is established. Digging through some Debian documentation, I set the IP address and up script in /etc/network/interfaces, but neither is applied. Following the bluez PAN documentation, there's the --devup option for pand, but setting Script under [PANU Role] in /etc/bluetooth/main.conf on the N900 to your setup script doesn't do a thing.
Is anyone deep enough into the N900/Debian side of things to have the final clue for me?

Quote & Reply |

9000	2011-02-12 , 05:52
Posts: 1,425 \| Thanked: 983 times \| Joined on May 2010 @ Hong Kong	#90

Originally Posted by eezo

Thanks for the tutorial, it works for me with Gentoo on my notebook.

However, although I'm not "afraid" to use the terminal, there still is a huge drawback in comparison to tethering via DUN: I can't seem to get it working without running something in the terminal. I understand that bnep0 is created dynamically on the N900 when I'm establishing the connection, but bnep0 doesn't have an IP after the connection is established. Digging through some Debian documentation, I set the IP address and up script in /etc/network/interfaces, but neither is applied. Following the bluez PAN documentation, there's the --devup option for pand, but setting Script under [PANU Role] in /etc/bluetooth/main.conf on the N900 to your setup script doesn't do a thing.
Is anyone deep enough into the N900/Debian side of things to have the final clue for me?

NP, what you're working on interested me too. Let's make it work.

What my script does is very simple: setup the IP on bnep0 and create the forwarding for internet access.

If you've seen the bnep0, N900 is pretty much done everything it has to do. You're using Gentoo I'm sure you understand what I mean, and you must see there's nothing in N900 that blocks your way in this case.

That's why I'd like you to check whether there's anything blocked on 850 size. I'm not going to blame 850 for anything poorly written, but there's still a lot of things that can go wrong in 850 if you can't open the terminal and look at the interface directly.

Say, if you've setup the IP on the wrong interface on 850, of course it won't work.

Also, it's chance that there's a startup sequence in 850 that when the PAN is establish it'd automatically do something that is not your intent, and drop the PAN entirely if that sequence failed. That's what we want to find out.

Sorry about the terminal things, but actually I don't go to the terminal to trigger that script everytime when I am using it (daily in fact). I trigger the script through Queen Beecon Widget once I got the PAN established.