Sebastien Roy wrote: > This case proposes a new "hostmodel" property for the IP module that > can have 3 settings: strong, weak and src-priority. Some sample > incantations for setting the tunable are provided in the Examples > section.
It looks like there's a fourth (reportable, not settable) value documented in the man page changes: "custom". > weak weak ES as defined in Section 3.3.4.2 of [RFC > 1122]. In particular, this is equivalent to > setting ip_strict_dst_multihoming = 0 through ndd > on Solaris 10 and earlier releases. > > src-priority Equivalent to the weak end-system model in > receive behavior, i.e., a packet will be accepted > on any interface, as long as the IP destination > of the packet is configured on one of the host's It may be necessary to document (somewhere, perhaps not completely in man pages) the complicated things that can happen when you use anything other than "weak." > interfaces. When transmitting a packet, if the > multiple routes for the IP destination in the > packet are available, the system will prefer > routes where the IP source address in the packet > is configured on the outgoing interface. If no Just for clarity: what defines the "multiple routes" case? I suspect that the answer is that we search for best match first and *then* select one route from a set of equivalent ones. If there's only one best route, then we pick that without regard to source address. In other words, if hme0 has only a default route, and hme1 has a specific subnet route, we'll send out hme1 when we match the specific subnet route destination, even if the source address is hme0's. Correct? If this is the case, then why not just make src-priority the default? It doesn't seem to have any effect on correctness from a routing point of view, and potentially affects only load-spreading in some narrow cases when not using vni interfaces. -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ opensolaris-arc mailing list [email protected]
