On 8/16/13 14:15, "Andrew Deason" <[email protected]> wrote:
>In fact, the code used to only apply this restriction in one direction, >and the code to do that is commented out right now, not entirely >deleted. This was removed and now applies in both directions as of >commit b4566d725e1aa4f57d1e6db5821c590a4b6da7c0 from 2004. I'm not sure >exactly what issue that commit message is referring to, but maybe some >multihomed clients can e.g. alternate IPs for the 'from' address on >outgoing packets. Maybe someone else can justify that better. FWIW, Linux follows "interesting" rules when picking an IP for an outgoing UDP packet when multiple interfaces/addresses are believed by it to be on the same network segment. (TCP doesn't have the same issue, since a connection has consistent addresses that can be referenced — but UDP of course has no notion of connections.) -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad
