I start running into trouble with 1000+ routes using 1Mbit mcast.
Sooner if I seriously
slam the network with flent or something else that abuses mcast like mdns. YMMV.
So what is the culprit here? What would it take to add an order of
magnitude?
As for aggregation and filtering: Most of my
Hello,
when building a large mesh network, Freifunk communities use maps such that
users can find nodes in the real world.
For this there must be a daemon collecting telemetry in the network.
This daemon must know a little bit about the network topology, at least
its neighbours.
Nils and I
> Nils and I wrote such a daemon, called mmfd. It is able to forward
> multicast packets in the whole network. To learn about the topology and
> the relevant neighbours, it queries babeld: mmfd is listening via
> "monitor" on the babeld socket.
Good.
> What do you think of providing the same
Juliusz Chroboczek writes:
>> The implementation does not have all the battle-tested optimisations of
>> babeld at the protocol level.
>
> On the other hand, babeld suffers from having too many features (it
> serves among others as a platform for student projects), which implies
>
Hello,
I noticed that there's this new commit (b8fb6d896a234eaa06) which removes
explicit initialization from check_xroutes() in xroute.c.
Personally I don't think it's a great idea because the initial values of the
variables involved are going to be undefined now, which makes the code
depend on
> I noticed that there's this new commit (b8fb6d896a234eaa06) which removes
> explicit initialization from check_xroutes() in xroute.c.
Fixed, thanks.
(I don't know what I was thinking when I accepted this patch. I need a rest.)
-- Juliusz
___
I didn't mean any present incorrect behaviour, but rather a weakness which
may
(or may not) reappear at some point later and cause painful bugs (a
zeroed-out
struct stands out way more than a gibberish-filled uninitialized one).
`do_filter` is two frames deeper from that `filter_result`'s
On Fri, Mar 9, 2018, at 13:21, Stanisław Drozd wrote:
> Hello,
> I noticed that there's this new commit (b8fb6d896a234eaa06)
> which removes> explicit initialization from check_xroutes() in xroute.c.
>
> Personally I don't think it's a great idea
I noticed that too and had exactly the same
> I didn't mean any present incorrect behaviour, but rather a weakness which may
> (or may not) reappear at some point later and cause painful bugs
I'm not worried, that's the kind of issue that valgrind is good at
detecting (and I regularly run babeld through valgrind). There's plenty
of other
9 matches
Mail list logo