So, are you saying that by adding a default route pointing to the inet.0 table (default routing table) the return traffic is not getting routed to via inet.0 via appropriate egress interface?
Is there any another more specific route in PBR.inet.0 for the return traffic destination? Is there a route for the return traffic destination in inet.0 point to the correct egress interface? Can you post “show route a.b.c.d extensive table PBR.inet.0” and then “show route a.b.c.d extensive”? Thanks, Nilesh On 12/2/09 7:21 PM, "Chris Evans" <chrisccnpsp...@gmail.com> wrote: Just tried that, no dice.. I also tried 'master.inet.0' with no luck. If I pull the interfaces out of the global routing instance, I can successfully use a firewall filter to forward how I need it to. Unfortunately it just doens't work with interfaces are in the default instance.. Thanks Chris On Wed, Dec 2, 2009 at 10:11 PM, Nilesh Khambal <nkham...@juniper.net> wrote: On 12/2/09 7:10 PM, "Nilesh Khambal" <nkham...@juniper.net> wrote: > - set virtual-router PBR routing-options static route 0.0.0.0/0 > <http://0.0.0.0/0> next-table > inet.0 Sorry the syntax should be - set routing-instances PBR routing-options static route 0.0.0.0/0 <http://0.0.0.0/0> next-table inet.0 Thanks, Nilesh. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
