public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Angel Rodriguez <jrodriguezv@telefonica.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] NAP problem
Date: Sat, 08 May 2004 10:46:03 +0200	[thread overview]
Message-ID: <409C9E4B.3070607@telefonica.net> (raw)
In-Reply-To: <1083972662.4420.156.camel@pegasus>

Marcel Holtmann wrote:

>Hi Jose,
>
>  
>
>>>>I hava a Debian Sarge PC as a NAP for a bluetooth network. The computer 
>>>>is also connected to an ADSL.
>>>>
>>>>This is my etc/network/interfaces file:
>>>># /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>>>>
>>>># The loopback interface
>>>>auto lo
>>>>iface lo inet loopback
>>>>
>>>># The first network card - this entry was created during the Debian 
>>>>installation# (network, broadcast and gateway are optional)
>>>>auto eth0
>>>>iface eth0 inet static
>>>>      address 192.168.0.2
>>>>      netmask 255.255.255.0
>>>>      network 192.168.0.0
>>>>      broadcast 192.168.0.255
>>>>      gateway 192.168.0.1
>>>>
>>>># bluetooth network server
>>>>iface bnep0 inet static
>>>>      address 10.0.0.1
>>>>      netmask 255.255.255.0
>>>>
>>>>eth0 is the ADSL connection an bnep0 is the bluetooth connection.
>>>>
>>>>My /etc/bluetooth/pan/dev-up file:
>>>>#!/bin/sh
>>>>ifup bnep0
>>>>
>>>>I think everytime a client connects it runs /etc/bluetooth/pan/dev-up. 
>>>>Everything was working fine, but after updating packages with apt-get 
>>>>everytime a client connects I have to configure bnep0 interface by hand 
>>>>(ifup bnep0).
>>>>
>>>>¿Does anybody know why /etc/bluetooth/pan/dev-up does not work now? ¿How 
>>>>can I configure bnep0 interface automaticaly?
>>>>   
>>>>
>>>>        
>>>>
>>>what about putting "auto bnep0" into the interfaces file ;)
>>>
>>>      
>>>
>>I tried this but it doesn't work. It was working fine with this 
>>interfaces file, but now :-(
>>    
>>
>
>my fault, the auto is for the boot time. You don't need any extra stuff
>and you also don't need any PAN dev-up script. Check your hotplug
>installation why it is not working. It is not a BlueZ problem.
>
>  
>
>>¿Should /etc/bluetooth/pan/dev-up run everytime a client connects? If I 
>>run that scrip manualy everythig works fine.
>>    
>>
>
>I don't know, because I never used it.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Sleepycat Software
>Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
>higher performing products faster, at low TCO.
>http://www.sleepycat.com/telcomwpreg.php?From=dnemail3
>_______________________________________________
>Bluez-users mailing list
>Bluez-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>  
>
Thank you very much for your time and your help :-)

Jose

      reply	other threads:[~2004-05-08  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-07 11:39 [Bluez-users] NAP problem Jose Angel Rodriguez
2004-05-07 16:13 ` Marcel Holtmann
     [not found]   ` <409C1B27.1050205@telefonica.net>
2004-05-07 23:31     ` Marcel Holtmann
2004-05-08  8:46       ` Jose Angel Rodriguez [this message]

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=409C9E4B.3070607@telefonica.net \
    --to=jrodriguezv@telefonica.net \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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