public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Setting up an hotplug connection with USB dongles
Date: Mon, 29 Nov 2004 02:38:31 +0100	[thread overview]
Message-ID: <1101692311.9527.10.camel@pegasus> (raw)
In-Reply-To: <200411282132.37941.rdorsch@web.de>

Hi Rainer,

> I am wondering, if there is a way to setup a hotplug connection between two 
> Linux machines using two bluetooth dongles. One of them is a NAP (with 
> Internet access) and booted first, the other box a PANU.
> 
> My problem is that I need the pand running on both sides first before I can do 
> an ifconfig for the bnep0 interface on the NAP.
> 
> 
> 
> What I did on both Debian Linux systems is:
> 
> Add a file
> 
> /etc/hotplug/usb/libbt.usermap
> 
> The file contains a line for an epox DG02A dongle
> 
> epoxbt                0x0003 0x0a12   0x0001    0x0000       0x0000       0x00         
> 0x00            0x00            0x00            0x00            0x00            
> 0x00000000
> 
> with the vendor ID (here 0x0a12) and the product ID (here 0x0001).
> 
> Then add the script epoxbt to the same directory:
> 
> # cat epoxbt
> echo "Load epox bluetooth dongle..."
> 
> modprobe bnep
> pand --master --listen --role NAP
> #
> 
> and 
> 
> topsi:~# cat /etc/hotplug/usb/epoxbt
> #!/bin/bash
> 
> echo "Load epox bluetooth dongle..."
> modprobe bnep
> pand --role PANU --connect <BT-ID>
> topsi:~#
> 
> 
> Then I do on the NAP an 
> 
> # ifconfig 192.128.2.1
> 
> and on the PANU
> 
> # dhclient
> 
> This works fine, I can access the Internet from the PANU.
> 
> 
> The problem is that the ifconfig on the NAP fails when I do not have the PANU 
> connected before....thus I can't add the network configuration part into the 
> expobt scripts.
> 
> Does anyone have an idea or pointer for that problem.

since this is Debian, don't do it like this. Use /etc/network/interfaces
and add up and down rules.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-11-29  1:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 20:32 [Bluez-users] Setting up an hotplug connection with USB dongles Rainer Dorsch
2004-11-29  1:38 ` Marcel Holtmann [this message]
2004-11-29 15:05 ` Erwin Authried
2004-12-19 22:23   ` Rainer Dorsch
2004-12-19 22:28     ` Marcel Holtmann
2004-12-23 22:43       ` Rainer Dorsch
2004-12-24 12:04         ` Marcel Holtmann
2005-01-02 13:51           ` Rainer Dorsch
2005-01-02 13:58             ` Marcel Holtmann
2005-01-02 17:37               ` Rainer Dorsch
2005-01-02 17:41                 ` Marcel Holtmann
2005-01-03 10:14                   ` Rainer Dorsch
2005-01-03 10:42                     ` Rainer Dorsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1101692311.9527.10.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox