Bug#45912: Bug 45912: ping, and name resolution in general, hangs

["Kingsley G. Morse Jr." <change@nas.com>]

I fixed a similar bug after upgrading to 2.2.12. Like you, I was using a
bogus IP address internally and a real IP address for the rest of the web.

In my case, the breakthrough was using tcpdump to diagnose the problem. I
think tcpdump may well help you too. For example, you could first run
tcpdump and then ping. tcpdump should then show you the packets that ping
is sending out. 

In my case, the new routing code in the 2.2.* kernel was causing the bogus
internal IP address to leak out to the rest of the net as the source
address of my outgoing packets. Therefore, no packets came back to me! I
fixed it by removing a netmask in my net (diald) configuration, but I
suggest that you run tcpdump first to diagnose your particular problem.

Thanks,
Kingsley