Re: Import directly connected routes

2017-05-10 Thread Damien Clabaut
Thank you for your answer. This is really useful and helped me solve a problem that seemed impossible in Quagga. Thanks :) On 09/05/17 08:47 AM, Ondrej Zajicek wrote: On Tue, May 09, 2017 at 08:28:26AM -0400, Damien Clabaut wrote: Hello, Thank you for your answer. Are there some

Re: Import directly connected routes

2017-05-09 Thread Ondrej Zajicek
On Tue, May 09, 2017 at 08:28:26AM -0400, Damien Clabaut wrote: > Hello, > > Thank you for your answer. > > Are there some reserved variable names in function arguments ? Yes, unfortunately each keyword is reserved and cannot be used as symbol (variable, argument, protocol, table, ... name).

Re: Import directly connected routes

2017-05-09 Thread Damien Clabaut
Hello, Thank you for your answer. Are there some reserved variable names in function arguments ? If I do (as per example in filter.conf in git repo): function onef(string s) { return 1; } I get syntax error in the first line of the function. However, function onef(string a) { return 1;

Re: Import directly connected routes

2017-05-09 Thread Ondrej Zajicek
On Mon, May 08, 2017 at 04:43:32PM -0400, Damien Clabaut wrote: > Hello again, > > Is there any way to declare a list of interfaces in a string set or > something ? No, string sets are not implemented. Although it is something that makes sense to add. You could define functions that match a set

Re: Import directly connected routes

2017-05-08 Thread Maximilian Wilhelm
Anno domini 2017 Damien Clabaut scripsit: Hi, > Is there any way to declare a list of interfaces in a string set or > something ? > > The goal would be to use it in direct protocol, and in pipe protocol (import > where ifname ~ list_if1) How 'bout managing the list of devices within the direct

Re: Import directly connected routes

2017-05-08 Thread Damien Clabaut
Hello again, Is there any way to declare a list of interfaces in a string set or something ? The goal would be to use it in direct protocol, and in pipe protocol (import where ifname ~ list_if1) Regards, On 08/05/17 03:47 PM, Ondrej Zajicek wrote: On Mon, May 08, 2017 at 03:45:17PM

Re: Import directly connected routes

2017-05-08 Thread Ondrej Zajicek
On Mon, May 08, 2017 at 03:45:17PM -0400, Damien Clabaut wrote: > Hello Ondrej, > > Thank you for your answer. > > I did not manage to do it with "device", but "direct" works: Yes, that was my mistake. 'direct' is the correct one, -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek

Re: Import directly connected routes

2017-05-08 Thread Damien Clabaut
Hello Ondrej, Thank you for your answer. I did not manage to do it with "device", but "direct" works: protocol direct direct_numa0 { table numa0; interface "eth4.800", "eth4.801"; } Thanks :) On 08/05/17 03:16 PM, Ondrej Zajicek wrote: On Mon, May 08, 2017 at 02:51:55PM -0400, Damien

Re: Import directly connected routes

2017-05-08 Thread Ondrej Zajicek
On Mon, May 08, 2017 at 02:51:55PM -0400, Damien Clabaut wrote: > Hello, > > I have an issue with latest stable Bird (1.6.3) on Debian8. > > I have a bunch of directly connected networks, with route in main routing > table: > > # ip route show > default via 10.21.136.126 dev eth0 >

Import directly connected routes

2017-05-08 Thread Damien Clabaut
Hello, I have an issue with latest stable Bird (1.6.3) on Debian8. I have a bunch of directly connected networks, with route in main routing table: # ip route show default via 10.21.136.126 dev eth0 10.21.136.0/25 dev eth0 proto kernel scope link src 10.21.136.19 192.168.1.0/31 dev