| 2009-03-01 22:34:18 |
Jack Coulter |
bug |
|
|
added bug |
| 2009-03-02 00:23:52 |
Jack Coulter |
description |
When Network Access Point local service is enabled, and dnsmasq is used as the DHCP server, it appears to attempt to bind to interfaces other than the bluetooth PAN bridge (ifname panX where X = 0-255)
This causes conflicts if dnsmasq is already running for other purposes. I get the following error:
"dnsmasq: failed to bind listening socket for ::1: Address already in use"
For example, virt-manager uses dnsmasq, but binds only to virbr0, and thus can coexist with dnsmasq running on other interfaces. I also have another instance of dnsmasq running and bound to eth0, wlan0, this coexists with the instance listening on virbr0.
Blueman should pass --interface=panX when it runs dnsmasq to avoid conflicts with a listening DHCP server on other interfaces |
When Network Access Point local service is enabled, and dnsmasq is used as the DHCP server, the --bind-interfaces option is not used, this causes the instance of dnsmasq created by Blueman to conflict with any other instances, even those listening on different interfaces.
This results in the following error:
"dnsmasq: failed to bind listening socket for ::1: Address already in use"
For example, virt-manager uses dnsmasq, but binds only to virbr0 and uses the --bind-interfaces, and thus can coexist with dnsmasq running on other interfaces. I also have another instance of dnsmasq running and bound to eth0, wlan0 (again with --bind-interfaces), this coexists with the instance listening on virbr0.
The fix for this would be for blueman to pass --bind-interfaces to dnsmasq |
|
| 2009-03-02 01:29:47 |
Jack Coulter |
bug |
|
|
added attachment 'blueman.diff' (blueman.diff) |
| 2009-03-02 01:31:18 |
Jack Coulter |
description |
When Network Access Point local service is enabled, and dnsmasq is used as the DHCP server, the --bind-interfaces option is not used, this causes the instance of dnsmasq created by Blueman to conflict with any other instances, even those listening on different interfaces.
This results in the following error:
"dnsmasq: failed to bind listening socket for ::1: Address already in use"
For example, virt-manager uses dnsmasq, but binds only to virbr0 and uses the --bind-interfaces, and thus can coexist with dnsmasq running on other interfaces. I also have another instance of dnsmasq running and bound to eth0, wlan0 (again with --bind-interfaces), this coexists with the instance listening on virbr0.
The fix for this would be for blueman to pass --bind-interfaces to dnsmasq |
When Network Access Point local service is enabled, and dnsmasq is used as the DHCP server, the --bind-interfaces option is not used, this causes the instance of dnsmasq created by Blueman to conflict with any other instances, even those listening on different interfaces.
This results in the following error:
"dnsmasq: failed to bind listening socket for ::1: Address already in use"
For example, virt-manager uses dnsmasq, but binds only to virbr0 and uses the --bind-interfaces and --except-interface=lo, and thus can coexist with dnsmasq running on other interfaces. I also have another instance of dnsmasq running and bound to eth0, wlan0 (again with --bind-interfaces), this coexists with the instance listening on virbr0.
The fix for this would be for blueman to pass --bind-interfaces and --except-interface=lo to dnsmasq. |
|
| 2009-03-02 07:14:53 |
Valmantas Palikša |
blueman: status |
New |
Fix Committed |
|
| 2009-03-02 07:14:53 |
Valmantas Palikša |
blueman: statusexplanation |
|
|
|
| 2009-10-30 22:54:08 |
Roland Hieber |
removed subscriber Roland Hieber |
|
|
|
| 2011-01-12 09:04:45 |
MF |
blueman: status |
Fix Committed |
Incomplete |
|
| 2011-01-12 09:05:12 |
MF |
blueman: status |
Incomplete |
In Progress |
|
| 2011-06-29 20:38:15 |
papukaija |
tags |
|
patch |
|
| 2014-03-22 02:57:53 |
evert de la rambelje |
bug task added |
|
boot-repair-xubuntu (nUbuntu) |
|
