Erik Nordmark wrote: > The strong end-system model (see RFC 1122) talks about restricting > things both at the receiving and sending ends, and we have some RFEs > asking for that. What this means in practice is that the source IP > address constrains the interface on which the packet can be sent out, > whether the source IP address was set by the application (doing a > bind()), or set as part of accepting a new TCP/SCTP connection.
I guess an app will get a network unreachable error if there is no route to a destination using the bound interface even when there is a route using another interface? Can an app enforce this restriction even if the system does not (ip[6]_strict_src_multihoming is not set)? Via a socket option? -- K. Poon. kacheong.poon at sun.com