03-06-2019, 04:15 AM
@Kent
My phone is a Sony Xperia Z5 Compact E5823 running Android 7.11.
My laptop runs Ubuntu 18.04. I re-compiled pulseaudio to use the correct RTP, so that's working now.
Both devices connect fine once they are set to "trusted" the first time. The hassle is really getting the "trust" into bluez after the initial pairing (or after explicitly un-pairing them in moode). Once the trust is established, re-connecting works like a charm. Getting moode's bluez to "trust" a device it has never seen before requires the strange procedure of pairing, scanning and reconnecting until it works for the first time.
Regarding the ssh issue: the moode RPi is connected via Wifi, so is my Ubuntu Laptop. I also have another RPi running libreElec which is connected to the router using an ethernet cable. I can ssh from the laptop to libreElec and from libreElec to moode without issues. Laptop to moode is sketchy and tends to fail almost always with ssh sessions that request a terminal (-t). It appears to be related to Wifi to Wifi somehow. I initially jumped to the MTU issue because I've seen similar hang-behaviour being caused by too high MTU settings and ICMP messages being filtered by firewalls that are too eager. Also, when I first lowered the MTU on the moode box, it appeared solved at first. But the next day it caused trouble even with lowered MTU and sometimes it worked with high MTU and lots of data being transferred. Thus, now, I don't think, it's the MTU. I've seen some posts on the internet that hint towards IPQos settings for ssh. And, of course, I also need to double check that my Laptop on a cable works fine.
In any case, an annoying (yet interesting) problem. I'm keen to get to the bottom of it, but for now, I have the workaround to use the libreElec box as a proxy, so other issues have a higher priority.
My phone is a Sony Xperia Z5 Compact E5823 running Android 7.11.
My laptop runs Ubuntu 18.04. I re-compiled pulseaudio to use the correct RTP, so that's working now.
Both devices connect fine once they are set to "trusted" the first time. The hassle is really getting the "trust" into bluez after the initial pairing (or after explicitly un-pairing them in moode). Once the trust is established, re-connecting works like a charm. Getting moode's bluez to "trust" a device it has never seen before requires the strange procedure of pairing, scanning and reconnecting until it works for the first time.
Regarding the ssh issue: the moode RPi is connected via Wifi, so is my Ubuntu Laptop. I also have another RPi running libreElec which is connected to the router using an ethernet cable. I can ssh from the laptop to libreElec and from libreElec to moode without issues. Laptop to moode is sketchy and tends to fail almost always with ssh sessions that request a terminal (-t). It appears to be related to Wifi to Wifi somehow. I initially jumped to the MTU issue because I've seen similar hang-behaviour being caused by too high MTU settings and ICMP messages being filtered by firewalls that are too eager. Also, when I first lowered the MTU on the moode box, it appeared solved at first. But the next day it caused trouble even with lowered MTU and sometimes it worked with high MTU and lots of data being transferred. Thus, now, I don't think, it's the MTU. I've seen some posts on the internet that hint towards IPQos settings for ssh. And, of course, I also need to double check that my Laptop on a cable works fine.
In any case, an annoying (yet interesting) problem. I'm keen to get to the bottom of it, but for now, I have the workaround to use the libreElec box as a proxy, so other issues have a higher priority.
