This tests the "next hop" function of the IDRP implementation. One of the machines is set up to simulate a route server, and the others peer only to that machine. "route_server" is set on for routes on all machines. The next hop should be the machine a route originates from, not the route server. In this implementation, the route server will also install routes.
local-node {
route-server yes;
local-info {
route-server yes;
}
ext-info {
route-server no;
}
}
import proto idrp rdi rdi1
idrp-ps-policy-atts {
route-server yes;
}
{
policy;
}
Policy is
Test 0 : no routes
Test 1: route set 1 - local
route set 2 - ext info set
Test 3: route set 2 deleted
route set 3 (routes in route set 1 with
exterior flag)
Test 4: route set 2 added
Test 5: route set 2 & 3 delete
For this test, we will set up a totally internal environment. The import policy should be set on the local as.
- the "route server" on routes will propogate, but with next hop of other machine. Without route-server the routes will still propagate. (no policy on internal routes) - each node will install its own static routes, and those from the "route server." This behavior will occur whether or not the route server option is turned on, because route server functions only with external RDIs.
For this test, we will set up a totally external environment on the same ethernet.
peer1 peer2 peer3 peer4 peer5 peer6 rdi1 rdi2 rdi3 rdi4 rdi5 rdi6 | | | | | | ========================================= Chain connection peer1 <->peer 2 <-> peer 3 <-> peer 4 <--> peer 5 <--> peer 6
All peers have the route-server set, but only on some routes. All routes with the route-server should have next hop from the original peer1. all other routes won't propagate. Set the gw to a unqiue gateway for each peer.
For this test, we will set up a combination of internal and external ethernet.
peer1 peer2 peer3 peer4 peer5 peer6 rdi1 rdi1 rdi2 rdi2 rdi3 rdi3 | | | | | | ========================================= peer1 <->peer 2 <-> peer 3 <-> peer 4 <--> peer 5 <--> peer 6
All peers have the route-server set, but only on some routes. All routes with the route-server should have next hop from the original peer1. all other routes won't propagate. Set the gw to a unqiue