Talk:HOWTO Configure a bluetooth network access point

From Gentoo Linux Wiki

[edit] Article have got some errors I think

At the beginning, here is a lot of useful information. But i don't get a reason why we create bridge with lan (eth0) interface. I think here is a mistake. Why? Reason we could create a bridge is for gather all bnepX interface which pand create (so we could use one ip address). for example: br0 (bridge which gather bnepX interface) ifconfig br0 192.168.0.1 bnep0,bnep1,bnep2 etc. are added to br0. bnepX interface are created by pand daemon and shows only when devices are connected. Why we don't need to create bridge between bnepX and eth0? the same reason we don't create bridge for example between eth0 and eth1 (eth0 and eth1 are different network card). I noticed that when we create a bridge between bnepX and eth0 there are problems with connection.

1. you forgot to tell to enable bridging in kernel :)
2. you forgot to tell that the bnep iface is only up once someone connects to the pan network!
3. i think using bridging is asking for troubles!!

You can simply start the pand and stuff, and NAT the connections :) Also, suggest a dhcp (selfdhcp is small) because most bluetooth devices which are no computers cannot assign an ip to themsleves easily.

I have seen issues with enabling the bridging in the kernel. It cut me off from the external network. I couldn't even ping www.google.com or www.yahoo.com.

It seems like there is probably some missing information is this guide. Maybe someone can flesh it out, filling in some of the assumptions.

It worked for me. Although can't get the bnep0 script to bring it up. I have to do it manually.

[edit] Article in need of a slight rewrite

I have this up and running using a slightly different tactic. Using the bridging method described I skipped the net.bnep0 script(s), since we'll have an arbitrary number of bnep interfaces and instead use /etc/bluetooth/pan/dev-up for configuring when a new connection is made.

 
    #!/bin/sh
    # dynamic bnep* configuration for Bluetooth NAP
    ifconfig $1 up
    brctl addif br0 $1
  

This is then combined with this additional configuration so that our bridge will disable the initial 30 seconds of wait before forwarding traffic (there's just no way to get DHCP reliably working otherwise)

 
 brctl_br0=( "stp off"
            "setfd 0" )
  

DHCP is a whole another discussion and shouldn't be covered in here IMHO as this describes how to bridge to a existing LAN where most users already have a DHCP-server. And as for bridging being 'bad', it's a very simple and straightforward method to give bluetooth devices access to the network (of course, that is bad in the same way as having a not properly secured WLan AP bridging to your network).

I will summarize the changes I have done to my system in addition to the above and fix this howto a little. Nostrad 19:57, 19 December 2006 (UTC)

[edit] A little error

While we talk about creating a network interface called "lan" with " $ ln -s net.lo net.lan ", subsequently we found " brctl addif br0 $1 " in the dev-up script, which needs to be changed in "brctl addif lan $1".

You are so right, copy/paste error, fixed :) Nostrad 20:27, 14 February 2007 (UTC)

connect with >=bluez-utils-3.10.1?

My story about bluetooth. I have two modules ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter And x86_64 Desktop & 32bit Laptop. My dream was wireless internet-serfing. At notebook bluez-utils/libs work fine. All troubles are on 64 bit. The simptoms were: (in log) [hcid] Can't open system message bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The design:

1. /etc/init.d/bluetooth stop
2. skill sdpd hcid pand

temp # tar xzf /usr/portage/distfiles/bluez-utils-2.25.tar.gz temp # cd bluez-utils-2.25/ bluez-utils-2.25 # ./configure && make

1. sdpd

bluez-utils-2.25 # ./hcid/hcid

1. pand --listen --role NAP

PS now i'n thinking, how to solv pand Connect to failed. Connection timed out(110)

• pand is running on server...