router : ripng : config distance
 
config distance
Use this subcommand to specify an administrative distance. When different routing protocols provide multiple routes to the same destination, the administrative distance sets the priority of those routes. The lowest administrative distance indicates the preferred route. The distance field is required. All other fields are optional.
If you specify a prefix, RIP uses the specified distance when the source IP address of a packet matches the prefix.
Variable
Description
Default
edit <distance_id>
Enter an ID number for the distance. The number must be an integer.
No default.
access-list6 <name_str>
Enter the name of an access list. The distances associated with the routes in the access list will be modified. To create an access list, see router access-list, access-list6.
Null
distance <distance_int>
Enter a number from 1 to 255, to set the administrative distance.
This field is required.
0
prefix6
<address_ipv6mask>
Optionally enter a prefix to apply the administrative distance to.
::/0
Example
This example shows how to change the administrative distance to 10 for all IP addresses that match the internal_example access-list.
config router rip
config distance
edit 1
set distance 10
set access-list internal_example
end
end
config distribute-list
Use this subcommand to filter incoming or outgoing updates using an access list or a prefix list. If you do not specify an interface, the filter will be applied to all interfaces. You must configure the access list or prefix list that you want the distribution list to use before you configure the distribution list. For more information on configuring access lists and prefix lists, see router access-list, access-list6 and router prefix-list, prefix-list6.
The direction and listname fields are required. All other fields are optional.
Variable
Description
Default
edit <distribute_list_id>
Enter an entry number for the distribution list. The number must be an integer.
No default.
direction {in | out}
Set the direction for the filter. Enter in to filter incoming packets. Enter out to filter outgoing packets.
out
interface <name_str>
Enter the name of the interface to apply this distribution list to. If you do not specify an interface, this distribution list will be used for all interfaces.
Null
listname <listname_str>
Enter the name of the access list or prefix list to use for this distribution list.
Null
status {enable | disable}
Enable or disable this distribution list.
disable
config interface
Use this subcommand to configure and enable split horizon. All fields are optional.
A split horizon occurs when a router advertises a route it learns over the same interface it learned it on. In this case the router that gave the learned route to the last router now has two entries to get to another location. However, if the primary route fails that router tries the second route to find itself as part of the route and an infinite loop is created. A poisoned split horizon will still advertise the route on the interface it received it on, but it will mark the route as unreachable. Any unreachable routes are automatically removed from the routing table. This is also called split horizon with poison reverse.
Variable
Description
Default
edit <interface_name>
Type the name of the FortiGate unit interface that is linked to the RIP network. The interface might be a virtual IPSec or GRE interface.
No default.
split-horizon {poisoned | regular}
Configure RIP to use either regular or poisoned split horizon on this interface. Choose one of:
regular — prevent RIP from sending updates for a route back out on the interface from which it received that route.
poisoned — send updates with routes learned on an interface back out the same interface but mark those routes as unreachable.
poisoned
split-horizon-status {enable | disable}
Enable or disable split horizon for this interface. Split horizon is enabled by default.
Disable split horizon only if there is no possibility of creating a counting to infinity loop when network topology changes.
enable
config neighbor
Use this subcommand to enable RIPng to send unicast routing updates to the router at the specified address. You can use the neighbor subcommand and “passive-interface <name_str>” to allow RIPng to send unicast updates to the specified neighbor while blocking broadcast updates on the specified interface. You can configure multiple neighbors.
All fields are required.
Variable
Description
Default
edit <neighbor_id>
Enter an entry number for the RIPng neighbor. The number must be an integer.
No default.
interface <name>
The interface that connects to the neighbor.
No default.
ip6 <address_ipv6>
Enter the IP address of the neighboring router to which to send unicast updates.
::
config offset-list
Use this subcommand to add the specified offset to the metric (hop count) of a route from the offset list. The access-list6, direction, and offset fields are required. All other fields are optional.
Variable
Description
Default
edit <offset_list_id>
Enter an entry number for the offset list. The number must be an integer.
No default.
access-list6 <name_str>
Enter the name of the access list to use for this offset list. The access list is used to determine which routes to add the metric to.
Null
direction {in | out}
Enter in to apply the offset to the metrics of incoming routes. Enter out to apply the offset to the metrics of outgoing routes.
out
interface <name_str>
Enter the name of the interface to match for this offset list.
Null
offset <metric_integer>
Enter the offset number to add to the metric. The metric is the hop count. The metric_integer range is from 1 to 16, with 16 being unreachable.
0
status {enable | disable}
Enable or disable this offset list.
disable
config redistribute
Use this subcommand to redistribute routes learned from OSPF, BGP, static routes, or a direct connection to the destination network.
The RIPng redistribution table contains four static entries. You cannot add entries to the table. The entries are defined as follows:
bgp — Redistribute routes learned from BGP.
connected — Redistribute routes learned from a direct connection to the destination network.
isis — Redistribute routes learned from ISIS.
ospf — Redistribute routes learned from OSPF.
static — Redistribute the static routes defined in the FortiGate unit routing table.
When you enter the subcommand, end the command with one of the four static entry names (that is, config redistribute {bgp | connected | isis | ospf | static}).
All fields are optional.
Variable
Description
Default
metric <metric_integer>
Enter the metric value to be used for the redistributed routes. The metric_integer range is from 0 to 16.
0
routemap <name_str>
Enter the name of the route map to use for the redistributed routes.
Null
status {enable | disable}
Enable or disable redistributing routes.
disable