Static routes on (active) interfaces without IP address set

2016-06-17 Thread Alexander Demenshin
Hi, Is there any specific reason why bird (1.6.0 @linux in particular) does not process static routes like: route 10.101.0.0/24 via "eth1"; when eth1 has no assigned IP address (but is up & active)? This route is completely legal but it is invisible anywhere, simply ignored (even does

Re: New "channels" feature in future version of Bird?

2016-06-17 Thread Alex Bligh
On 17 Jun 2016, at 12:40, Jan Matejka wrote: > If one of our crazy ideas comes true, we may add Lua as a possible > language to write filters in (in several years' perspective) and maybe > also deprecate the current, then-legacy filter language in far future. FWIW I did

Re: New "channels" feature in future version of Bird?

2016-06-17 Thread raf
Le 17/06/2016 à 13:40, Jan Matejka a écrit : table it; ... } should change to something like protocol bgp { ipv4 { table t1; import ...; export ...; }; ipv6 { table t2; import ...; export ...; }; vpn4 { ... }; igp ipv4 table it4; igp ipv6 table it6; ... } Look really good and clear

Re: New "channels" feature in future version of Bird?

2016-06-17 Thread Ondrej Zajicek
On Fri, Jun 17, 2016 at 01:40:45PM +0200, Jan Matejka wrote: > Import and export filters should stay as they were before. The > "channels" feature is just an internal abstraction layer between routing > tables and protocols. Hi I would disagree a bit here. Channels are not just an internal

Re: New "channels" feature in future version of Bird?

2016-06-17 Thread Job Snijders
On Fri, Jun 17, 2016 at 01:40:45PM +0200, Jan Matejka wrote: > If one of our crazy ideas comes true, we may add Lua as a possible > language to write filters in (in several years' perspective) and maybe > also deprecate the current, then-legacy filter language in far future. YES!!! that would be

New "channels" feature in future version of Bird?

2016-06-17 Thread Baptiste Jonglez
Hi, I am very curious about the new "channels" feature from the int-new branch. I understand it is supposed to replace import and export filters by connecting protocols to routing tables. What is the motivation for this change, and how does it work from a high-level perspective? Will it be