Dear Linux users,

I'd like to give my Nokia N-gage QD the internet connection via Bluetooth from my Linux box. I need this trick as I develop mobile sites and I'd like to see them on a real phone.
This was possible with my old xp, but I don't want to come back to that horrible OS.

I can share everything between Linux and Nokia N-Gage through Bluetooth (I use Kbluetoothd).

Doing some Google search, I met someone talking about GNUBOX. I tried it, but it doesn't work even if everything goes right setting up both the phone and the Linux box.

Now I've a doubt : as I take internet connection via wireless card, can a Linux box forward this kind of internet connection ?

Or, easier, anyone has my problem, maybe with some other Nokia phone using GNUBOX ? Anyone managed to work the connection ?

Thanks
Fabio

Hai i am new to linux.I have an N-Gage mobile but i donot know how to configure for dialup network in linuxin suse linux.I can transfer files from the hdd to mobile.

Hi,

Don't know if it will be of any use, but I connect to the Internet usinf bluetooth from my Palm T5 PDA via my Fedora Core 4 box.

What it boils down to is getting bluetooth configured, a PPP connection up and running on request from the PDA and sorting out the IP routing.

The standard FC4 bluetooth packages (bluez-utils etc.) provide all the required tools but requires a bit of configuring to get bluetooth active and advertising the right services etc.

Service start-up runs 'hcid' for event handling, 'sdpd' for service discovery and 'rfcomm' to provide a socket interface. A dial-up network daemon 'dund' is run for the appropriate connection events that then runs 'ppp' for the IP connection.

How this would apply to you set-up, I don't know. If you are using FC4 let me know and I can supply the configuration files I use.

Took me about a week of evenings to get it working reliably.

Have Fun!

--DaveG

I use Fedora core 4.So pls send me the scripts you have.Good night we will meet tomorrow.

FC4 packages (base): bluez-hcidump-1.18-1, bluez-utils-2.15-7, bluez-libs-devel-2.15-1, bluez-libs-2.15-1, bluez-pin-0.24-2, ppp-2.4.2-7.

/etc/bluetooth/hcid.conf:
# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# PIN helper
#pin_helper /usr/bin/bluepin;

# D-Bus PIN helper
dbus_pin_helper;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x120104;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;

# Authentication and Encryption (Security Mode 3)
#auth enable;
#encrypt enable;
}

/etc/bluetooth/rfcomm.conf: all commented out.

/etc/bluetooth/pin: single line containing your PIN string. e.g. "1234".

/etc/sysconfig/dund:
DUNDARGS='--listen --persist -pppd file /etc/ppp/options.pda'

/etc/sysconfig/hidd:
HIDDARGS="--server"

/etc/sysconfig/pand:
PANDARGS='--listen --role NAP'

/etc/ppp/options.pda
#
# PPP Options for PDA connections.
#
local
passive
auth
name usb
ktune
noipv6
proxyarp
asyncmap 0
ms-dns <your DNS server IP>
# e.g. ms-dns 192.168.1.1
ms-wins <your WINS server IP>
# e.g. ms-wins 192.168.1.16

/etc/ppp/options.rfcomm0:
<server IP>:<device IP>
# e.g. 192.168.99.16:192.168.1.24
linkname rfc0

Notes:
The bluetooth PIN for the server must be set up.
The device and server need to "trust" each other.
PPP will use system defaults plus 'options.pda' for the connection plus 'options.<device>'. The first bluetooth socket will be named 'rfcomm0'. This is used to assign an IP address to the device.
Router and firewall issues are avoided by using proxy ARP - the bluetooth device is assigned an IP address in the same range as the local network and the server does most of the work.
Remove the 'auth' entry in 'options.pda' if you don't want to set up PPP PAP/CHAP passwords.
Enable services; bluetooth, dund and pand.

Typical /var/log/messages for a bluetooth connect-disconnect:
dund[26552]: New connection from <ethernet address>
kernel: CSLIP: code copyright 1989 Regents of the University of California
kernel: PPP generic driver version 2.4.2
pppd[26560]: pppd 2.4.2 started by root, uid 0
pppd[26560]: Using interface ppp0
pppd[26560]: Connect: ppp0 <--> /dev/rfcomm0
kernel: PPP Deflate Compression module registered
pppd[26560]: found interface eth0 for proxy arp
pppd[26560]: local IP address 192.168.99.16
pppd[26560]: remote IP address 192.168.1.24
pppd[26560]: IPCP terminated by peer
pppd[26560]: LCP terminated by peer
pppd[26560]: Hangup (SIGHUP)
pppd[26560]: Modem hangup
pppd[26560]: Connection terminated.
pppd[26560]: Connect time 0.5 minutes.
pppd[26560]: Sent 1206 bytes, received 1452 bytes.
pppd[26560]: Connect time 0.5 minutes.
pppd[26560]: Sent 1206 bytes, received 1452 bytes.
pppd[26560]: Exit.


Hope that helps. Let me know if I've forgotten anything.

--DaveG.

Just found something else that may be of interest to the Phone Phreaks:
http://www.fenrus.org/tomtom/
Using a Linux server to emulate a GPRS phone for a TomTom Sat Nav.

--DaveG