Field
Description
•
? # @ 3 !"
: Route to an individual host
via a specific interface.
•
? # @ 3 1&
: Route to an individual host via
a specific gateway.
•
'1 7 @ 3 !"
(default value): Route to
a network via a specific interface.
•
'1 7 @ 3 1&
: Route to a network via a
specific gateway.
Only for interfaces that are operated in DHCP client mode:
Even if an interface is configured for DHCP client mode, routes
can still be configured for data traffic via that interface. The set-
tings received from the DHCP server are then copied, along
with those configured here, to the active routing table. This en-
ables, e. g., in the case of dynamically changing gateway ad-
dresses, particular routes to be maintained, or routes with differ-
ent metrics (i. e. of differing priority) to be specified. However, if
the DHCP server sends static routes, the settings configured
here are not copied to the routing.
•
.!3, @ 3 (), ) .?2
: The routing in-
formation is taken entirely from the DHCP server. Only ad-
vanced parameters can be additionally configured. This route
remains unchanged by other routes created for this interface
and is copied to the routing table in parallel with them.
•
? # @ 3 (), ) .?2
: The settings received
by DHCP are supplemented by routing information about a
particular host.
•
'1 7 @ 3 (), ) .?2
: The settings re-
ceived by DHCP are supplemented by routing information
about a particular network.
Note
When the DHCP lease expires or when the device is re-
started, the routes that consist from the combination of DH-
CP settings and those made here are initially deleted once
more from the active routing. If the DHCP is reconfigured
they are re-generated and re-activated.
Teldat GmbH
14 Networking
bintec Rxxx2/RTxxx2
191
