Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35904 - [bluez4] PAND up/down scipts are broken.
Attached to Project:
Arch Linux
Opened by Alexandr Berdnik (alexandr.berdnik) - Sunday, 23 June 2013, 18:02 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 24 November 2013, 11:16 GMT
Opened by Alexandr Berdnik (alexandr.berdnik) - Sunday, 23 June 2013, 18:02 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 24 November 2013, 11:16 GMT
|
DetailsDescription:
Interface created by pand and reported to startup scripts is not exist (possibly replaced by udev rules) Additional info: * package version(s) bluez4 4.101-3 * config and/or log files etc. Steps to reproduce: 1. create pand-up script with following content: echo "bnet interface: $1" > /tmp/pand-log ip link list > /tml/pand-log 2. start pand pand --connect xx:xx:xx:xx:xx:xx --service NAP --devup=/path/to/pand-up 3. check network interface names stored in pand-log: You will find $1 = bnep0 and something like enp0s26u1u4 in ip command output. |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 24 November 2013, 11:16 GMT
Reason for closing: Won't fix
Additional comments about closing: Bleuz4 has been dropped. Please check bluez5 stack.
Sunday, 24 November 2013, 11:16 GMT
Reason for closing: Won't fix
Additional comments about closing: Bleuz4 has been dropped. Please check bluez5 stack.