[j-nsp] Source based routing on m160 with Junos 5.5R2.3

[Lars Higham]

In the new routing instance, use a BGP import policy which matches the
BGP routes that you want installed into that routing instance's table.
You might also want to exclude those routes in your BGP import policy
for your inet.0 main routing table.

You still need to do FBF incoming on your interfaces to direct the
packets to/from 172.16/12 (assumption) to the correct routing-instance.

Regards,
Lars

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jeroen Veen
Sent: Tuesday, August 12, 2003 8:16 PM
To: juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] Source based routing on m160 with Junos 5.5R2.3


Thanks for all the tips/links in response to my previous question!

Another question in line of the same subject:

Is there a way to send routes acquired through BGP into a specific
routing table? As in, put all the 172.16/8 routes into FBF_Routing_Table
and use this table for all interfaces that get 172.16/8 traffic so it
gets completely separate from and independant of 'normal' business.

It's at time like this you start pushing company management to invest in
an M5 for a lab :-)

Greetings,

Jeroen

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp