Logan oos Even

> How current version of n2 handle broadcasts? Broadcasts are forwarded and then distributed by the supernode; to all peers that are registered with it and to all other federated...

> Maybe we can choose some edges to relay these packages? Yes. That is exactly what supernodes do today and in the future (4.0) other peers will take over. Without...

If the supernode is aware, it certainly is possible – and actually a good idea! – to answer the "who is" or forward it to the supernode that has the...

> I am wondering is it enough that supernode can only see `This is a boardcast packet` and `This isn't a boardcast, dst addr is xxx` The supernode can see...

A few thoughts: - Where do we get the information about the other nodes from? Do we trust the supernode but for forwarding? The information deposited at the supernode would...

Here no opportunity to test in bridged scenario. But apart from cavities in `Bridging.md`, I think we can merge.

Merging in anticipation of more feedback.

I see. TF and CC20 will still be handled inside our code. So, it really seems an endianess issue here. Not sure where to start.

Might be that ARP packet do not get through. If -E, (former also -b I think...) (and perhaps -r) on all edges does not help, someone might need to extend...

That's actually one idea being discussed among the maintainers. It is expected to increase throughput on the one hand but on the other hand, we still would need some locks...