On Wed, Jun 08, 2011 at 04:58:01AM -0500, Trey Blancher wrote: > Here's the output you requested: (...)
> Looks like the ping method is broken from here. I saw that you made (...) It certainly looks like the ping mechanism doesn't work in your environment. As for the changes I introduced, none affect netselect's ICMP probes. So we can still try to find the issue debugging your current installation. Could you please try running the following in your system? (I'm assuming your system's network card is 'eth0' and that you have tcpdump installed ) ----------------------------------------------------------------------------- [ first ensure you don't have any other background process using 'jobs' ] # tcpdump -w /tmp/netselect-icmp.pcap -ni eth0 net 74.125.115.0 or icmp & # netselect -I -vv -s 1 www.google.com # kill %1 [ or use 'fg' to restore the tcpdump capture and interrupt it with Ctrl+C ] # tcpdump -w /tmp/netselect-trace.pcap -ni eth0 net 74.125.115.0 or icmp & # netselect -vv -s 1 www.google.com # kill %1 ----------------------------------------------------------------------------- And send me the /tmp/netselect-icmp.pcap and /tmp/netselect-trace.pcap files through private e-mail (do not send them to the bug report). Please try to prevent doing any network related activity while doing the packet captures (i.e. no browsing, e-mail or other stuff). Based on the packet captures I might try to determine what's wrong in your setup. Regards Javier
signature.asc
Description: Digital signature
