Ticket #118 (assigned defect)

Opened 6 years ago

Last modified 5 years ago

bluetooth networking support

Reported by: laforge@… Owned by: openmoko-devel
Priority: high Milestone:
Component: bluez Version: current svn head
Severity: normal Keywords:
Cc: buglog@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

We want to be able to establish both connections to existing bluetooth access
points, as well as act ourselves as access point for other bluetooth devices.

Change History

comment:1 Changed 6 years ago by marcel@…

  • Status changed from new to assigned

The main support will be the PAN profile with BNEP as underlaying protocol. The
idea is to transform the pand program into bluetoothd-service-network that will
act in NAP and GN roles. Then it has control a bridge device that will forward
packages over GPRS or allow access into the device itself.

For PANU role (client) it needs to detect other access points in range and then
connect to them. Getting the routing right seems to be hardest part since for
the user there should be no difference if it is via Bluetooth, WiFi?, GRPS or USB.

A proper D-Bus interface has been specified, yet.

comment:2 Changed 5 years ago by willie_chen@…

  • Owner changed from marcel@… to michael@…
  • Status changed from assigned to new

Hi Machiael,
Help us follow this issue.

comment:3 Changed 5 years ago by roh

  • Owner changed from michael@… to michael

comment:4 Changed 5 years ago by john_lee

  • Owner changed from michael to openmoko-devel
  • Status changed from new to assigned
  • HasPatchForReview unset

reassign bluetooth related tickets to openmoko-devel now. we might look into these later.

Note: See TracTickets for help on using tickets.