Using RAdv and trigger routes with multiple interfaces

[Ondrej Zajicek]

On Fri, Nov 29, 2013 at 03:34:25PM +0100, Tore Anderson wrote:
> Hi,
> 
> On first look, it would appear that the "trigger" option is exactly what
> I need. However, I ran into the a problem - it appears to be global for
> the entire radv protocol instead of being per-interface, and that I
> cannot seem to work around limitation that by setting up multiple (one
> per interface) instances of the protocol either.
...
> Am I missing something obvious here or is the trigger feature only
> useful on routers with a single network interface?

Well, your use case wasn't the one i have in mind for 'trigger' feature.
I expected trigger to be like default route. But your use case should
work with multiple radv instances.

> ...but that only gives me a syntax error on the line marked. So I tried
> the following instead, which also resulted in a syntax error:
> 
> protocol radv vlan100 { # <-- syntax error on this line
>   interface "vlan100";
>   trigger 2001:db8:100::/64;
> }

This works for me. Perhaps you have some define for symbol vlan100,
or some other problem?

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at 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."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20131129/089254cc/attachment-0001.asc>