forked from Mirror/frr
doc: Add v4-over-v6 next-hop to staticd docs
GATEWAY can now be v4 or v6 for v4 routes, for v6 routes it can only be v6 (like today). Signed-off-by: Christopher Dziomba <christopher.dziomba@telekom.de>
This commit is contained in:
parent
438360e2bd
commit
86628752a5
|
@ -46,8 +46,8 @@ a static prefix and gateway, with several possible forms.
|
||||||
NETWORK is destination prefix with a valid v4 or v6 network based upon
|
NETWORK is destination prefix with a valid v4 or v6 network based upon
|
||||||
initial form of the command.
|
initial form of the command.
|
||||||
|
|
||||||
GATEWAY is the IP address to use as next-hop for the prefix. Currently, it must match
|
GATEWAY is the IP address to use as next-hop for the prefix. Routes of type v4 can use v4 and v6 next-hops,
|
||||||
the v4 or v6 route type specified at the start of the command.
|
v6 routes only support v6 next-hops.
|
||||||
|
|
||||||
IFNAME is the name of the interface to use as next-hop. If only IFNAME is specified
|
IFNAME is the name of the interface to use as next-hop. If only IFNAME is specified
|
||||||
(without GATEWAY), a connected route will be created.
|
(without GATEWAY), a connected route will be created.
|
||||||
|
|
Loading…
Reference in a new issue