The Maemo Record

Tethering the N900

PACKAGEtethering
SECTIONthe software
IN THE LINEcore: the platform itself
ANSWERSn900 tethering
ARCHIVED LINKS1 old article address points here

Tethering the N900 means using the internet tablet as a data link for another machine, so a laptop or a phone shares the N900's 3G connection. Nokia shipped the N900 in 2008 as a fully open Debian system, and its Maemo 5 software includes working network sharing over 2 routes: Bluetooth DUN and USB. Either way, the N900 stays connected to the 3G network, and the other device borrows the link for web traffic, downloads and e-mail.

A tangled bundle of network cables on a desk, one plug dangling toward a port.

Before any cable or pairing, understand what the tablet is and what is missing from it. The N900 runs Maemo 5 on a 600 MHz ARM processor with 128 MB of RAM, and its base image is a Debian derivative you can extend with 4 main categories of packages: user applications, network tools, drivers and desktop components. That openness is the point of What you could actually install on this device: a 150 MB firmware image leaves the rest of the package repository open, and the community repositories at the Maemo community store carried 3,000 or more packages at their peak. For tethering you need nothing more than the base system; the rest decides what the shared connection is used for. The official The Ovi Store on Maemo 5 was limited in range, which pushed users to community repositories for anything beyond the basics, from file managers to terminal tools.

How N900 tethering works

Tethering works by making the N900 a modem, and the mechanism differs between the 2 routes. Over Bluetooth DUN the tablet emulates a dial-up modem: the computer dials the N900 with a PPP or RAS profile, and the N900's own 3G link carries the traffic. Over USB the tablet exposes a serial port that behaves the same way, without pairing or radio overhead. In both cases the N900 keeps its own 3G data session, so the tablet can still browse, e-mail or navigate while the computer uses the shared line. This is a serial-style data channel, not a NAT router, which is why a single computer at a time is the sensible setup.

Set up Bluetooth DUN on the N900

To set up Bluetooth DUN on the N900, enable the modem side first, then pair the computer. The steps are:

  1. On the N900, open Settings and enable the Bluetooth stack.
  2. Open the Bluetooth profile list and switch the N900 to the DUN role, not the standard client role.
  3. On the computer, add the N900 as a Bluetooth device and pair it with the 16 digit passkey shown on the tablet.
  4. Create a dial-up connection on the computer that targets the N900's Bluetooth address, using the default DUN number and leaving user and password blank.
  5. Connect the dial-up profile, and confirm that the N900's 3G indicator stays active while the computer's connection comes up.

After the first pairing, the 2 devices remember each other, and reconnecting is a single click. The DUN link negotiates in a few seconds once both radios are awake.

Set up USB tethering on the N900

To set up USB tethering on the N900, use a data cable, not a charge-only lead, and enable the USB serial function. The sequence is shorter than the Bluetooth route:

  1. Plug the N900 into the computer with a USB data cable.
  2. On the N900, open the USB settings and select the modem or serial function instead of mass storage.
  3. On the computer, let the dial-up or cellular connection tool detect the new serial port.
  4. Connect the new port with an empty username and password, and check the link speed the computer reports.

The USB route typically delivers the full speed of the 3G line, which on an HSDPA network of the 2008 era meant roughly 3 to 7 Mbit/s in practice. The Bluetooth DUN link is slower, usually settling around 0.5 to 1 Mbit/s, but it needs no cable at all.

Route Setup time Typical speed Needs
Bluetooth DUN 10 minutes 0.5 to 1 Mbit/s Pairing, no cable
USB serial 5 minutes 3 to 7 Mbit/s Data cable

Use the shared connection for data apps

The shared connection is for data-hungry apps, and the classic pair is Maps and navigation plus an e-mail client. With MeeGo on the N900 in mind, remember the successor line: the N9 and N950 that followed moved to the MeeGo 1.2 platform and dropped the N900's DUN roles in favor of a Wi-Fi hotspot that could feed 5 clients at once. The N900 itself has no hotspot mode, so the computer, not the tablet, is the hub. In day to day use, the tethered laptop runs the heavier work while the N900 handles light browsing, and the 3G data plan carries both. Battery life matters here: a tethered session drains the tablet faster than idle use, and a fully charged N900 holds a USB tether for a couple of hours on a 1,500 mAh battery, which is why most owners kept the charger plugged in during long downloads.

Fix common tethering problems

Most tethering problems on the N900 come from 3 sources, and each has a known fix:

These failures are electronics level rather than network level, which is why they are common in a device that is now 15 years old: capacitors age, ports wear, and a 2008 battery no longer holds a 1,500 mAh charge the way it did at the shelf. The same diagnostics apply to any of the related devices in the same family, from the N800 and N810 before the N900 to the MeegoPhone hardware that carried MeeGo forward after Nokia left the platform.

Why the N900 tether still matters

The N900 tether still matters because the device is the last of the line to expose both routes without a closed modem stack, and because its open system means every setting in this page can be inspected and changed with a text editor. A tablet that can share its 3G link over 2 independent routes is a useful field device in 2026 the way it was in 2008: it gives an old laptop a network where no Wi-Fi exists, and it does so with software you can read. The lineage that followed, from MeeGo handsets to the Sailfish OS tablets that Jolla still sells, learned from this open approach, and the N900 remains the reference point for anyone who wants to see how Linux tethering worked before hotspots were built into everything.

Where to go next