Phill
Phill
> It would be very helpful if you could verify my hypothesis by modifying the service file according to #554. There's a lot of stuff in #554 but I take...
> Yes, I meant the desktop os. It has a graphical target, whether you are using it or not, that pigpiod is racing to set up internal SOC registers (my...
I think I've figured out the origin of `-l` or, more precisely, the absence of the problem caused by the *assumed* presence of that switch in the target environment ([SensorsIot/IOTstack](https://github.com/SensorsIot/IOTstack))....
Maybe just use: ``` $ docker exec mosquitto mosquitto_passwd -b /mosquitto/pwfile/pwfile someuser somepassword ``` where `/mosquitto/pwfile/pwfile` is the path associated with the `password_file` directive in your `mosquitto.conf`, as in: ```...
I have just found an excellent way to trigger this problem: * on the target host, run `$ iperf -s` * on the source host, run `$ iperf3 -c x.x.x.x`...
Yes. In my case I had been staring at "bad file descriptor" for some time thinking "but this worked a few moments ago, why won't it work now?". I kept...
What happens if you use the `-p` option to change to a non-default port? I've never seen anything like this but, then, I've never tried running iperf3 on a VM...
I know I'm probably going to *sound* a bit reactionary here but I'd like to explain my thinking behind proposing #12 as a *separate* image ("-router") rather than trying to...
> yep happy to proceed. @Paraphraser appreciate if you can give it a test as well since you are also an active user of this variant. I'd rather get your...
It makes sense and it's the kind of thing I might once have done myself in a past life with a multi-port router, upping and downing circuits for specific requirements...