[j-nsp] Filter-based forwarding outside of inet.0?

[Clarke Morledge]

I am still trying to wrap my head around FBF, and I am stuck on how to 
achieve a Cisco-like PBR forcing a packet that matches a set of conditions 
to go to a different next-hop inside a VRF.  The problem I have is when 
the new next-hop can only be resolved within the VRF, NOT the default 
routing instance (inet.0).

Let's say I am trying to create this forwarding instance to change the 
default route:

[edit routing-instances fbf-test]
HonkinBigMx# show
instance-type forwarding;
routing-options {
     static {
         route 0.0.0.0/0 next-hop 192.168.255.1;
     }
}

I need to create a rib group where 192.168.255.1 can be resolved 
(correct?).  It can be resolved in a virtual routing instance (a VRF) 
called test.inet.0 where I need to insert via a filter the changed default 
route next-hop for PBR forwarding purposes.  THe 192.168.255.1 can not 
resolve in inet.0 because it does not live there.

If I try to create a rib group:

interface-routes {
     rib-group inet fbf-rib-test;
}
rib-groups {
     fbf-rib-test {
         import-rib [ fbf-test.inet.0 test.inet.0 ];
     }
}

The Junos compiler complains:

[edit routing-options interface-routes]
   'rib-group'
     fbf-rib-test: primary rib for instance master was not found in 
ribgroup configuration.
error: configuration check-out failed

I try to define the interface-routes at in the test.inet.0 routing 
instance stanza (which is where I think it should be defined anyway), and 
I get a similar complaint.

In reading the docs, they insist that I must import inet.0 into the rib 
group, even though the next-hop can not be found to resolve there. 
Furthermore, I can only define a rib-group in the default routing 
instance part of the config and not in the routing-instance part of the 
config.

What am I missing here and/or how can I workaround this limitation?

Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187