Hi Ondrej,

thanks for the Info!

> 'ifname' represents an interface associated with the route (i.e. one to
> which the route aims), not the iface to which the route is announced by
> RIP. When route is accepted for protocol, it is accepted for all
> interfaces of the protocol (unless split horizon applies).

yes, I saw that while debugging and that explains why the filter did not get activated.
I also checked if the 'gw' and 'from' attributes could be used in some way, but the values were empty IPs.

> If you want better control, you could configure two protocol instances,
> one for each interface. Such setup has some limitations and may require
> some tweaking, but should work.

I will try to configure it. Could you please elaborate what limitations you see in this approach ?

Thanks,
Alex


On Mon, Jul 4, 2016 at 6:00 PM, Ondrej Zajicek <santiago@crfreenet.org> wrote:
On Mon, Jul 04, 2016 at 03:49:06PM +0200, Alexander Velkov wrote:
> Hello,
>
> I would like to configure RIP with different ACLs set on different RIP
> interfaces. For this purpose I thought I could use the '*ifname*' route
> attribute in bird filters. The problem I am facing is that when I use it,
> no RIP routes are announced at all, so maybe I am using a wrong syntax.

Hi

'ifname' represents an interface associated with the route (i.e. one to
which the route aims), not the iface to which the route is announced by
RIP. When route is accepted for protocol, it is accepted for all
interfaces of the protocol (unless split horizon applies).

It would be a good idea to have separate import/export filters per
interface, but that is not supported now.

If you want better control, you could configure two protocol instances,
one for each interface. Such setup has some limitations and may require
some tweaking, but should work.

--
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."