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/[email protected]/
[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 ]
Lukasz Trabinski
lukasz at wsisiz.edu.pl
Sat May 12 19:43:31 CEST 2012
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 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 > >
- 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 ]