From: Alberto Garcia Hierro <tcpdevil@linuxlover.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] automatic bnep0 configuration
Date: Thu, 23 Sep 2004 04:37:12 +0200 [thread overview]
Message-ID: <200409230437.30844.tcpdevil@linuxlover.org> (raw)
In-Reply-To: <opseq1blhheocfdv@debian>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
El Jueves, 23 de Septiembre de 2004 00:12, Christoph Torens escribió:
> Hello List,
>
> I wonder if there is a way to automatically set up and
> configure the bnep0 device that comes into existing after
> a pand connection was set up. At the moment I create the
> connection and do 'ifconfig bnep0 10.10.0.5'.
> But when setting up something like a server you normally
> can't do this ifconfig by hand.
>
> I tried to configure this with /etc/network/interfaces
> but that didn't help. I also tried to set 'auto bnep0'
> but this only works at boot time, when the device is
> not there yet.
> What's the trick?
>
> By the way: thanks for all the previous help, already :-)
When a pand connection is established, /etc/bluetooth/pan/dev-up is executed,
passing args "interface baddr" (for example /etc/bluetooth/pan/dev-up bnep0
00:10:60:A2:3A:0B) . These are the scripts I use, you may find them usefull.
On the client side:
fiam@americana 100% ~ $ cat /etc/bluetooth/pan/dev-up
#!/bin/bash
if [ "$2" = "00:10:60:A2:3A:0B" ]
then
ifconfig $1 192.168.3.2
if ! ifconfig | egrep "eth0|wlan0"
then
route add default gw 192.168.3.1
fi
else
mesg y
echo "Pand connection to $2" | write fiam
mesg n
fi
And on the server side:
fiam@ignition fiam $ cat /etc/bluetooth/pan/dev-up
#!/bin/bash
PAN_IFACE=pan0
if [ -z "$1" ]
then
exit 1
fi
if ! ifconfig -a |grep ${PAN_IFACE} &> /dev/null
then
brctl addbr ${PAN_IFACE}
brctl setfd ${PAN_IFACE} 0
brctl stp ${PAN_IFACE} disable
ifconfig ${PAN_IFACE} 192.168.3.1
fi
if ! iptables -t nat -L -v | \
egrep "REDIRECT( )*tcp( )*--( )*${PAN_IFACE}
( )*any( )*anywhere( )*!192.168.232.0/24
( )*tcp( )*dpt:www( )*redir( )*ports( )*3128"
then
iptables -t nat -A PREROUTING -i ${PAN_IFACE} -p tcp -d !
192.168.3.0/24 --dport 80 -j REDIRECT --to-port 3128
fi
brctl addif ${PAN_IFACE} $1
ifconfig $1 0.0.0.0
Sorry for the ausence of comments, but I wrote these scripts yesterday and I
hadn't time to comment them. If you need further explanations, just ask :)
Regards,
Alberto
--
/* Alberto García Hierro (Skyhusker) */
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2004-09-23 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 22:12 [Bluez-users] automatic bnep0 configuration Christoph Torens
2004-09-22 22:38 ` Pavel Ruzicka
2004-09-23 2:37 ` Alberto Garcia Hierro [this message]
[not found] ` <41528C5F.70508@c-s.fr>
[not found] ` <200409231444.27391.tcpdevil@linuxlover.org>
2004-09-23 13:44 ` GUILLON Gabriel
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=200409230437.30844.tcpdevil@linuxlover.org \
--to=tcpdevil@linuxlover.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.