Logan oos Even

The current n2n protocol actually uses also the forwarded data packets for hole punching, just dropping them unfortunately is no solution.

I am sorry that no one has been able to help with `buildroot` so far. Have you succeeded meanwhile? I just want to say thank you for your hint to...

We have just kind of [dropped Windows XP support](https://github.com/ntop/n2n/pull/717#issuecomment-877683968) due to the lack of required network functionality. We might pick it up again if we find ways to work around...

Thank you for bringing it up as separate issue helping us to better keep track of it. I have had a first look into the code when we discussed this...

In addition to or instead of binding edges to one IP address, you can try the freshly fixed `-DSKIP_MULTICAST_PEERS_DISCOVERY` [macro / compile time option](https://github.com/ntop/n2n/blob/dev/doc/Building.md#disable-multicast-local-peer-detection) to disable multicast peer detection. You...

> This form is not elegant enough. Well, it's what we have had up to now, just fixed the macro use. You probably prefer a command line option?

This definitely is not the final state, just a real quick fix to get an edge without multicast. peer detetction. `-E` and the SKIP_MULTICAST_PEERS_DISCOVERY macro aim at different levels (overlay...

> There are too many options in n2n, and it seems too complicated, add a great cognitive burden to users. I fully agree. A lot of them are expert settings....

Please note that #772 merges `-b` into `-p`.

I have observed the extra thread (Windows only!) not immediately reacting, i.e. it took some seconds to terminate the edge after CTRL + C, but so far, I have never...