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

[Rainer Dorsch <rdorsch@web.de>]

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