Thread: N800 PAN workaround installer
View Single Post
PePPeRV is offline PePPeRV
2007-07-02 , 00:47
Posts: 2 | Thanked: 1 time | Joined on Jun 2007
#31
Sorry guys for the delay. Please check out my post again. I have commented the script to be more clear about the choices we have.

When I first posted the script I have it with DHCP enabled, but I have come across a bug with ubuntu edgy bluez-utils bug, that didn't let me to reconnect after I disconnect and I leave it to the fanoush's default script. I have to manual shut down the bnep0 inferface from my ubuntu machine to be able to reconnect again to internet through my ubuntu box. I have not searched yet what's causing it but .... with find it I hope.

In windows XP I was able to connect and get IP from DHCP Server but I wasn't able to share my internet connection. I used BlueSoleil drivers and everything seemed to be allright, except the known XP bug about Internet Connection Sharing that forces you to use 192.168.0.1 as IP of the interface, which is not acceptable in most cases. I thing I little searching in google will solve that problem to. It is not N800 problem but windows problem.

I will have to insist to my primary goal of This post.

Does Anybody wants or have the time to collaborate and bring a final solution (a fully automate solution to the matter )?? I need someone who has worked with maemo API to do a simple Contol Panel plugin GUI

Originally Posted by gleitz View Post
I ditched the BlueSoleil drivers and switched to

My steps are as follows:

1. Open xterm, sudo gainroot
2. pand -Q10 (accept network access on PC from n800)
3. pand -l (displays "bnep0 00:10:C6:91:18:F9 PANU)
4. Connect to network "BlueToothPan" using connection manager
5. udhcpc -i bnep0 (says deleting routers, route: no such process, and adding dns 192.169.0.1

At this point the internet works correctly, but with a little less automation that I would have liked from the script. Any thoughts on what might be the problem?
There is no need to for Xterm with the script. Just watch the Bluetooth Icon in your status bar. If it get yellowed the you are connected to the PAN, if it is white then something is went wrong and you should do some troubleshooting with "pand". As for the DHCP problem see again my initial post (I made some editing again).

Originally Posted by gleitz View Post
Additionally, there are a ton of echo statements in PePPeRV's script, but I never get any console output. Do I need to enable something to get the output from the bluetoothPAN script?

Thx!

EDIT: a shell script run from "osso-statusbar-cpu" automates the process, removing the xterm requirement
No need. See above. It is something that you should not run from command line(Weird syntax because of dbus-scripts). Right now there 3 type of messages you are receiving.

Connected : Everything including DNS is set up from N800 side
Disconnected : Manually disconnected using the Connection manager. There is no support to be informed if we get out of BT Range. The only indicator is the BT icon in Status Bar.
Connection failed: If something went wrong on N800 side. If you are using DHCP configuration and something isn't right configured you will not see any message because udhcp client will insist trying to get IP from DHCP Server. You will problably have to disconnect the connection and try again.


PS: Did anyone heard something about the new firmware release?
There were rumours that it had to be released 2 days before!!!
Last edited by PePPeRV; 2007-07-02 at 01:53.