This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Cannot ping 128.0.0.1, 128.0.24.1
- Previous message (by thread): [atlas] Cannot ping 128.0.0.1, 128.0.24.1
- Next message (by thread): [atlas] Cannot ping 128.0.0.1, 128.0.24.1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iñigo Ortiz de Urbina
inigo at infornografia.net
Sat May 12 19:55:50 CEST 2012
On Sat, May 12, 2012 at 7:43 PM, Lukasz Trabinski <lukasz at 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 at 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"
- Previous message (by thread): [atlas] Cannot ping 128.0.0.1, 128.0.24.1
- Next message (by thread): [atlas] Cannot ping 128.0.0.1, 128.0.24.1
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]