Config: briefly describes the route preference option
Forwarding Table: illustrates the preference of different routes in the IP forwarding table.
Preference/Distance/Metric: Explains terminology, and gives default distance for various route types/protocols
In order of importance
Test 1: We lack a test that verifies the preference argument to static routes.
Idea Test1: Test "floating static route" as compared to OSPF. Let the static route have "worse" distance than OSPF (110) and check that OSPF route is used when available, and the static route becomes active if there is no matching OSPF route.
Test 2: We lack(?) a test which verifies dynamic changes of DHCP vs other routes, e.g., OSPF or a floating static route.
Idea Test 12: Verify that a route retrieved via DHCP (distance 5) "loses" to a regular static route (distance 1), but "wins" over a floating static route with "distance" higher than 5.
Test 3: Test that static routes with distance 255 do not become active, even when no competing destination entry exists.
admin@infix-00-00-00:/> show routes
DESTINATION PREF NEXT-HOP PROTO UPTIME
>* 10.0.0.0/24 0/0 e1 direct 00:00:04
>* 10.0.2.0/24 50/0 10.0.0.5 static 00:00:04
10.0.3.0/24 255/0 10.0.0.6 static 00:00:04
admin@infix-00-00-00:/>
Background:
In order of importance
Test 1: We lack a test that verifies the preference argument to static routes.
Idea Test1: Test "floating static route" as compared to OSPF. Let the static route have "worse" distance than OSPF (110) and check that OSPF route is used when available, and the static route becomes active if there is no matching OSPF route.
Test 2: We lack(?) a test which verifies dynamic changes of DHCP vs other routes, e.g., OSPF or a floating static route.
Idea Test 12: Verify that a route retrieved via DHCP (distance 5) "loses" to a regular static route (distance 1), but "wins" over a floating static route with "distance" higher than 5.
Test 3: Test that static routes with distance 255 do not become active, even when no competing destination entry exists.