[Babel-users] ANNOUNCE: babeld-1.6.0

[Steven Barth]

I will look into migrating hnetd to use the regular babeld package next 
week but I at least need subtrees to be enabled and that patch of mine 
needs to be there. I bumped babels to one or two commits before 1.6.0 to 
Juliusz' main branch already and so far that worked out well. I will 
just have to figure out if the init-changes make a difference to me or not.


About the patch I submitted it more than a year ago already:
https://lists.alioth.debian.org/pipermail/babel-users/2014-February/001551.html
and have it in babels ever since. I can't find it right now- but if I'm 
not all too clumsy I sent a reminder about it to Matthieu and Juliusz a 
few weeks / months ago but got no reply to both mails.


Anyway the reasoning is that if you simply do a: ping6 ipv6.google.com 
on the router itself, ping6 will simply use connect() or sendto() 
without explicitly bind()ing to a source-address address thus the kernel 
tries to lookup the route with source-address ::/128 (unspecified 
address). If you only have source-restricted routes you then need to 
have a route with source ::/128 aswell otherwise ping6 will fail with 
sth. like "network is unreachable" and many programs will behave the 
same. By default babel though treats these routes as invalid (due to 
::/128) so I have to patch the filter.


Cheers,

Steven




On 18.04.2015 08:06, Gabriel Kerneis wrote:
>>>>         append_parm "$cfg" 'src_ip' 'src-ip'
>>>>         append_parm "$cfg" 'src_eq' 'src-eq'
>>>>         append_parm "$cfg" 'src_le' 'src-le'
>>>>         append_parm "$cfg" 'src_ge' 'src-ge'
>>>
>>>
>>> Ah, I had warned people on this very list about changes to filter 
>>> rules, and
>>> then I managed to miss them because they weren't in the release 
>>> notes. My
>>> mistake, will fix.
>>
>> OK. I am totally ok with, like distributing patches that people can 
>> test for
>> robustness. If you want to take that on, I will gladly test. If not, I
>> can attempt
>> to merge the rules myself.
>
> As far as I can tell, the 4 lines above are all you need (and enabling 
> ipv6-subtrees in the config file, since it's not compiled in, if you 
> want that as well).
>
> Best,