Transport Optional Upgrade Release (TOUR) 2.4 Release Notes

What Is in This Version

You can use the ndd parameter ip_strong_es_model to enable the default gateway for a

physical IPv4 interface. The ip_strong_es_model parameter controls support for the strong

end-system model. When this parameter is enabled, packet source addresses (and therefore

interfaces on a multihomed host) affect selection of a gateway for outbound packets.

Previously, ip_strong_es_model supported two values, namely 0 and 1. These values affect

the routing decision made by a client application. If ip_strong_es_model is set to 0, the

strong end-system model is disabled.

NOTE A value of 0 for ip_strong_es_model is also the default option in TOUR 2.4

when the default gateway is disabled for a physical IPv4 interface.

If ip_strong_es_model is set to 1, the strong end-system model is enabled on the system.

Starting with TOUR 2.4, the ip_strong_es_model parameter supports another value, that is

2. If you set ip_strong_es_model to 2, the system attempts to match the best gateway

(discussed in Case 1) when multiple default gateways are set up on a single IPv4 subnet.

Following are different instances that affect the routing decision:

Case 1 If the client application is bound to the IP source address, the default gateway

chosen is the one associated to that source address.

Case 2 If the client application is bound to INADDR_ANY, the default gateway chosen is the

one associated to the source address the client application binds to.

For more information on configuring the default gateway for a physical IPv4 interface, refer to

the ndd help text.

IMPORTANT The components PPPoE/v6 and Mobile IPv6 A.01.00 are not new in TOUR 2.4

but are supported since TOUR 2.0. For more information on these components,

refer to the Transport Optional Upgrade Release (TOUR) 2.0 Release Notes at

http://www.docs.hp.com/en/netcom.html#IPv6.