[Bluez-users] Setting up an hotplug connection with USB dongles

[Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Hello,

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.

Thanks,
Rainer

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Marcel Holtmann]

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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Erwin Authried]

Am Son, den 28.11.2004 schrieb Rainer Dorsch um 21:32:
> Hello,
> 
> 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.
> 
> Thanks,
> Rainer

Hi,
here is a nice description for Debian:

http://quozl.netrek.org/bluetooth/

the interfaces aren't brought up directly by ifconfig, but by a "dev-up"
script in /etc/bluetooth/pan. In addition, the "-persist" option for
pand may be useful to keep the connection up. 

-Erwin



-------------------------------------------------------
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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Hi Erwin,

thanks for that very useful link.

If have everything up an running, only two minor issues left on the PANU side:

1. It seems that I need to do an "hcitool scan" to make pand --search working, 
e.g.

              hcitool scan
              pand --nodetach --role PANU --search --encrypt 
--pidfile /var/run/pand.pid

It does work without hcitool scan, when I use the BT device address

              pand --connect <BT device address>

2. On the client side, I do not get dhcp to work. When I run 

               dhclient bnep0

I see on the PANU (from syslog):

Dec 19 23:07:42 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 5
Dec 19 23:07:42 topsi dhclient: send_packet: Network is down
Dec 19 23:07:47 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 10
Dec 19 23:07:47 topsi dhclient: send_packet: Network is down
Dec 19 23:07:49 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 10
Dec 19 23:07:49 topsi dhclient: send_packet: Network is down
Dec 19 23:07:57 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 14
Dec 19 23:07:57 topsi dhclient: send_packet: Network is down
Dec 19 23:07:59 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 1
Dec 19 23:07:59 topsi dhclient: send_packet: Network is down
Dec 19 23:08:00 topsi dhclient: No DHCPOFFERS received.
Dec 19 23:08:00 topsi dhclient: No working leases in persistent database.
Dec 19 23:08:00 topsi dhclient: Sleeping.
Dec 19 23:08:11 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 14
Dec 19 23:08:11 topsi dhclient: send_packet: Network is down
Dec 19 23:08:25 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 15
Dec 19 23:08:25 topsi dhclient: send_packet: Network is down
Dec 19 23:08:40 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
67 interval 3
Dec 19 23:08:40 topsi dhclient: send_packet: Network is down
Dec 19 23:08:43 topsi dhclient: No DHCPOFFERS received.
Dec 19 23:08:43 topsi dhclient: No working leases in persistent database.
Dec 19 23:08:44 topsi dhclient: Sleeping.

There is no entry in the syslog file in the DHCP server (which is NAP). Its 
dhcpd.conf looks like this:

# Bluetooth
subnet 192.168.2.0 netmask 255.255.255.0 {
  range 192.168.2.100 192.168.2.150;
#  option broadcast-address 204.254.239.31;
  option domain-name "vix.com";
  option domain-name-servers 192.168.2.1;
  option broadcast-address 192.168.2.255;
  option routers 192.168.2.1;
}

Any ideas are welcome.

Thanks,
Rainer


Am Montag, 29. November 2004 16:05 schrieb Erwin Authried:
> Hi,
> here is a nice description for Debian:
>
> http://quozl.netrek.org/bluetooth/
>
> the interfaces aren't brought up directly by ifconfig, but by a "dev-up"
> script in /etc/bluetooth/pan. In addition, the "-persist" option for
> pand may be useful to keep the connection up.
>
> -Erwin

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Marcel Holtmann]

Hi Rainer,

> thanks for that very useful link.
> 
> If have everything up an running, only two minor issues left on the PANU side:
> 
> 1. It seems that I need to do an "hcitool scan" to make pand --search working, 
> e.g.
> 
>               hcitool scan
>               pand --nodetach --role PANU --search --encrypt 
> --pidfile /var/run/pand.pid
> 
> It does work without hcitool scan, when I use the BT device address
> 
>               pand --connect <BT device address>
> 
> 2. On the client side, I do not get dhcp to work. When I run 
> 
>                dhclient bnep0
> 
> I see on the PANU (from syslog):
> 
> Dec 19 23:07:42 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 5
> Dec 19 23:07:42 topsi dhclient: send_packet: Network is down
> Dec 19 23:07:47 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 10
> Dec 19 23:07:47 topsi dhclient: send_packet: Network is down
> Dec 19 23:07:49 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 10
> Dec 19 23:07:49 topsi dhclient: send_packet: Network is down
> Dec 19 23:07:57 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 14
> Dec 19 23:07:57 topsi dhclient: send_packet: Network is down
> Dec 19 23:07:59 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 1
> Dec 19 23:07:59 topsi dhclient: send_packet: Network is down
> Dec 19 23:08:00 topsi dhclient: No DHCPOFFERS received.
> Dec 19 23:08:00 topsi dhclient: No working leases in persistent database.
> Dec 19 23:08:00 topsi dhclient: Sleeping.
> Dec 19 23:08:11 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 14
> Dec 19 23:08:11 topsi dhclient: send_packet: Network is down
> Dec 19 23:08:25 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 15
> Dec 19 23:08:25 topsi dhclient: send_packet: Network is down
> Dec 19 23:08:40 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255 port 
> 67 interval 3
> Dec 19 23:08:40 topsi dhclient: send_packet: Network is down
> Dec 19 23:08:43 topsi dhclient: No DHCPOFFERS received.
> Dec 19 23:08:43 topsi dhclient: No working leases in persistent database.
> Dec 19 23:08:44 topsi dhclient: Sleeping.
> 
> There is no entry in the syslog file in the DHCP server (which is NAP). Its 
> dhcpd.conf looks like this:
> 
> # Bluetooth
> subnet 192.168.2.0 netmask 255.255.255.0 {
>   range 192.168.2.100 192.168.2.150;
> #  option broadcast-address 204.254.239.31;
>   option domain-name "vix.com";
>   option domain-name-servers 192.168.2.1;
>   option broadcast-address 192.168.2.255;
>   option routers 192.168.2.1;
> }
> 
> Any ideas are welcome.

as I said, use the standard Debian stuff for configuring the network
interfaces. If you got problems setup a bridge that covers all the PAN
connections.

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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Am Sonntag, 19. Dezember 2004 23:28 schrieb Marcel Holtmann:
> Hi Rainer,
>
> > thanks for that very useful link.
> >
> > If have everything up an running, only two minor issues left on the PANU
> > side:
> >
> > 1. It seems that I need to do an "hcitool scan" to make pand --search
> > working, e.g.
> >
> >               hcitool scan
> >               pand --nodetach --role PANU --search --encrypt
> > --pidfile /var/run/pand.pid
> >
> > It does work without hcitool scan, when I use the BT device address
> >
> >               pand --connect <BT device address>
> >
> > 2. On the client side, I do not get dhcp to work. When I run
> >
> >                dhclient bnep0
> >
> > I see on the PANU (from syslog):
> >
> > Dec 19 23:07:42 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 5
> > Dec 19 23:07:42 topsi dhclient: send_packet: Network is down
> > Dec 19 23:07:47 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 10
> > Dec 19 23:07:47 topsi dhclient: send_packet: Network is down
> > Dec 19 23:07:49 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 10
> > Dec 19 23:07:49 topsi dhclient: send_packet: Network is down
> > Dec 19 23:07:57 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 14
> > Dec 19 23:07:57 topsi dhclient: send_packet: Network is down
> > Dec 19 23:07:59 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 1
> > Dec 19 23:07:59 topsi dhclient: send_packet: Network is down
> > Dec 19 23:08:00 topsi dhclient: No DHCPOFFERS received.
> > Dec 19 23:08:00 topsi dhclient: No working leases in persistent database.
> > Dec 19 23:08:00 topsi dhclient: Sleeping.
> > Dec 19 23:08:11 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 14
> > Dec 19 23:08:11 topsi dhclient: send_packet: Network is down
> > Dec 19 23:08:25 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 15
> > Dec 19 23:08:25 topsi dhclient: send_packet: Network is down
> > Dec 19 23:08:40 topsi dhclient: DHCPDISCOVER on bnep0 to 255.255.255.255
> > port 67 interval 3
> > Dec 19 23:08:40 topsi dhclient: send_packet: Network is down
> > Dec 19 23:08:43 topsi dhclient: No DHCPOFFERS received.
> > Dec 19 23:08:43 topsi dhclient: No working leases in persistent database.
> > Dec 19 23:08:44 topsi dhclient: Sleeping.
> >
> > There is no entry in the syslog file in the DHCP server (which is NAP).
> > Its dhcpd.conf looks like this:
> >
> > # Bluetooth
> > subnet 192.168.2.0 netmask 255.255.255.0 {
> >   range 192.168.2.100 192.168.2.150;
> > #  option broadcast-address 204.254.239.31;
> >   option domain-name "vix.com";
> >   option domain-name-servers 192.168.2.1;
> >   option broadcast-address 192.168.2.255;
> >   option routers 192.168.2.1;
> > }
> >
> > Any ideas are welcome.
>
> as I said, use the standard Debian stuff for configuring the network
> interfaces. If you got problems setup a bridge that covers all the PAN
> connections.
>

Marcel,

I used the Debian standard stuff (at least, as far as I am aware of it):

rd@topsi:~$ grep bnep0 /etc/network/interfaces
iface bnep0 inet dhcp
rd@topsi:~$ cat /etc/bluetooth/pan/dev-up
#!/bin/sh
echo running dev-up
ifup bnep0
rd@topsi:~$

Since this did not work, I run dhclient manually for debugging purposes.

Is there anything which is more "standard" I can do?

Thanks,
Rainer

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Marcel Holtmann]

Hi Rainer,

> I used the Debian standard stuff (at least, as far as I am aware of it):
> 
> rd@topsi:~$ grep bnep0 /etc/network/interfaces
> iface bnep0 inet dhcp

add a line with "auto bnep0" and it will bring up your interface when it
is available.

> rd@topsi:~$ cat /etc/bluetooth/pan/dev-up
> #!/bin/sh
> echo running dev-up
> ifup bnep0

Don't do it this way. Bad stuff.

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

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Hi Marcel,

thanks for the immediate reply....but somehow I must miss something:

Am Freitag, 24. Dezember 2004 13:04 schrieb Marcel Holtmann:
> Hi Rainer,
>
> > I used the Debian standard stuff (at least, as far as I am aware of it):
> >
> > rd@topsi:~$ grep bnep0 /etc/network/interfaces
> > iface bnep0 inet dhcp
>
> add a line with "auto bnep0" and it will bring up your interface when it
> is available.

=46rom man interfaces

Stanzas beginning with the word "auto" are used to identify the physical=20
interfaces to be brought up when ifup is run with the -a option.  (This
option  is  used  by  the system boot scripts.)  Physical interface names=20
should follow the word "auto" on the same line.  There can be multiple
"auto" stanzas.  ifup brings the named interfaces up in the order listed.

=46rom the ifup manpage

      -a, --all
              If given to ifup, affect all interfaces marked auto.  Interfa=
ces=20
are brought up in the order in  which  they  are  defined  in  /etc/net-
              work/interfaces.  If given to ifdown, affect all interfaces. =
=20
Interfaces are brought down in the order in which they are currently listed
              in the state file.


>
> > rd@topsi:~$ cat /etc/bluetooth/pan/dev-up
> > #!/bin/sh
> > echo running dev-up
> > ifup bnep0
>
> Don't do it this way. Bad stuff.
>

Are you suggeting to use "ifup -a" instead of "ifup bnep0"? Why would I wan=
t=20
to bring up all interaces again.


Somehow I do not get rid of the impression that I missed something...

Thanks,
Rainer

=2D-=20
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Marcel Holtmann]

Hi Rainer,

> > add a line with "auto bnep0" and it will bring up your interface when it
> > is available.
> 
> From man interfaces
> 
> Stanzas beginning with the word "auto" are used to identify the physical 
> interfaces to be brought up when ifup is run with the -a option.  (This
> option  is  used  by  the system boot scripts.)  Physical interface names 
> should follow the word "auto" on the same line.  There can be multiple
> "auto" stanzas.  ifup brings the named interfaces up in the order listed.
> 
> From the ifup manpage
> 
>       -a, --all
>               If given to ifup, affect all interfaces marked auto.  Interfaces 
> are brought up in the order in  which  they  are  defined  in  /etc/net-
>               work/interfaces.  If given to ifdown, affect all interfaces.  
> Interfaces are brought down in the order in which they are currently listed
>               in the state file.

if you use "auto bnep0" and hotplug is configured to deal also with the
network interface then bnep0 will be brought up at the time the kernel
created it. No need to run ifup/ifdown manually.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Am Sonntag, 2. Januar 2005 14:58 schrieb Marcel Holtmann:
> Hi Rainer,
>
> > > add a line with "auto bnep0" and it will bring up your interface when
> > > it is available.
> >
> > From man interfaces
> >
> > Stanzas beginning with the word "auto" are used to identify the physical
> > interfaces to be brought up when ifup is run with the -a option.  (This
> > option  is  used  by  the system boot scripts.)  Physical interface names
> > should follow the word "auto" on the same line.  There can be multiple
> > "auto" stanzas.  ifup brings the named interfaces up in the order listed.
> >
> > From the ifup manpage
> >
> >       -a, --all
> >               If given to ifup, affect all interfaces marked auto. 
> > Interfaces are brought up in the order in  which  they  are  defined  in 
> > /etc/net- work/interfaces.  If given to ifdown, affect all interfaces.
> > Interfaces are brought down in the order in which they are currently
> > listed in the state file.
>
> if you use "auto bnep0" and hotplug is configured to deal also with the
> network interface then bnep0 will be brought up at the time the kernel
> created it. No need to run ifup/ifdown manually.

Hmm....do I enable that with in /etc/default/hotplug

# NET_AGENT_POLICY
# - how to manage network interfaces with ifupdown? 'all', 'auto' or 'hotplug'
NET_AGENT_POLICY=hotplug

?

Thanks,
Rainer

>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Marcel Holtmann]

Hi Rainer,

> > if you use "auto bnep0" and hotplug is configured to deal also with the
> > network interface then bnep0 will be brought up at the time the kernel
> > created it. No need to run ifup/ifdown manually.
> 
> Hmm....do I enable that with in /etc/default/hotplug
> 
> # NET_AGENT_POLICY
> # - how to manage network interfaces with ifupdown? 'all', 'auto' or 'hotplug'
> NET_AGENT_POLICY=hotplug

I had no problem with 'hotplug', but you can also try to use 'auto'.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Hi Marcel,

Am Sonntag, 2. Januar 2005 18:41 schrieb Marcel Holtmann:
> Hi Rainer,
>
> > > if you use "auto bnep0" and hotplug is configured to deal also with the
> > > network interface then bnep0 will be brought up at the time the kernel
> > > created it. No need to run ifup/ifdown manually.
> >
> > Hmm....do I enable that with in /etc/default/hotplug
> >
> > # NET_AGENT_POLICY
> > # - how to manage network interfaces with ifupdown? 'all', 'auto' or
> > 'hotplug' NET_AGENT_POLICY=hotplug
>
> I had no problem with 'hotplug', but you can also try to use 'auto'.
>

yes, with auto it works out of the box. Setting it back to hotplug made it 
stopping working, because in my /etc/network/interfaces

mapping hotplug
  script echo
  map bnep0

was missing.

Now the interfaces come up without the ifup.

Many thanks,
Rainer

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Setting up an hotplug connection with USB dongles

[Rainer Dorsch]

Am Montag, 3. Januar 2005 11:14 schrieb Rainer Dorsch:
> Hi Marcel,
>
> Am Sonntag, 2. Januar 2005 18:41 schrieb Marcel Holtmann:
> > Hi Rainer,
> >
> > > > if you use "auto bnep0" and hotplug is configured to deal also with
> > > > the network interface then bnep0 will be brought up at the time the
> > > > kernel created it. No need to run ifup/ifdown manually.
> > >
> > > Hmm....do I enable that with in /etc/default/hotplug
> > >
> > > # NET_AGENT_POLICY
> > > # - how to manage network interfaces with ifupdown? 'all', 'auto' or
> > > 'hotplug' NET_AGENT_POLICY=hotplug
> >
> > I had no problem with 'hotplug', but you can also try to use 'auto'.
>
> yes, with auto it works out of the box. Setting it back to hotplug made it
> stopping working, because in my /etc/network/interfaces
>
> mapping hotplug
>   script echo
>   map bnep0
>
> was missing.
>
> Now the interfaces come up without the ifup.
>

I need to take that back. Only with auto I get the usb device working 
reliably...

Rainer


-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users