Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Juliusz Chroboczek
A new *incompatible* version of Babels is available. It is incompatible because we have changed the Source Specific Update TLV's format. Matthieu, I cannot find the Source Omitted field any longer. Did you remove it? -- Juliusz ___ Babel-users

Re: [Babel-users] Aggregating and visualising data from multiple Babel routers

2014-07-05 Thread Juliusz Chroboczek
Baptiste: http://ze.polyno.me/babel/babelcli.py Cool. python3 babelcli.py localhost:33123 other_router: 172.23.184.{1..9}: Baptiste, look into the mirror, repeat to yourself I can do it, and jump into the Javascript code. Gabriel's code is pretty clean, and you'll find yourself

Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Matthieu Boutier
Matthieu, I cannot find the Source Omitted field any longer. Did you remove it? Yes, it's not a mistake. The Idea is that you will sort your TLVs by lexicographic (dst, src) in a Babel packet. Usually, the source prefix will not begin the same than the destination prefix cached: -

Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Matthieu Boutier
Suppose my network has prefixes 2001:bad:c0ff:ee::/64 and 2001:0dd:f00d:1/64. Then I'll see: 1. 64 routes towards both prefixes, typically /128; 2. default routes from both /64. If I place the source-specific after the right /128, I can compress the source prefix. so you earn 14 bytes

Re: [Babel-users] ANNOUNCE: important babels update.

2014-07-05 Thread Juliusz Chroboczek
If I place the source-specific after the right /128, I can compress the source prefix. so you earn 14 bytes in one packet... (?) Hmm... you may have a point. Ok, I'm now convinced you're right. I haven't looked at the latest version of your code yet, but if the packet parser is not too