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] Probe connectivity status update interval
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Mon Jul 7 15:58:53 CEST 2014
On Jul 7, 2014, at 7:27 AM, Hendrik Visage <hvjunk at gmail.com> wrote: > On Mon, Jul 7, 2014 at 11:24 AM, Colin Johnston <colinj at mx5.org.uk> wrote: >> 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. > > Same for 3G networks here in ZA that issues RFC1918 IPs, so to check > the "speed"/response of your local link with the probe, necessitates a > ping to a RFC1918 IP. > > My use case was for checking a VPN link, but yes, that is a local > case, and the only real need I could come up for using my credits :) Seems like they should be numbered with IPv6 addresses instead? :) Then this could work ... or can you work around this by using a DNS name that points to 1918 IP? - Jared
- Previous message (by thread): [atlas] Fwd: monitoring RFC1918 IPs
- Next message (by thread): [atlas] Probe connectivity status update interval
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]