> For me, it always stops at 766 packets received.
>
> --- localhost ping statistics ---
> 47742 packets transmitted, 766 packets received, 98% packet loss
> round-trip min/avg/max = 0.7/227.6/422.3 ms
>
> --- localhost ping statistics ---
> 8166 packets transmitted, 766 packets received, 90% packet loss
> round-trip min/avg/max = 0.7/158.6/285.0 ms
>
> --- localhost ping statistics ---
> 56121 packets transmitted, 766 packets received, 98% packet loss
> round-trip min/avg/max = 0.7/251.0/491.2 ms
Yep, same here (2.1.122 on a single Pro200). If I interrupt early
enough in the run it shows almost exactly 50% packet loss. But
after 766 are received it seems to drop them all.
> I refuse to floodping any other site on my network because that would
> surely be considered abuse.
Well, if you only send a few hundred packets out it'll hardly kill
anything. I usually interrupt after c. 1 second. And don't do it too
often :).
On eth0 (Intel EEPro100+ but running at 10MBit for now) I can
floodping other machines on the LAN with no packet loss.
> Perhaps this is related to that "too many network errors problem" as
> ifconfig gives me this:
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:262348 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:22036952 dropped:262348 overruns:0
> carrier:0 coll:0
This is because your ifconfig is out of date (I believe this is a FAQ).
FWIW my loopback shows no errors after my floodping
experiments (rx packets== tx packets as always).
-D
-- David Mansell at home: david@manpart.co.uk http://ban.joh.cam.ac.uk/'I'd LOVE to go out with you, but I'm teaching my ferret to yodel'
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/