[Solved] Can't ping tinycorelinux.net

[jazzbiker]

Hi, Core people!

My question is not TinyCore specific, so moderators can easily delete it, and is not of big value, but smth curious for me.

Seems, that i don't understand the simplest things about network. Earlier I've used ping and traceroute commands. Not for something urgent, but simply instead of ifconfig sometimes. To see wether i'm online or not. Occasionally today i've tried to tracroute the tinycorelinux.net, and got the "stars"... Same hang-up with ping. And site become unreacheable for some amount of time. Then i can read it again, but every attempt to ping or traceroute hangs, and block the site access temporarily.
Is ping prohibited, or maybe ICMP packets are treated as the threat nowadays? Seems, that not long ago it all worked. Are there any tricks?

Those packet are lost in some black-holes on the way, because some sites are pingable for me and tracerouteable too without any anomalies.

If anybody can describe my fault, will be grateful.

Regards!

[Rich]

Hi jazzbiker
See this:
http://forum.tinycorelinux.net/index.php/topic,22433.msg140508.html#msg140508

If you want to see if a site is reachable, a  wget --spider -q URL  approach may be a better choice.

[jazzbiker]

Hi, Rich!

Thanks, will look now, but the joke is, that site is reacheable without any problem, until it is pinged. It becomes unreacheable for some time, and then become reacheable again.

EDIT: not tinycorelinux.net only, with some other sites this temporary break-down occured too.

[jazzbiker]

Ok, Rich, thanks!

Just the thing, understood, thanks a lot.

[Rich]

Hi jazzbiker

... Thanks, will look now, but the joke is, that site is reacheable without any problem, until it is pinged. It becomes unreacheable for some time, and then become reacheable again. ...

Which is why I provided a link to this reply:

The main repo blocks pings as part of the port scanning protection. It likely marked you as an intruder and blocked your connections for a minute or two.

[jazzbiker]

One more question in continuation. Is such a practice quite common? So hands must be taught not to ping everything, like a curious baby?

And traceroute ... we will miss it :-(

[Rich]

Hi jazzbiker
I don't know how common it is.

In my opinion, the best response to unwanted pings and other probes is no response. This ensures the prober gains zero
information from the probe. I would use the same approach for remote logins. If your credentials are wrong, there is no
response. Error messages such as  "Invalid name or password"  tell a hacker something is listening on that connection.

[jazzbiker]

Hi, Rich!

As my traceroute invocations are showing stars stopped on the 3rd hop, I didn't even reach tinycore site, thats my local ICMP-scared provider. But i can easily traceroute google.com, for example.

I am using standard utilities, no "ping-of-death"s, they simpy block them.

Thanks a lot!

Please, mark as solved.

[jazzbiker]

EDIT: I was wrong,

Code: [Select]

traceroute tinycorelinux.net stops at the 6th hop outside my provider's net, so, probably this is tinycorelinux.net, who bans me.
Some other situation occurs. For example

Code: [Select]

traceroute duckduckgo.com stops at the 8th hop outside my provider's net, but I am not blocked, duckduckgo.com site remains reachable.

Solved anymore, thanks.

[Rich]

Hi jazzbiker

... Please, mark as solved.

Done.