What do you think of providing the same data over json to make it better
parsable?
The format of the monitoring interface is well defined : it's a series of
lines of the form
keyword id key value key value ...
where each key/value is either space separated, or a string within double
quotes.
Hi Guys,
I am aware that you might already feel spammed by my mailing activity.
May I ask for the list admin to include a List-ID header in the mails of
this mailing list for easier filtering?
Also with this header, many mail clients will recognize this mail as a
mail to the mailing list whic
Christof Schulze writes:
> Hi Guys,
>
> I am aware that you might already feel spammed by my mailing activity.
> May I ask for the list admin to include a List-ID header in the mails of
> this mailing list for easier filtering?
From: Christof Schulze
To: babel-users@lists.alioth.debian.org
Mes
Juliusz Chroboczek writes:
>> 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 d
Christof Schulze writes:
> There are approaches to reduce the amount of routes per client
> including using nat66 on each node. You certainly are making it sound
> like there should be put some thought into reducing the amount of
> routes. This will be the next step after we have more than jus
Hi,
I've pushed the code to run Babel over unicast. It's in branch "unicast".
In order to use it, you need to say in your config file:
default unicast true
It's a per-interface parameter.
The code is pretty nasty, and not up-to-date with master, so I'll probably
be rebasing it some more.
> I agree that the current format is very easy to parse for a human, which
> is a benefit. I am struggling to have a machine parse this though.
You need a lexer. Here's a simple lexer for you:
https://www.irif.fr/~jch/software/babel/babel-lexer.c
-- Juliusz
__
> The main benefit of a well-known format is that the requirement for a
> client goes from easy parsing code to *no* parsing code.
Right. So either we add a dependency on JSON to babeld, or we add
a trivial parser to every program that consumes babeld's input.
> In this example, parsing the cust
8 matches
Mail list logo