9:11 a.m.
I'm trying to make my Edison board connect to my cell phone. The cell
phone is set to do tethering over bluetooth.
I can connect my PC (which uses network-manager) to the phone . So the
phone side configuration seems to be working fine.
Also, on the Edison side I can pair/trust/connect bluetooth to the phone
fine, or I can connect to the Edison from the phone side. In neither
case does a bluetooth service appear in connmanctl. In connmanctl I ahve
a bluetooth technology and can power it on/off fine.
Does anybody know what I am doing wrong here? Any suggestions are welcomed.
Note the Edison is not running it's factory firmware, but a rather
recent Yocto Sumo.
root@edison:~# uname -a
Linux edison 4.20.0-rc5-edison-acpi-standard #1 SMP Wed Dec 5 21:29:04
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@edison:~# bluetoothctl -v
bluetoothctl: 5.48
root@edison:~# /usr/sbin/connmand -v
1.35
6:27 a.m.
On 12/23/18 11:11 AM, Ferry Toth wrote:
I'm trying to make my Edison board connect to my cell phone. The
cell
phone is set to do tethering over bluetooth.
I can connect my PC (which uses network-manager) to the phone . So the
phone side configuration seems to be working fine.
Also, on the Edison side I can pair/trust/connect bluetooth to the phone
fine, or I can connect to the Edison from the phone side. In neither
case does a bluetooth service appear in connmanctl. In connmanctl I ahve
a bluetooth technology and can power it on/off fine.
Does anybody know what I am doing wrong here? Any suggestions are welcomed.
Note the Edison is not running it's factory firmware, but a rather
recent Yocto Sumo.
root@edison:~# uname -a
Linux edison 4.20.0-rc5-edison-acpi-standard #1 SMP Wed Dec 5 21:29:04
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@edison:~# bluetoothctl -v
bluetoothctl: 5.48
root@edison:~# /usr/sbin/connmand -v
1.35
If you paired the phone and the Edison before tethering was enabled, you
may need to remove the phone from the Bluetooth on the Edison and then
re-pair it. You can also use bluetoothctl to see a list of service UUIDs
for the phone to make sure that one of the possible 3 PAN services is
there. If the phone uses the DUN profile instead of PAN, I'm not sure
that it will work with ConnMan.
11:39 a.m.
Op 06-01-19 om 18:40 schreef Ferry Toth:
Hello David,
Op 03-01-19 om 15:27 schreef David Lechner:
> On 12/23/18 11:11 AM, Ferry Toth wrote:
>> I'm trying to make my Edison board connect to my cell phone. The cell phone
>> is set to do tethering over bluetooth.
>>
>> I can connect my PC (which uses network-manager) to the phone . So the phone
>> side configuration seems to be working fine.
>>
>> Also, on the Edison side I can pair/trust/connect bluetooth to the phone
>> fine, or I can connect to the Edison from the phone side. In neither case
>> does a bluetooth service appear in connmanctl. In connmanctl I ahve a
>> bluetooth technology and can power it on/off fine.
>>
>> Does anybody know what I am doing wrong here? Any suggestions are welcomed.
>>
>> Note the Edison is not running it's factory firmware, but a rather recent
>> Yocto Sumo.
>>
>> root@edison:~# uname -a
>> Linux edison 4.20.0-rc5-edison-acpi-standard #1 SMP Wed Dec 5 21:29:04 UTC
>> 2018 x86_64 x86_64 x86_64 GNU/Linux
>> root@edison:~# bluetoothctl -v
>> bluetoothctl: 5.48
>> root@edison:~# /usr/sbin/connmand -v
>> 1.35
> If you paired the phone and the Edison before tethering was enabled, you may
> need to remove the phone from the Bluetooth on the Edison and then re-pair it.
> You can also use bluetoothctl to see a list of service UUIDs for the phone to
> make sure that one of the possible 3 PAN services is there. If the phone uses
> the DUN profile instead of PAN, I'm not sure that it will work with ConnMan.
I tried your advice and removed the phone, switched tethering on the phone on,
then re-paired, without success.
Info for the phone:
[Ferry Toth (Galaxy Note3)]# info [ 5491.759797] Bluetooth: hci0: last event is
not cmd complete (0x0f)
C4:62:EA:01:AF:74
Device C4:62:EA:01:AF:74 (public)
Name: Ferry Toth (Galaxy Note3)
Alias: Ferry Toth (Galaxy Note3)
Class: 0x005a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v0075p0100d0200
RSSI: -55
Edison controller:
Controller 43:34:1B:00:1F:AC (public)
Name: edison
Alias: edison
Class: 0x00200110
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: yes
Connman services:
connmanctl> services
*AO Wired ethernet_00800f951d4d_cable
OP35_Extra wifi_784b87ad4d70_4f5033355f4578747261_managed_psk
Oranje Plantage 35 2.4G
wifi_784b87ad4d70_4f72616e6a6520506c616e7461676520333520322e3447_managed_psk
ANNE wifi_784b87ad4d70_414e4e45_managed_psk
Wifi wifi_784b87ad4d70_57696669_managed_psk
wifi_784b87ad4d70_hidden_managed_psk
Ziggo63D6178 wifi_784b87ad4d70_5a6967676f36334436313738_managed_psk
Ziggo2973930 wifi_784b87ad4d70_5a6967676f32393733393330_managed_psk
I made some progress. It appears I needed to build bluez5 with
--enable-network. Now I get:
[Ferry Toth (Galaxy Note3)]# show
Controller 43:34:1B:00:1F:AC (public)
Name: edison
Alias: edison
Class: 0x00200110
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: no
root@edison:~# connmanctl
connmanctl> services
*AR Wired ethernet_00800f951d4d_cable
Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
Input/output error
Seems like 1 more thing is missing.
7:51 a.m.
root@edison:~# connmanctl
connmanctl> services
*AR Wired ethernet_00800f951d4d_cable
Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
Input/output error
Seems like 1 more thing is missing.
Something interesting in the logs?
2:41 p.m.
Op 09-01-19 om 16:51 schreef Daniel Wagner:
> root@edison:~# connmanctl
> connmanctl> services
> *AR Wired ethernet_00800f951d4d_cable
> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
> Input/output error
>
> Seems like 1 more thing is missing.
Something interesting in the logs?
Maybe. bnep0 is not appearing.
bnep0: Could not find udev device: No such device
bnep0: Failed
Could not add new link, ignoring: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
5:43 a.m.
Op 11-01-19 om 23:41 schreef Ferry Toth:
Op 09-01-19 om 16:51 schreef Daniel Wagner:
>> root@edison:~# connmanctl
>> connmanctl> services
>> *AR Wired ethernet_00800f951d4d_cable
>> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
>> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
>> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
>> Input/output error
>>
>> Seems like 1 more thing is missing.
> Something interesting in the logs?
Maybe. bnep0 is not appearing.
bnep0: Could not find udev device: No such device
bnep0: Failed
Could not add new link, ignoring: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
link_config: autonegotiation is unset or enabled, the speed and duplex
are not writable.
link_config: could not get ethtool features for bnep0
Could not set offload features of bnep0: No such device
After turning on -d I got a bit more:
../connman-1.35/src/service.c:service_send_changed()
***
../connman-1.35/src/service.c:service_append_added_foreach() changed
/net/connman/service/bluetooth_43341B001FAC_C462EA01AF74
***
../connman-1.35/src/rtnl.c:rtnl_message() NEWLINK len 1316 type 16 flags
0x0000 seq 0 pid 0
../connman-1.35/src/ipconfig.c:__connman_ipconfig_newlink() index 10
bnep0 {create} index 10 type 1 <ETHER>
bnep0 {update} flags 4098 <DOWN>
bnep0 {newlink} index 10 address 43:34:1B:00:1F:AC mtu 1500
bnep0 {newlink} index 10 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_newlink() type 1 index 10
Adding interface bnep0 [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/src/rtnl.c:rtnl_message() DELLINK len 560 type 17 flags
0x0000 seq 0 pid 0
bnep0 {dellink} index 10 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_dellink() type 1 index 10
../connman-1.35/src/ipconfig.c:__connman_ipconfig_dellink() index 10
(null) {remove} index 10
Remove interface (null) [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/plugins/bluetooth.c:pan_connect_cb() network 0x1887450
org.bluez.Error.Failed
../connman-1.35/src/network.c:connman_network_set_associating() network
0x1887450 associating 0
../connman-1.35/src/network.c:connman_network_set_error() network
0x1887450 error 1
../connman-1.35/src/service.c:__connman_service_indicate_error() service
0x1887540 error 4
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x1887540 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 1 (IPv4)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x18878f0
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x1887540
old association - new failure/association => association
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x1887540 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 2 (IPv6)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x1887960
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x1887540
old association - new failure/failure => failure
../connman-1.35/src/session.c:service_state_changed() service 0x1887540
state 7
../connman-1.35/src/provider.c:provider_service_changed() service
0x1887540 bluetooth_43341B001FAC_C462EA01AF74 state 7 index 0/-1
../connman-1.35/src/agent.c:connman_agent_report_error_full() agent
0x188acb0 sender :1.33 context 0x1887540 path /net/connman/connmanctl3155
../connman-1.35/src/agent.c:connman_agent_queue_message() driver 0x59f82c
../connman-1.35/src/service.c:connman_service_ref_debug() 0x1887540 ref
2 by ../connman-1.35/src/service.c:7296:agent_context_ref()
../connman-1.35/src/network.c:__connman_network_disconnect() network
0x1887450
../connman-1.35/plugins/bluetooth.c:bluetooth_pan_disconnect() network
0x1887450
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network
0x1887450 org.bluez.Error.NotConnected
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network 0x1887450
6:27 a.m.
I missed some stuff in the log see below.
Op 12-01-19 om 14:43 schreef Ferry Toth:
Op 11-01-19 om 23:41 schreef Ferry Toth:
>
> Op 09-01-19 om 16:51 schreef Daniel Wagner:
>>> root@edison:~# connmanctl
>>> connmanctl> services
>>> *AR Wired ethernet_00800f951d4d_cable
>>> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
>>> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
>>> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
>>> Input/output error
>>>
>>> Seems like 1 more thing is missing.
>> Something interesting in the logs?
>
> Maybe. bnep0 is not appearing.
>
>
> bnep0: Could not find udev device: No such device
> bnep0: Failed
> Could not add new link, ignoring: No such device
> link_config: autonegotiation is unset or enabled, the speed and
> duplex are not writable.
> link_config: could not get ethtool features for bnep0
> Could not set offload features of bnep0: No such device
> link_config: autonegotiation is unset or enabled, the speed and
> duplex are not writable.
> link_config: could not get ethtool features for bnep0
> Could not set offload features of bnep0: No such device
> link_config: autonegotiation is unset or enabled, the speed and
> duplex are not writable.
> link_config: could not get ethtool features for bnep0
> Could not set offload features of bnep0: No such device
> link_config: autonegotiation is unset or enabled, the speed and
> duplex are not writable.
> link_config: could not get ethtool features for bnep0
> Could not set offload features of bnep0: No such device
After turning on -d I got a bit more:
../connman-1.35/src/service.c:service_send_changed()
***
../connman-1.35/src/service.c:service_append_added_foreach() changed
/net/connman/service/bluetooth_43341B001FAC_C462EA01AF74
***
../connman-1.35/src/rtnl.c:rtnl_message() NEWLINK len 1316 type 16
flags 0x0000 seq 0 pid 0
../connman-1.35/src/ipconfig.c:__connman_ipconfig_newlink() index 10
bnep0 {create} index 10 type 1 <ETHER>
bnep0 {update} flags 4098 <DOWN>
bnep0 {newlink} index 10 address 43:34:1B:00:1F:AC mtu 1500
bnep0 {newlink} index 10 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_newlink() type 1 index 10
Adding interface bnep0 [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/src/rtnl.c:rtnl_message() DELLINK len 560 type 17
flags 0x0000 seq 0 pid 0
bnep0 {dellink} index 10 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_dellink() type 1 index 10
../connman-1.35/src/ipconfig.c:__connman_ipconfig_dellink() index 10
(null) {remove} index 10
Remove interface (null) [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/plugins/bluetooth.c:pan_connect_cb() network 0x1887450
org.bluez.Error.Failed
../connman-1.35/src/network.c:connman_network_set_associating()
network 0x1887450 associating 0
../connman-1.35/src/network.c:connman_network_set_error() network
0x1887450 error 1
../connman-1.35/src/service.c:__connman_service_indicate_error()
service 0x1887540 error 4
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x1887540 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 1 (IPv4)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x18878f0
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service
0x1887540 old association - new failure/association => association
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x1887540 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 2 (IPv6)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x1887960
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service
0x1887540 old association - new failure/failure => failure
../connman-1.35/src/session.c:service_state_changed() service
0x1887540 state 7
../connman-1.35/src/provider.c:provider_service_changed() service
0x1887540 bluetooth_43341B001FAC_C462EA01AF74 state 7 index 0/-1
../connman-1.35/src/agent.c:connman_agent_report_error_full() agent
0x188acb0 sender :1.33 context 0x1887540 path /net/connman/connmanctl3155
../connman-1.35/src/agent.c:connman_agent_queue_message() driver 0x59f82c
../connman-1.35/src/service.c:connman_service_ref_debug() 0x1887540
ref 2 by ../connman-1.35/src/service.c:7296:agent_context_ref()
../connman-1.35/src/network.c:__connman_network_disconnect() network
0x1887450
../connman-1.35/plugins/bluetooth.c:bluetooth_pan_disconnect() network
0x1887450
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network
0x1887450 org.bluez.Error.NotConnected
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network 0x1887450
../connman-1.35/src/service.c:connect_service() service 0x8f9ad0
../connman-1.35/src/service.c:__connman_service_connect() service
0x8f9ad0 state idle connect reason none -> user
../connman-1.35/src/service.c:__connman_service_clear_error() service
0x8f9ad0
../connman-1.35/src/stats.c:__connman_stats_service_register() service
0x8f9ad0
../connman-1.35/src/stats.c:stats_open() file 0x8f5840 name
/var/lib/connman/bluetooth_43341B001FAC_C462EA01AF74/data
../connman-1.35/src/stats.c:stats_file_setup() file 0x8f5840 fd 24 name
/var/lib/connman/bluetooth_43341B001FAC_C462EA01AF74/data
../connman-1.35/src/stats.c:stats_file_remap() file 0x8f5840 size 4096
addr (nil) len 0
../connman-1.35/src/network.c:__connman_network_connect() network 0x8f99e0
../connman-1.35/src/device.c:__connman_device_disconnect() device 0x8f3d10
Skipping disconnect of C462EA01AF74, network is connecting.
../connman-1.35/plugins/bluetooth.c:bluetooth_pan_connect() network 0x8f99e0
../connman-1.35/src/network.c:connman_network_set_associating() network
0x8f99e0 associating 1
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x8f9ad0 (bluetooth_43341B001FAC_C462EA01AF74) old state 1
(idle) new state 2 (association) type 1 (IPv4)
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x8f9ad0
old idle - new association/idle => association
../connman-1.35/src/session.c:service_state_changed() service 0x8f9ad0
state 2
../connman-1.35/src/connection.c:__connman_connection_update_gateway()
default 0x8f1200
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x8f9ad0 (bluetooth_43341B001FAC_C462EA01AF74) old state 1
(idle) new state 2 (association) type 2 (IPv6)
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x8f9ad0
old association - new association/association => association
../connman-1.35/src/network.c:connman_network_set_associating() network
0x8f99e0 associating 1
../connman-1.35/src/service.c:__connman_service_connect() service
0x8f9ad0 err -115
***
../connman-1.35/src/ipconfig.c:__connman_ipconfig_newlink() index 12
bnep0 {create} index 12 type 1 <ETHER>
bnep0 {update} flags 4098 <DOWN>
bnep0 {newlink} index 12 address 43:34:1B:00:1F:AC mtu 1500
bnep0 {newlink} index 12 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_newlink() type 1 index 12
Adding interface bnep0 [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/src/rtnl.c:rtnl_message() DELLINK len 560 type 17 flags
0x0000 seq 0 pid 0
bnep0 {dellink} index 12 operstate 2 <DOWN>
../connman-1.35/src/detect.c:detect_dellink() type 1 index 12
../connman-1.35/src/ipconfig.c:__connman_ipconfig_dellink() index 12
(null) {remove} index 12
Remove interface (null) [ bluetooth ]
../connman-1.35/src/technology.c:technology_find() type 4
../connman-1.35/plugins/bluetooth.c:pan_connect_cb() network 0x8f99e0
org.bluez.Error.Failed
../connman-1.35/src/network.c:connman_network_set_associating() network
0x8f99e0 associating 0
../connman-1.35/src/network.c:connman_network_set_error() network
0x8f99e0 error 1
../connman-1.35/src/service.c:__connman_service_indicate_error() service
0x8f9ad0 error 4
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x8f9ad0 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 1 (IPv4)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x8f9e80
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x8f9ad0
old association - new failure/association => association
../connman-1.35/src/service.c:__connman_service_ipconfig_indicate_state()
service 0x8f9ad0 (bluetooth_43341B001FAC_C462EA01AF74) old state 2
(association) new state 7 (failure) type 2 (IPv6)
../connman-1.35/src/ipconfig.c:__connman_ipconfig_disable() ipconfig
0x8f9ef0
../connman-1.35/src/ntp.c:__connman_ntp_stop()
../connman-1.35/src/service.c:service_indicate_state() service 0x8f9ad0
old association - new failure/failure => failure
../connman-1.35/src/session.c:service_state_changed() service 0x8f9ad0
state 7
../connman-1.35/src/provider.c:provider_service_changed() service
0x8f9ad0 bluetooth_43341B001FAC_C462EA01AF74 state 7 index 0/-1
../connman-1.35/src/agent.c:connman_agent_report_error_full() agent
0x8e3bb0 sender :1.56 context 0x8f9ad0 path /net/connman/connmanctl3435
../connman-1.35/src/agent.c:connman_agent_queue_message() driver 0x51682c
../connman-1.35/src/service.c:connman_service_ref_debug() 0x8f9ad0 ref 2
by ../connman-1.35/src/service.c:7296:agent_context_ref()
../connman-1.35/src/network.c:__connman_network_disconnect() network
0x8f99e0
../connman-1.35/plugins/bluetooth.c:bluetooth_pan_disconnect() network
0x8f99e0
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network 0x8f99e0
org.bluez.Error.NotConnected
../connman-1.35/plugins/bluetooth.c:pan_disconnect_cb() network 0x8f99e0
../connman-1.35/src/network.c:connman_network_set_connected() network
0x8f99e0 connected 0/0 connecting 0 associating 0
../connman-1.35/src/dhcpv6.c:timeout_info_req() info RT timeout 112381 msec
12:22 p.m.
Op 09-01-19 om 16:51 schreef Daniel Wagner:
> root@edison:~# connmanctl
> connmanctl> services
> *AR Wired ethernet_00800f951d4d_cable
> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
> Input/output error
>
> Seems like 1 more thing is missing.
Something interesting in the logs?
I posted debug logs. Did you have a look?
7:49 p.m.
On 1/29/19 2:22 PM, Ferry Toth wrote:
Op 09-01-19 om 16:51 schreef Daniel Wagner:
>> root@edison:~# connmanctl
>> connmanctl> services
>> *AR Wired ethernet_00800f951d4d_cable
>> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
>> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
>> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
>> Input/output error
>>
>> Seems like 1 more thing is missing.
> Something interesting in the logs?
I posted debug logs. Did you have a look?
I had a look, but I didn't see anything helpful. Sorry.
Maybe there is something in the BlueZ/bluetoothd logs?
Maybe you are missing a kernel option that needs to be
enabled for ConnMan or BlueZ?
11:51 a.m.
On Tue, Jan 29, 2019 at 09:49:13PM -0600, David Lechner wrote:
On 1/29/19 2:22 PM, Ferry Toth wrote:
>
> Op 09-01-19 om 16:51 schreef Daniel Wagner:
> > > root@edison:~# connmanctl
> > > connmanctl> services
> > > *AR Wired ethernet_00800f951d4d_cable
> > > Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
> > > connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
> > > Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
> > > Input/output error
> > >
> > > Seems like 1 more thing is missing.
> > Something interesting in the logs?
> I posted debug logs. Did you have a look?
I had a look, but I didn't see anything helpful. Sorry.
Me neither.
Maybe there is something in the BlueZ/bluetoothd logs?
Maybe you are missing a kernel option that needs to be
enabled for ConnMan or BlueZ?
Hmm, good idea. If it would be oFono my tip would CONFIG_TUN. Almost :(
Thanks,
Daniel
2:01 p.m.
Op 14-02-19 om 20:51 schreef Daniel Wagner:
On Tue, Jan 29, 2019 at 09:49:13PM -0600, David Lechner wrote:
> On 1/29/19 2:22 PM, Ferry Toth wrote:
>> Op 09-01-19 om 16:51 schreef Daniel Wagner:
>>>> root@edison:~# connmanctl
>>>> connmanctl> services
>>>> *AR Wired ethernet_00800f951d4d_cable
>>>> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
>>>> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
>>>> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
>>>> Input/output error
>>>>
>>>> Seems like 1 more thing is missing.
>>> Something interesting in the logs?
>> I posted debug logs. Did you have a look?
> I had a look, but I didn't see anything helpful. Sorry.
Me neither.
> Maybe there is something in the BlueZ/bluetoothd logs?
>
> Maybe you are missing a kernel option that needs to be
> enabled for ConnMan or BlueZ?
I have read the parts relating to the kernel
config. I think I have
everything. But then again, it's not working.
Hmm, good idea. If it would be oFono my tip would CONFIG_TUN. Almost
:(
Could d-bus be blocking something? This my bluetooth.conf:
<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration
1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some
holes -->
<policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent1"/>
<allow send_interface="org.bluez.MediaEndpoint1"/>
<allow send_interface="org.bluez.MediaPlayer1"/>
<allow send_interface="org.bluez.Profile1"/>
<allow send_interface="org.bluez.GattCharacteristic1"/>
<allow send_interface="org.bluez.GattDescriptor1"/>
<allow send_interface="org.bluez.LEAdvertisement1"/>
<allow send_interface="org.freedesktop.DBus.ObjectManager"/>
<allow send_interface="org.freedesktop.DBus.Properties"/>
</policy>
<policy at_console="true">
<allow send_destination="org.bluez"/>
</policy>
<!-- allow users of lp group (printing subsystem) to
communicate with bluetoothd -->
<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>
<policy context="default">
<deny send_destination="org.bluez"/>
</policy>
</busconfig>
Thanks,
Daniel
6:02 a.m.
Op 14-02-19 om 23:01 schreef Ferry Toth:
Op 14-02-19 om 20:51 schreef Daniel Wagner:
> On Tue, Jan 29, 2019 at 09:49:13PM -0600, David Lechner wrote:
>> On 1/29/19 2:22 PM, Ferry Toth wrote:
>>> Op 09-01-19 om 16:51 schreef Daniel Wagner:
>>>>> root@edison:~# connmanctl
>>>>> connmanctl> services
>>>>> *AR Wired ethernet_00800f951d4d_cable
>>>>> Ferry Toth (Galaxy Note3) bluetooth_43341B001FAC_C462EA01AF74
>>>>> connmanctl> connect bluetooth_43341B001FAC_C462EA01AF74
>>>>> Error /net/connman/service/bluetooth_43341B001FAC_C462EA01AF74:
>>>>> Input/output error
>>>>>
>>>>> Seems like 1 more thing is missing.
>>>> Something interesting in the logs?
>>> I posted debug logs. Did you have a look?
>> I had a look, but I didn't see anything helpful. Sorry.
> Me neither.
>
>> Maybe there is something in the BlueZ/bluetoothd logs?
>>
>> Maybe you are missing a kernel option that needs to be
>> enabled for ConnMan or BlueZ?
I have read the parts relating to the kernel config. I think I have
everything. But then again, it's not working.
> Hmm, good idea. If it would be oFono my tip would CONFIG_TUN. Almost :(
Could d-bus be blocking something? This my bluetooth.conf:
<!-- This configuration file specifies the required security policies
for Bluetooth core daemon to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus
Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- ../system.conf have denied everything, so we just punch some
holes -->
<policy user="root">
<allow own="org.bluez"/>
<allow send_destination="org.bluez"/>
<allow send_interface="org.bluez.Agent1"/>
<allow send_interface="org.bluez.MediaEndpoint1"/>
<allow send_interface="org.bluez.MediaPlayer1"/>
<allow send_interface="org.bluez.Profile1"/>
<allow send_interface="org.bluez.GattCharacteristic1"/>
<allow send_interface="org.bluez.GattDescriptor1"/>
<allow send_interface="org.bluez.LEAdvertisement1"/>
<allow send_interface="org.freedesktop.DBus.ObjectManager"/>
<allow send_interface="org.freedesktop.DBus.Properties"/>
</policy>
<policy at_console="true">
<allow send_destination="org.bluez"/>
</policy>
<!-- allow users of lp group (printing subsystem) to
communicate with bluetoothd -->
<policy group="lp">
<allow send_destination="org.bluez"/>
</policy>
<policy context="default">
<deny send_destination="org.bluez"/>
</policy>
</busconfig>
Solved this, thanks Andy Shevchenko.
It appears on Edison (and some other BT devices too), bd_addr is not
stored in OTP. For instance on Edison it is stored in a partition on the
eMMC (/factory). The bcm driver (BCM43341B0) bases the default bd_addr
on the chip (43:34:1B:00:1F:AC), which is fine for most BT services, but
apparently not for pan/nap. It seems like the bnep device is created and
then immediately removed again. The only thing missing is error handling
of this case.
Using the bdaddr tool to set the address makes connman connect to
bluetooth service without problems.
> Thanks,
> Daniel
10:32 a.m.
Hi Ferry,
Solved this, thanks Andy Shevchenko.
It appears on Edison (and some other BT devices too), bd_addr is not
stored in OTP. For instance on Edison it is stored in a partition on the
eMMC (/factory). The bcm driver (BCM43341B0) bases the default bd_addr
on the chip (43:34:1B:00:1F:AC), which is fine for most BT services, but
apparently not for pan/nap. It seems like the bnep device is created and
then immediately removed again. The only thing missing is error handling
of this case.
Using the bdaddr tool to set the address makes connman connect to
bluetooth service without problems.
Thanks for the feedback.
If I am not completely mistaken, 43:34:1B:00:1F:AC says it is locally
administered address, so you can't reach any routed network.
Thanks,
Daniel
597
days inactive
674
days old
13 comments
3 participants
participants (3)
-
Daniel Wagner -
David Lechner -
Ferry Toth