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] Fwd: monitoring RFC1918 IPs
- Previous message (by thread): [atlas] Fwd: monitoring RFC1918 IPs
- Next message (by thread): [atlas] Fwd: monitoring RFC1918 IPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Colin Johnston
colinj at mx5.org.uk
Mon Jul 7 11:24:52 CEST 2014
It would for useful for internal network monitoring for backup lans if such networks could be monitored via probes. also satellite networks nat internally in same fashion using internal network address space. Colin On 7 Jul 2014, at 10:18, Daniel Karrenberg <daniel.karrenberg at ripe.net> wrote: > On 3.07.14 21:43 , Hendrik Visage wrote: >> Hi there, >> >> I'd like to monitor a couple of internal routes from one of my >> probes, but I get this error: >> Ping: Field 'target' : Measurement target "10.23.0.1" is invalid. >> >> Is that a limit somewhere? possible to relax that for probes >> owned/operated by me? > > > Hi Hendrik, > > [Sorry for the latish response. The office was closed for our summer > outing on Friday.] > > We do not allow this because the usefulness and semantics of such > measurements is local and we assumed that this can be done with local > resources outside of RIPE Atlas. Also we intended to prevent others > 'snooping around' in local infrastructure. > > If allowing this for the probe host themselves is something more people > want, we can certainly add it to the road-map. > > If this is a one-off, we can probably accommodate you with a "one-time > special". > > Daniel > > > >
- Previous message (by thread): [atlas] Fwd: monitoring RFC1918 IPs
- Next message (by thread): [atlas] Fwd: monitoring RFC1918 IPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]