Route Object
A-37
Internal Stack Functions
-
FLG_RTE_REJECT – Entry is rejecting
When set, indicates that the route is to an invalid address. All packets des-
tined for this address are discarded with an error indication.
-
FLG_RTE_MODIFIED – Route has been auto modified
When set, indicates that the route has been modified as a result of an
ICMP redirect message. This can occur only to GATEWAY routes, and
only if ICMP modifications are enabled in the stack configuration.
-
FLG_RTE_DYNAMIC – Route has been auto created
When set, indicates that the route has been created as a result of an ICMP
redirect message. ICMP can only create GATEWAY routes, and may do so
only if ICMP modifications are enabled in the stack configuration.
-
FLG_RTE_PROXYPUB – Reply to ARP with client’s MAC address
This flag indicates that the router is a proxy publisher of another entity’s
MAC address. When set, the ARP protocol will respond to ARP requests
for the route’s IP address with the supplied static MAC address when the
host is on the same IF device as the incoming ARP request. This allows
support of hosts that do not implement ARP but are on the same physical
Ethernet network (as if this is going to happen). PROXYPUB entries are
always created with an LLA (link-layer address), and contain a static LLI
(link-layer info, i.e., ARP entry). (Note: PROXY and PROXYPUB have
nothing in common other than the word PROXY in their name.)
Note: This flag will be very rarely specified (if at all).
-
FLG_RTE_PROXY – Reply to ARP with router’s MAC address
This flag indicates that the router is acting as a proxy for this host or net-
work route. When set, the ARP protocol will respond to ARP requests for
the associated IP host or network when the network appears on a IF de-
vice which is different from that of the incoming ARP request. The MAC
address supplied in the reply is the MAC of the IF device on which the ARP
request was received. A PROXY entry has no LLI (link-layer info, i.e., ARP
entry). This technique is used to “trick” clients into sending packets to the
router when subnets are split across physical devices on a router. (Note:
PROXY and PROXYPUB have nothing in common other than the word
PROXY in their name.)
Note: This flag will be very rarely specified, and is only useful when the
stack is acting as a router. One potential use applies when the stack is act-
ing as a PPP server and a PPP client is made part of the same IP subnet as
an Ethernet based interface. Here, the stack acts as the PPP client’s proxy