Annika Wickert

But it doesn't say that the person who runs the node did it. As they just provide an open access network. But as said, that's for a lawyer to decide.

Because that will introduce much overhead for us, on which basis should the /64 be chosen? How long does the node keep it? Our server still has the logs who...

It's also possible to just log the B.A.T.M.A.N. claimtable over time and ask for mac addresses. Those nexthops are know to us at any time, because that's how it all...

We don't but do we know who does it? No we don't. The layer2 is more risky than anything else traffic can also just be redirected through other nodes without...

But which pool? For how long do we mark /64 as stale and not usable for others? I don't see any benefit here only operational overhead, looking at Freifunk Franken...

Also we then have to do the same for IPv4, as any WebRTC call will leak all addresses ... the NAT address of the Node as well as external NAT,...

`nbthread 4` is set for this service but other services with a much higher `nbthread` setting have no issue on the same machine so there must be something specific to...

``` (gdb) t a a bt full Thread 4 (Thread 0x7fab6aed5700 (LWP 334456)): #0 0x00007fab73feb68e in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x0000555f15ff7871 in _do_poll (p=,...

What's interesting, as soon as I add `-dMtag,no-merge,integrity` the crashes seem to stop.

That makes sense, before the service was running haproxy 2.8.7 and the crash doesn't happen here. So maybe it was introduced somewhere in 2.9 or 3.0.