NSLU2-Linux
view · edit · print · history

Peripherals.BluetoothAdapter History

Hide minor edits - Show changes to markup

September 24, 2008, at 08:22 PM by Joep den Mulder -- working hardware added (CBTGPS32)
Changed lines 146-147 from:

This will (through udev) also create /dev/rfcomm0 (which can be used for communication).

to:

This will (through udev) also create /dev/rfcomm0 (which can be used for communication).
(rfcomm bind command is not necessary if rfcomm.conf has the entry bind yes;)

Added line 157:

Conceptronic CBTGPS32\\

June 16, 2008, at 08:03 PM by Luca Zorzi -- Added D-Link DBT.120 to compatibility list
Changed lines 161-162 from:
to:

D-Link DBT-120

January 25, 2008, at 09:08 AM by Sander Evers -- changed typo underscore to dash
Changed line 24 from:

kernel-module-hci_usb \ \\

to:

kernel-module-hci-usb \ \\

January 22, 2008, at 05:32 AM by MarkStinson -- forgot minor markup
Deleted lines 18-19:

For SlugOS 4.8:\\

Added lines 20-21:

For SlugOS 4.8:
\\

January 22, 2008, at 05:32 AM by MarkStinson -- Updated required installed ipkgs for SlugOS 4.8
Added lines 9-10:

For OpenSlug 3.10:
\\

Changed lines 19-20 from:

Then register all modules by:\\

to:

For SlugOS 4.8:\\

Added lines 22-34:

ipkg install \
kernel-module-bluetooth \
kernel-module-hci_usb \
kernel-module-l2cap \
kernel-module-bnep \
kernel-module-rfcomm \
bluez-hcidump \
bluez-utils \
bluez-utils-compat

  1. Then register all modules by:
    \\
July 20, 2007, at 11:50 PM by rwhitby -- Updated for latest OpenSlug binary release. Also removed the comments about OpenWrt, which does indeed have bluetooth support.
Deleted lines 2-5:

As of 7/6/2007 this howto doesn't work. OpenSlug 2.5 is no longer available. OpenWrt 2.6 kamikaze does not have the required hci modules nor does it have any of the other kmods available referenced in this howto.

As far as I can tell, kamikaze doesn't support bluetooth at all, even though bluez-utils and blues-libs are available.

Changed lines 5-6 from:
  1. Install OpenSlug 2.5 or later.
to:
  1. Install OpenSlug 3.10 or later.
July 06, 2007, at 05:21 PM by wag3slav3gmailcom -- Notice that this howto is broken
Added lines 3-6:

As of 7/6/2007 this howto doesn't work. OpenSlug 2.5 is no longer available. OpenWrt 2.6 kamikaze does not have the required hci modules nor does it have any of the other kmods available referenced in this howto.

As far as I can tell, kamikaze doesn't support bluetooth at all, even though bluez-utils and blues-libs are available.

June 27, 2007, at 10:58 AM by Darren Long -- Reformatting of the Debian/NSLU2 hardware section I just added
Changed lines 147-149 from:

NSLU2

  • Advent CE1DR? (as sold by PC World in the UK) - plug and play OK
to:

Debian/NSLU2

  • Advent CE1DR (as sold by PC World in the UK) - plug and play OK
June 27, 2007, at 10:54 AM by Darren Long -- Added info about Advent CE1DR working with Debian/NSLU2
Added lines 146-149:

Other hardware/OS combinations

NSLU2

  • Advent CE1DR? (as sold by PC World in the UK) - plug and play OK
April 26, 2007, at 11:44 AM by doorshapeseekercom --
Changed lines 144-145 from:
to:

Sitecom CN-520

April 06, 2007, at 02:34 PM by doorshapeseekercom -- Added known working bluetooth dongle to list
Changed lines 143-144 from:
to:

Sitecom CN-512

January 27, 2007, at 08:14 AM by Martin Mueller -- Add hint when l2ping responds with \\\"Funktion not implemented\\\"
Added lines 56-57:

If l2ping responds with "Function not implemented", it could help to restart your device, not only to restart the bluetooth via bluetooth stop; bluetooth start.

January 14, 2007, at 04:18 PM by Tim Walker -- Added Belkin F8T013 to list of recognised Bluetooth adapters
Changed lines 140-141 from:
to:

BelkinF8T013 (note: this is Broadcom-based, and needs the firmware as below - otherwise, seems to work fine)

December 03, 2006, at 01:02 PM by Jon Hind --
Changed lines 90-91 from:
  1. !/bin/bash
to:
  1. !/bin/sh
December 03, 2006, at 01:00 PM by Jon Hind -- Minor mods
Changed lines 89-91 from:

\\

to:

And if you do not have bash on your slug then the first line may need to read:
#!/bin/bash

Changed line 112 from:
        # Bluetooth address of the device \\
to:
        # Bluetooth address of the device attached to the slug\\
Changed lines 139-140 from:
to:

BelkinFS8100

November 26, 2006, at 07:10 AM by mlp -- added new supported hardware
Changed lines 136-137 from:

Targus ACB10?

to:

Targus ACB10

November 26, 2006, at 07:09 AM by mlp -- added new supported hardware
Changed lines 136-137 from:
to:

Targus ACB10?

August 07, 2006, at 06:06 PM by eFfeM --
Changed line 17 from:

Then if needed register all modules by:\\

to:

Then register all modules by:\\

Deleted lines 18-23:

cd /lib/modules/2.6.*
insmod ./kernel/net/bluetooth/bluetooth.ko
insmod ./kernel/net/bluetooth/l2cap.ko
insmod ./kernel/net/bluetooth/rfcomm/rfcomm.ko
insmod ./kernel/net/bluetooth/bnep/bnep.ko
insmod ./kernel/drivers/bluetooth/hci_usb.ko\\

August 07, 2006, at 05:08 PM by eFfeM --
Changed lines 16-17 from:

@@

to:

@@\\

Added line 18:

\\

August 07, 2006, at 05:07 PM by eFfeM --
Added lines 18-26:

Then if needed register all modules by:
cd /lib/modules/2.6.*
insmod ./kernel/net/bluetooth/bluetooth.ko
insmod ./kernel/net/bluetooth/l2cap.ko
insmod ./kernel/net/bluetooth/rfcomm/rfcomm.ko
insmod ./kernel/net/bluetooth/bnep/bnep.ko
insmod ./kernel/drivers/bluetooth/hci_usb.ko
depmod -a

Added lines 140-143:

List of hardware which is tested to work using this method. (please add)

Conceptronic CBT200U2

Deleted lines 146-147:

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

June 05, 2006, at 04:35 AM by rwhitby --
Deleted lines 90-91:
  1. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
June 05, 2006, at 04:28 AM by rwhitby --
Added lines 12-13:

kernel-module-rfcomm \
kernel-module-bnep \ \\

May 28, 2006, at 03:25 PM by eFfeM --
Added lines 49-50:

If l2ping responds with "Connection refused", it might be that you messed up your link keys. Go to /var/lib/bluetooth/<your device id> and remove the file linkkeys and try again.

April 28, 2006, at 07:25 PM by hifi-andrew -- added ipkg install bluez-utils-nodbus; this has hciconfig
Changed lines 12-13 from:

kernel-module-hci-usb \\

to:

kernel-module-hci-usb \
bluez-utils-nodbus \\

February 28, 2006, at 08:36 PM by eFfeM --
Changed lines 79-80 from:

Where you of course can replace 0000 with your pin.

to:

Where you of course can replace 0000 with your pin.
Do not forget to make /bin/bluepin executable (chmod 555 /bin/bluepin)

Note that the file /etc/bluetooth/hcid.conf contains the location of the pin function. My hcid.conf contained out of the box: # pin_helper /bin/bluepin;. If you have this as well you need to remove the #

February 19, 2006, at 02:56 PM by eFfeM --
Added lines 112-114:

Then I had to connect the port using the command: hcitool cc <device_address>.
You can verify that this actually works and that you made a connection through hcitool con

Changed lines 117-122 from:

This will (through udev) also create /dev/rfcomm0 (which can be used for communication.

After that you should be able to connect to your bluetooth serial device. E.g. use minicom /dev/rfcomm0 (you might need to install minicom first)

Alternately as a starter you can use rfcomm connect 0 <device id>

to:

This will (through udev) also create /dev/rfcomm0 (which can be used for communication).

After that you should be able to connect to your bluetooth serial device. I first tried connecting to my gps device and did cat /dev/rfcomm0 You can also use minicom /dev/rfcomm0 (you might need to install minicom first)

Alternately as a starter you might be able to use rfcomm connect 0 <device id>

February 19, 2006, at 10:30 AM by eFfeM --
Added lines 43-47:

If l2ping responds with "invalid exchange" it is possible that your target device does not support encryption. For that change the auth and encrypt lines in hcid.conf to:
auth disable;
encrypt disable;
You'll need to go to /etc/init.d and issue the commands ./bluetooth stop; ./bluetooth start in order for these settings to take effect. Without this I was unable to connect to my BT GPS receiver.

February 19, 2006, at 10:24 AM by eFfeM --
Changed lines 35-36 from:

hcitool irq

to:

hcitool inq

February 19, 2006, at 10:13 AM by eFfeM --
Changed lines 3-4 from:

The following are the steps required to turn your NSLU2 into a Bluetooth access point for devices like the Treo 650.

to:

Basic Installation

Changed lines 15-17 from:
  1. Test your work.\\
to:

Test your work

You should now be able to do:\\

Deleted lines 18-19:

You should now be able to do:
\\

Changed lines 31-58 from:

The `BDAddr` (short for `BD Address`) is the unique hardware address of the Bluetooth adapter.\\

to:

The `BDAddr` (short for `BD Address`) is the unique hardware address of the Bluetooth adapter.

You can scan for the presence of Bluetooth nodes in your vicinity:

hcitool irq

To prove that the low-level link is up, try pinging the other Bluetooth adapter (using the address hcitool inq returned):

l2ping [BDAddr]

You can also use hcitool scan which will give similar info.

Installing PPP

In order to run PPP (e.g) to turn your NSLU2 into a Bluetooth access point for devices like the Treo 650) install the following additional packages:

ipkg install \
kernel-module-bnep \
kernel-module-ppp-generic \
kernel-module-slhc \
kernel-module-crc-ccitt \
kernel-module-ppp-async \
kernel-module-ppp-deflate \
kernel-module-bsd-comp \
libbluetooth1 \
bluez-utils-nodbus \
ppp

  1. Edit /etc/ppp/options to read:\\
Changed lines 60-67 from:

You can scan for the presence of Bluetooth nodes in your vicinity:\\

to:
 noauth
crtscts
lock
local
proxyarp
ktune
192.168.1.XX:192.168.1.YY
ms-dns 192.168.1.ZZ\\
Changed lines 69-94 from:

hcitool irq\\

to:

(edit the last two lines to suit your network topology, the first IP address is your BlueSlug, the second IP address will be assigned to the client, and the third IP address is your DNS server)

  1. Normally the pin is in the file /etc/bluetooth/pin. This one is read by /bin/bluepin. However bluepin requires pygtk which is not available on the slug. Hence I replaced it with the following script:
    #!/bin/bash
    echo "PIN:0000"
    Where you of course can replace 0000 with your pin.
  2. Reboot the slug
  3. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
  4. Connect to the slug with your Bluetooth client (e.g. a Treo 650)

Getting serial communication to work

In order to run serial communication (rfcomm) install the following additional package:
ipkg install kernel-module-rfcomm
Create /etc/bluetooth/rfcomm.conf. This file should contain:
#
# RFCOMM configuration file.
#

rfcomm0 {
# Automatically bind the device at startup
bind yes; \\

Changed lines 96-149 from:

To prove that the low-level link is up, try pinging the other Bluetooth adapter (using the address hcitool inq returned):

l2ping [BDAddr]

You can also use hcitool scan which will give similar info.

  1. In order to run ppp install the following additional packages:

    ipkg install \
    kernel-module-bnep \
    kernel-module-ppp-generic \
    kernel-module-slhc \
    kernel-module-crc-ccitt \
    kernel-module-ppp-async \
    kernel-module-ppp-deflate \
    kernel-module-bsd-comp \
    libbluetooth1 \
    bluez-utils-nodbus \
    ppp
  2. Edit /etc/ppp/options to read:

    noauth
    crtscts
    lock
    local
    proxyarp
    ktune
    192.168.1.XX:192.168.1.YY
    ms-dns 192.168.1.ZZ

    (edit the last two lines to suit your network topology, the first IP address is your BlueSlug, the second IP address will be assigned to the client, and the third IP address is your DNS server)
  3. Normally the pin is in the file /etc/bluetooth/pin. This one is read by /bin/bluepin. However bluepin requires pygtk which is not available on the slug. Hence I replaced it with the following script:
    #!/bin/bash
    echo "PIN:0000"
    Where you of course can replace 0000 with your pin.
  4. Reboot the slug
  5. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
  6. Connect to the slug with your Bluetooth client (e.g. a Treo 650)

Getting serial communication to work

In order to run serial communication (rfcomm) install the following additional package:
ipkg install kernel-module-rfcomm
Create /etc/bluetooth/rfcomm.conf. This file should contain:
#
# RFCOMM configuration file.
# \\

to:
        # Bluetooth address of the device 
device 00:11:22:33:44:55; \\
Deleted lines 98-104:

rfcomm0 {
# Automatically bind the device at startup
bind yes;

# Bluetooth address of the device
device 00:11:22:33:44:55;
\\

Changed lines 105-106 from:

Where the number after device the device identifies to which you want to connect (as given by rfcomm scan)

to:

Where the number after device (here 00:11:22:33:44:55) identifies the device to which you want to connect (as given by rfcomm scan)

Changed lines 113-116 from:
to:

Alternately as a starter you can use rfcomm connect 0 <device id>

Notes

February 18, 2006, at 10:03 PM by eFfeM --
Changed lines 111-113 from:
to:

After that you should be able to connect to your bluetooth serial device. E.g. use minicom /dev/rfcomm0 (you might need to install minicom first)

February 18, 2006, at 10:01 PM by eFfeM --
Changed line 95 from:
to:

\\

February 18, 2006, at 10:00 PM by eFfeM --
Changed line 84 from:
 In order to run serial communication (rfcomm) install the following additional package:\\
to:

In order to run serial communication (rfcomm) install the following additional package:\\

Added lines 87-106:

Create /etc/bluetooth/rfcomm.conf. This file should contain:
#
# RFCOMM configuration file.
#

rfcomm0 {
# Automatically bind the device at startup
bind yes;

        # Bluetooth address of the device 
device 00:11:22:33:44:55;

# RFCOMM channel for the connection
channel 1;

# Description of the connection
comment "NSLU2";
}
Where the number after device the device identifies to which you want to connect (as given by rfcomm scan)
February 18, 2006, at 09:48 PM by eFfeM --
Changed line 44 from:
  1. Run the following to install additional packages:\\
to:
  1. In order to run ppp install the following additional packages:\\
Deleted line 46:

kernel-module-rfcomm \ \\

Changed lines 71-72 from:
  1. Edit /etc/bluetooth/pin, replacing "BlueZ" with your own PIN.
to:
  1. Normally the pin is in the file /etc/bluetooth/pin. This one is read by /bin/bluepin. However bluepin requires pygtk which is not available on the slug. Hence I replaced it with the following script:
    #!/bin/bash
    echo "PIN:0000"
    Where you of course can replace 0000 with your pin.
Added lines 82-91:

Getting serial communication to work

 In order to run serial communication (rfcomm) install the following additional package:
ipkg install kernel-module-rfcomm

Next bind the port with the command:
rfcomm bind rfcomm0
This will (through udev) also create /dev/rfcomm0 (which can be used for communication.

February 16, 2006, at 03:36 PM by eFfeM -- added external ref
Added lines 1-2:

Note: This is not an introduction or overview on Bluetooth. It is an overview on how to get things installed on the slug. I found http://www.hanscees.com/bluezhowto.html very useful to get an understanding of Bluetooth. A lot of linux bluetooth related info can also be found on: http://www.holtmann.org/linux/bluetooth/

Changed lines 82-84 from:

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

NOTE: A lot of linux bluetooth related info can be found on: http://www.holtmann.org/linux/bluetooth/

to:

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

February 16, 2006, at 12:05 PM by eFfeM --
Changed lines 80-82 from:

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

to:

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

NOTE: A lot of linux bluetooth related info can be found on: http://www.holtmann.org/linux/bluetooth/

February 16, 2006, at 12:03 PM by eFfeM -- added some text
Changed line 5 from:
  1. Run the following to install the packages:\\
to:
  1. Run the following to install the basic packages:\\
Changed lines 10-23 from:

kernel-module-rfcomm \
kernel-module-bnep \
kernel-module-hci-usb \
kernel-module-ppp-generic \
kernel-module-slhc \
kernel-module-crc-ccitt \
kernel-module-ppp-async \
kernel-module-ppp-deflate \
kernel-module-bsd-comp \
libbluetooth1 \
bluez-utils-nodbus \
ppp@@

  1. Edit /etc/ppp/options to read:\\
to:

kernel-module-hci-usb
@@

  1. Test your work.\\
Changed lines 15-22 from:
 noauth
crtscts
lock
local
proxyarp
ktune
192.168.1.XX:192.168.1.YY
ms-dns 192.168.1.ZZ\\
to:

You should now be able to do:\\

Added lines 17-67:

hciconfig hci0 up

to make the Bluetooth interface available to the Bluetooth protocol stack.

Run hciconfig by itself again should give something like this:

hci0: Type: USB
BD Address: 00:03:0D:00:07:8A ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:8567 acl:125 sco:0 events:409 errors:0
TX bytes:4518 acl:128 sco:0 commands:130 errors:0

The `BDAddr` (short for `BD Address`) is the unique hardware address of the Bluetooth adapter.

You can scan for the presence of Bluetooth nodes in your vicinity:

hcitool irq

To prove that the low-level link is up, try pinging the other Bluetooth adapter (using the address hcitool inq returned):

l2ping [BDAddr]

You can also use hcitool scan which will give similar info.

  1. Run the following to install additional packages:

    ipkg install \
    kernel-module-rfcomm \
    kernel-module-bnep \
    kernel-module-ppp-generic \
    kernel-module-slhc \
    kernel-module-crc-ccitt \
    kernel-module-ppp-async \
    kernel-module-ppp-deflate \
    kernel-module-bsd-comp \
    libbluetooth1 \
    bluez-utils-nodbus \
    ppp
  2. Edit /etc/ppp/options to read:

    noauth
    crtscts
    lock
    local
    proxyarp
    ktune
    192.168.1.XX:192.168.1.YY
    ms-dns 192.168.1.ZZ
    \\
January 03, 2006, at 04:18 AM by Alan Parry --
Changed lines 44-46 from:

NOTE: If you have a Broadcom-based bluetooth dongle, you might have to load the firmware. You can get the firmware from the bluez homepage. Just "./configure && make install", "mkdir -p /usr/lib/hotplug/firmware", "mv /lib/firmware/* /usr/lib/hotplug/firmware/"

to:

NOTE: If you have a Broadcom-based bluetooth dongle, you might have to load the firmware. You can get the firmware from the bluez homepage. Just "./configure && make install", "mkdir -p /usr/lib/hotplug/firmware", "mv /lib/firmware/* /usr/lib/hotplug/firmware/"

NOTE: It would be useful to have a list of hardware which is tested to work using this method.

December 16, 2005, at 05:05 AM by rwhitby --
Added line 32:
 ms-dns 192.168.1.ZZ\\
Changed lines 34-35 from:

(edit the last line to suit your network topology, the first IP address is your BlueSlug, the second IP address will be assigned to the client)

to:

(edit the last two lines to suit your network topology, the first IP address is your BlueSlug, the second IP address will be assigned to the client, and the third IP address is your DNS server)

October 21, 2005, at 01:24 PM by repvik --
Added lines 42-43:

NOTE: If you have a Broadcom-based bluetooth dongle, you might have to load the firmware. You can get the firmware from the bluez homepage. Just "./configure && make install", "mkdir -p /usr/lib/hotplug/firmware", "mv /lib/firmware/* /usr/lib/hotplug/firmware/"

August 12, 2005, at 12:54 PM by tman --
Changed line 5 from:
  1. Install the following packages\\
to:
  1. Run the following to install the packages:\\
August 12, 2005, at 12:54 PM by tman --
Added lines 7-21:

ipkg install \
kernel-module-bluetooth \
kernel-module-l2cap \
kernel-module-rfcomm \
kernel-module-bnep \
kernel-module-hci-usb \
kernel-module-ppp-generic \
kernel-module-slhc \
kernel-module-crc-ccitt \
kernel-module-ppp-async \
kernel-module-ppp-deflate \
kernel-module-bsd-comp \
libbluetooth1 \
bluez-utils-nodbus \
ppp

Deleted lines 22-27:
 ipkg install kernel-module-bluetooth kernel-module-l2cap kernel-module-rfcomm kernel-module-bnep
 ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
August 11, 2005, at 09:47 PM by Joschi --
Changed lines 9-11 from:
 -<ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 -<ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 -<ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
to:
 ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
August 11, 2005, at 09:46 PM by Joschi --
Changed line 7 from:
 [=
to:
Changed lines 12-13 from:
 =]
to:
August 11, 2005, at 09:46 PM by Joschi --
Changed lines 9-11 from:
 ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
to:
 -<ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 -<ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 -<ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
August 10, 2005, at 01:22 PM by rwhitby --
Changed lines 3-5 from:
  1. Build OpenSlug 1.5 (Kernel 2.6.11) or later from source.
  2. Modify your local.conf file by adding the following two lines:\\
to:
  1. Install OpenSlug 2.5 or later.
  2. Install the following packages\\
Changed lines 8-17 from:
 OPENSLUG_EXTRA_DEPENDS = "bluez-utils-nodbus ppp"
 OPENSLUG_EXTRA_INSTALL = "         kernel-module-bluetooth kernel-module-l2cap         kernel-module-rfcomm kernel-module-bnep         kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus         kernel-module-ppp-generic         kernel-module-slhc kernel-module-crc-ccitt         kernel-module-ppp-async kernel-module-ppp-deflate         kernel-module-bsd-comp ppp         "
to:
 ipkg install kernel-module-bluetooth kernel-module-l2cap kernel-module-rfcomm kernel-module-bnep
 ipkg install kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
 ipkg install kernel-module-ppp-generic kernel-module-slhc kernel-module-crc-ccitt
 ipkg install kernel-module-ppp-async kernel-module-ppp-deflate kernel-module-bsd-comp ppp
Deleted lines 13-16:
  1. Rebuild a new openslug image (this will be a custom image including all the above modules).
  2. Flash the new custom BlueSlug image.
Changed lines 28-29 from:
  1. Boot the slug
to:
  1. Reboot the slug
Changed line 32 from:
  1. Connect to the slug with your Treo 650.
to:
  1. Connect to the slug with your Bluetooth client (e.g. a Treo 650)
June 20, 2005, at 02:51 PM by tman --
Changed lines 5-6 from:
  1. Modify your local.conf file by adding the following two lines:
to:
  1. Modify your local.conf file by adding the following two lines:
    \\
Changed lines 22-37 from:
  1. Flash the new custom BlueSlug? image.
  2. Edit /etc/ppp/options to read:
 noauth
 crtscts
 lock
 local
 proxyarp
 ktune
 192.168.1.XX:192.168.1.YY

(edit the last line to suit your network topology, the first IP address is your BlueSlug?, the second IP address will be assigned to the client)

  1. Edit /etc/bluetooth/pin, replacing "BlueZ?" with your own PIN.
to:
  1. Flash the new custom BlueSlug image.
  2. Edit /etc/ppp/options to read:

    noauth
    crtscts
    lock
    local
    proxyarp
    ktune
    192.168.1.XX:192.168.1.YY

    (edit the last line to suit your network topology, the first IP address is your BlueSlug, the second IP address will be assigned to the client)
  3. Edit /etc/bluetooth/pin, replacing "BlueZ" with your own PIN.
Changed lines 42-43 from:
  1. Connect to the slug with your Treo 650
to:
  1. Connect to the slug with your Treo 650.
March 16, 2005, at 02:51 PM by rwhitby --
Changed line 10 from:
        kernel-module-bluetooth kernel-module-l2cap kernel-module-sco \
to:
        kernel-module-bluetooth kernel-module-l2cap \
March 16, 2005, at 02:43 PM by rwhitby --
Added lines 40-41:
  1. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
March 16, 2005, at 02:29 PM by rwhitby --
Changed line 13 from:
        kernel-module-netconsole kernel-module-ppp-generic \
to:
        kernel-module-ppp-generic \
Changed line 32 from:
 :192.168.1.XX
to:
 192.168.1.XX:192.168.1.YY
Changed line 34 from:

(edit the last line to suit your network topology)

to:

(edit the last line to suit your network topology, the first IP address is your BlueSlug?, the second IP address will be assigned to the client)

Deleted lines 38-39:
  1. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
March 16, 2005, at 02:26 PM by mathieu_xwave --
Changed line 3 from:
  1. Build OpenSlug 1.4 or later from source.
to:
  1. Build OpenSlug 1.5 (Kernel 2.6.11) or later from source.
Deleted line 9:
        kernel-module-input \
Changed line 11 from:
        kernel-module-rfcomm kernel-module-bnep kernel-module-hidp \
to:
        kernel-module-rfcomm kernel-module-bnep \
February 26, 2005, at 03:02 PM by rwhitby --
Added line 7:
 [=
Changed lines 9-17 from:
 OPENSLUG_EXTRA_INSTALL = " 
kernel-module-input
kernel-module-bluetooth kernel-module-l2cap kernel-module-sco
kernel-module-rfcomm kernel-module-bnep kernel-module-hidp
kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
kernel-module-netconsole kernel-module-ppp-generic
kernel-module-slhc kernel-module-crc-ccitt
kernel-module-ppp-async kernel-module-ppp-deflate
kernel-module-bsd-comp ppp \\
to:
 OPENSLUG_EXTRA_INSTALL = "         kernel-module-input         kernel-module-bluetooth kernel-module-l2cap kernel-module-sco         kernel-module-rfcomm kernel-module-bnep kernel-module-hidp         kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus         kernel-module-netconsole kernel-module-ppp-generic         kernel-module-slhc kernel-module-crc-ccitt         kernel-module-ppp-async kernel-module-ppp-deflate         kernel-module-bsd-comp ppp \
Added lines 19-20:
 =]
February 26, 2005, at 03:00 PM by rwhitby --
Changed lines 8-16 from:
 OPENSLUG_EXTRA_INSTALL = "         kernel-module-input         kernel-module-bluetooth kernel-module-l2cap kernel-module-sco         kernel-module-rfcomm kernel-module-bnep kernel-module-hidp         kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus         kernel-module-netconsole kernel-module-ppp-generic         kernel-module-slhc kernel-module-crc-ccitt         kernel-module-ppp-async kernel-module-ppp-deflate         kernel-module-bsd-comp ppp \
to:
 OPENSLUG_EXTRA_INSTALL = " 
kernel-module-input
kernel-module-bluetooth kernel-module-l2cap kernel-module-sco
kernel-module-rfcomm kernel-module-bnep kernel-module-hidp
kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus
kernel-module-netconsole kernel-module-ppp-generic
kernel-module-slhc kernel-module-crc-ccitt
kernel-module-ppp-async kernel-module-ppp-deflate
kernel-module-bsd-comp ppp \\
February 26, 2005, at 02:59 PM by rwhitby --
Changed lines 1-41 from:

Describe BuildABlueSlug? here.

to:

The following are the steps required to turn your NSLU2 into a Bluetooth access point for devices like the Treo 650.

  1. Build OpenSlug 1.4 or later from source.
  2. Modify your local.conf file by adding the following two lines:
 OPENSLUG_EXTRA_DEPENDS = "bluez-utils-nodbus ppp"
 OPENSLUG_EXTRA_INSTALL = "         kernel-module-input         kernel-module-bluetooth kernel-module-l2cap kernel-module-sco         kernel-module-rfcomm kernel-module-bnep kernel-module-hidp         kernel-module-hci-usb libbluetooth1 bluez-utils-nodbus         kernel-module-netconsole kernel-module-ppp-generic         kernel-module-slhc kernel-module-crc-ccitt         kernel-module-ppp-async kernel-module-ppp-deflate         kernel-module-bsd-comp ppp         "
  1. Rebuild a new openslug image (this will be a custom image including all the above modules).
  2. Flash the new custom BlueSlug? image.
  3. Edit /etc/ppp/options to read:
 noauth
 crtscts
 lock
 local
 proxyarp
 ktune
 :192.168.1.XX

(edit the last line to suit your network topology)

  1. Edit /etc/bluetooth/pin, replacing "BlueZ?" with your own PIN.
  2. Boot the slug
  3. Log in, and run "modprobe hci_usb" (this step is a work-around for a problem that we have with hotplug)
  4. Connect to the slug with your Treo 650
Page last modified on September 24, 2008, at 08:22 PM