Steven Honson

+1 to this feature request. As someone who has a lot of experience using `babeld` with WireGuard, with the same topology as @NickCao (multiple WireGuard interfaces, each with a single...

@MisterDA Using a network namespace for the WireGuard interfaces introduces problems of its own, in particular the fact that you then need to bind any services you want accessible to...

I suspect I'm experiencing the same problem. Like @BenGig, `inspect` returns values fine, but `run` doesn't seem to ever get any values. It doesn't seem to be a browser issue...

Made some progress, the `latest` Docker image is 2 years old, since that is when the last release of `mbmd` appears to have been cut, so predates https://github.com/volkszaehler/mbmd/pull/191. Building the...

Curious, `docker build -t volkszaehler/mbmd:devel https://github.com/volkszaehler/mbmd.git#59dcc46d62d4d0169e430223c949810112ea26f3`, which is the merge commit for https://github.com/volkszaehler/mbmd/pull/191, works fine for `FRONIUS1.240` with both `inspect` and `run`. So there seems to be a regression impacting...

I think I've narrowed it down to https://github.com/volkszaehler/mbmd/pull/265, as the immediately preceding commit of 7251dd80a3fb8cd49a3bb50c43207a03d0f7ffbd is fine, with a1401c1f7c7dab43910453c790fc9973e5274832 being the commit where the `i/o timeout` error crops up. It...

Thanks @tobima, I couldn't find any other reports of issues post this PR, so I suspect 300ms is still plenty for most TCP cases. I suspect part of the reason...