Comment 25 for bug 1021471

I guess I am at the limits of my knowledge. So far it looks like ip_connect_route initially calls __ip_route_output_key to fill in source and destination address. And this seems to cause a routing cache entry to be created with source and destination address 0.
It could be wrong to cache that or to create it with 0 addresses or both... I added all that info to the upstream bug in the hope of someone there knows details...