You are not logged in.
Having sorted out the (so I thought) most difficult part of setting up Bluetooth PAN networking, I am at the stage of being able to make a PAN connection from an Android phone to my Arch machine, which causes a new interface "bnep0" to appear:
[root@alarm ~]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP. mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether c8:a0:30:ae:19:26 brd ff:ff:ff:ff:ff:ff
3: pan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
link/ether 00:19:45:44:16:33 brd ff:ff:ff:ff:ff:ff
4: bnep0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master pan0 state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 00:19:45:44:16:33 brd ff:ff:ff:ff:ff:ff
pan0 is a "skeleton" interface created using "brctl addbr", which is then used to provide an org.bluez.NetworkServer for PAN clients to connect to.
My question is: how can I configure the system (using a config file /etc/netctl/bnep0? or some other way?) so that bnep0 is automatically assigned a static IPv4 address when it comes up?
I have a working /etc/netctl/eth0 config. file that assigns a static IP address, gateway, nameserver etc. to eth0, and I've tried various modifications of that file as /etc/netctl/bnep0 (e.g. connection type "bridge" or "dummy" instead of "ethernet"), but without success so far.
thanks,
Mike
Last edited by MikeH (2014-02-26 08:35:20)
Offline
Having sorted out the (so I thought) most difficult part of setting up Bluetooth PAN networking, I am at the stage of being able to make a PAN connection from an Android phone to my Arch machine, which causes a new interface "bnep0" to appear:
[root@alarm ~]# ip link show 1: lo: <LOOPBACK,UP,LOWER_UP. mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether c8:a0:30:ae:19:26 brd ff:ff:ff:ff:ff:ff 3: pan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether 00:19:45:44:16:33 brd ff:ff:ff:ff:ff:ff 4: bnep0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master pan0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 00:19:45:44:16:33 brd ff:ff:ff:ff:ff:ff
pan0 is a "skeleton" interface created using "brctl addbr", which is then used to provide an org.bluez.NetworkServer for PAN clients to connect to.
My question is: how can I configure the system (using a config file /etc/netctl/bnep0? or some other way?) so that bnep0 is automatically assigned a static IPv4 address when it comes up?
I have a working /etc/netctl/eth0 config. file that assigns a static IP address, gateway, nameserver etc. to eth0, and I've tried various modifications of that file as /etc/netctl/bnep0 (e.g. connection type "bridge" or "dummy" instead of "ethernet"), but without success so far.
thanks,
Mike
Hello.
I’m also trying to set up a Bluetooth tethering with my smartphone but every guide I’ve found are deprecated (using bluez4 and pand), please, could you explain me what have you do to have pan0 and bnep0
Interfaces "woke up"?.
Thanks
Offline