Re: Problem booting after Yum update of FC4



Tim wrote:
someone suggested:

Try "ping google.com" for several hours, and see how many packets you
drop.


Tim:

I hope you don't mean continuously. That would constitute abuse.


James Wilkinson:

That's a fairly harsh definition of abuse you've got.

It fits mine. It's not an attack, but it is an abuse. Having a ping test for 30 sec or so probably wouldn't bother anyone, but running it "for several hours" would sure fit my definition of "abuse".



They've made the ping service available in the same way as they make the HTTP service available. Accessing Google's web pages once a second would not be OTT for a suitably busy site.


What makes you think that Google has provided you with a ping responder?

Exactly, right on the mark, correct.


[snip continuous pinging sometimes necessary]

Fair enough, but do such things with the consent of the equipment
owners.  If you're testing your equipment, do so against someone that
doesn't mind it.

Yep. Or buy your own.

This guy sounds like "it doesn't matter that I broke into the
car repair shop and used the tools there, because I put them
all back when I was through with them."

I suggest this: do you have a router? Try pinging that. I use
a router between my DSL modem and my machine. It responds to
pings. So does my DSL modem, for that matter.

$ ping dslmodem
PING dslmodem (192.168.0.1) 56(84) bytes of data.
64 bytes from dslmodem (192.168.0.1): icmp_seq=0 ttl=63 time=2.60 ms
64 bytes from dslmodem (192.168.0.1): icmp_seq=1 ttl=63 time=1.26 ms
64 bytes from dslmodem (192.168.0.1): icmp_seq=2 ttl=63 time=1.19 ms

--- dslmodem ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 1.194/1.689/2.606/0.649 ms, pipe 2

$ ping router
PING router (172.17.100.199) 56(84) bytes of data.
64 bytes from router (172.17.100.199): icmp_seq=0 ttl=127 time=0.562 ms
64 bytes from router (172.17.100.199): icmp_seq=1 ttl=127 time=0.579 ms
64 bytes from router (172.17.100.199): icmp_seq=2 ttl=127 time=0.569 ms
64 bytes from router (172.17.100.199): icmp_seq=3 ttl=127 time=0.570 ms
64 bytes from router (172.17.100.199): icmp_seq=4 ttl=127 time=0.571 ms
64 bytes from router (172.17.100.199): icmp_seq=5 ttl=127 time=0.565 ms

--- router ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 0.562/0.569/0.579/0.020 ms, pipe 2


[snip]

Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



Relevant Pages

  • Re: Nework Problems
    ... > can activate the card but cannot even ping router. ... Plz post message from your attempt to dynamic eth0 config. ...
    (linux.redhat)
  • Re: (Wireless) LAN access fine but WAN (web) access not working!
    ... > a) Able to ping router on 192.168.2.1 ... > b) Able to ping colleague's PC 192.168.2.2 ... > nameserver 192.168.168.1 ... tauno voipio iki fi ...
    (comp.os.linux.networking)
  • Can not browse and network cant see
    ... internet explorer and insert an address, ... If i ping from SBS ... to it's network card all go fine, but if i ping router from SBS or from ...
    (microsoft.public.windows.server.sbs)
  • Re: network issue
    ... > Run ipconfig /flushdns before trying to ping a new hosts file entry. ... where is dsl modem getting 192.168.1.47 from? ...
    (microsoft.public.windowsxp.network_web)
  • Re: Ping Over Office Network
    ... If I understand you correctly, you can ping your ... home PC from another PC on the internet, but not from your office PC. ... DSL modem if you were using its NAT capabilities, ... I will be surprised if you actually have no firewall protection. ...
    (microsoft.public.windowsxp.network_web)