I guess it is logical and I was hoping to be able to make my life easier :-).
I did my tests with & without FIB indirect-nexthops. No change in behaviour. Vladi On 2 Sep 2013, at 23:47, Daniel Roesen <[email protected]> wrote: > On Mon, Sep 02, 2013 at 11:26:46PM +0100, Vladislav A. VASILEV wrote: >> Figured it out. My intention was to filter routes by performing matches >> against each protocol next hop. However, this is not supported when the >> policy is applied under "routing-options forwarding-table export". Has >> anyone seen this documented anywhere on juniper.net? > > Isn't this kinda logical? > > You're filtering RIB-to-FIB, so protocol next-hops aren't (in > first-order approximation[1]) not in play anymore, just forwarding > next-hops. So at this point, I would expect "from next-hop" to match > forwarding next-hops, not protocol next-hops. > > Best regards, > Daniel > > [1] unsure wether/how FIB indirect-nexthops might change the picture. > > -- > CLUE-RIPE -- Jabber: [email protected] -- dr@IRCnet -- PGP: 0xA85C8AA0 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
