Cheers! Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at? THX! -Cornelius -- Cornelius Keck -----------------------------------------> ckeck@texoma.net Beware, so long as you live, of judging men by their outward appearance. Jean de La Fontaine
BTW, "not only my probe" means that I can't ping those two addresses from any system on the same network as the probe. -Cornelius On Sat, 12 May 2012 ckeck@texoma.net wrote:
Date: Sat, 12 May 2012 11:34:54 -0500 (CDT) From: ckeck@texoma.net To: ripe-atlas@ripe.net Subject: [atlas] Cannot ping 128.0.0.1, 128.0.24.1
Cheers!
Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at?
THX!
-Cornelius
-- Cornelius Keck -----------------------------------------> ckeck@texoma.net Beware, so long as you live, of judging men by their outward appearance. Jean de La Fontaine
Hi Probably problem is related with: https://labs.ripe.net/Members/emileaben/the-curious-case-of-128.0-16 On Sat, 12 May 2012, ckeck@texoma.net wrote:
Cheers!
Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at?
THX!
-Cornelius
On Sat, May 12, 2012 at 7:43 PM, Lukasz Trabinski <lukasz@wsisiz.edu.pl> wrote:
Hi
Probably problem is related with: https://labs.ripe.net/Members/emileaben/the-curious-case-of-128.0-16
http://www.ris.ripe.net/debogon/2012/05/20120511.shtml provides a list of filtering ASNs too.
On Sat, 12 May 2012, ckeck@texoma.net wrote:
Cheers!
Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at?
THX!
-Cornelius
-- - Así que este es el futuro del hombre: calentarse a los rayos del sol, bañarse en las claras corrientes de agua, y comer los frutos de la tierra olvidando todo trabajo y fatiga. - Bueno, y por qué no? "El tiempo en sus manos"
See also: http://albatross.ripe.net/128-probe-measurements/ Robert On 2012.05.12. 19:43, Lukasz Trabinski wrote:
Hi
Probably problem is related with: https://labs.ripe.net/Members/emileaben/the-curious-case-of-128.0-16
On Sat, 12 May 2012, ckeck@texoma.net wrote:
Cheers!
Looked at my stats, and it looks as if not only my probe can't ping 128.0.0.1 and 128.0.24.1. The probe is hooked up to a router on a Verizon FIOS (fiberoptic) line. To see if that's a systemic issue, I pinged the same addresses from systems at work, as well as TMobile's (U.S.) wireless broadband, and they respond just fine. Question now is, where is the problem at?
THX!
-Cornelius
participants (4)
-
ckeck＠texoma.net -
Iñigo Ortiz de Urbina -
Lukasz Trabinski -
Robert Kisteleki