We all know that user tags are imperfect and there is not a lot we can do (except pinging from time to time the hosts, like ICANN does with "Keep your social data up-to-date for your domain", with mixed success). One of the problems is that people tag correctly (I hope so) but do not always tag when it would be useful. For instance, the tag "nat" is sometimes given to probes without NAT (see for instance probes 1000929, 1005290, 1008281 or 50663) but the opposite is much more common. When requesting a measurement withOUT tag "nat", 3/4 of the selected probes have a RFC 1918 IP address (see measurement #74862711) and are certainly NATted. It seems that for many hosts, "nat" is the default.
Am 03.07.2024 um 16:13:31 Uhr schrieb Stephane Bortzmeyer:
We all know that user tags are imperfect and there is not a lot we can do (except pinging from time to time the hosts, like ICANN does with "Keep your social data up-to-date for your domain", with mixed success).
One of the problems is that people tag correctly (I hope so) but do not always tag when it would be useful. For instance, the tag "nat" is sometimes given to probes without NAT (see for instance probes 1000929, 1005290, 1008281 or 50663) but the opposite is much more common. When requesting a measurement withOUT tag "nat", 3/4 of the selected probes have a RFC 1918 IP address (see measurement #74862711) and are certainly NATted.
It seems that for many hosts, "nat" is the default.
At least for RFC1918 or ULA this could be a system tag that detects that. If no outgoing connection to the RIPE is possible via the non-global address, NAT won't be given. -- Gruß Marco Send unsolicited bulk mail to 1720016011muell@cartoonies.org
Hi Stephane, We tag these probes with system-ipv4-rfc1918 and system-ipv6-ula. You can use these tags to include or exclude them in measurements. Cheers, Johan On Wed, 3 Jul 2024 at 16:25, Marco Moock <mm@dorfdsl.de> wrote:
Am 03.07.2024 um 16:13:31 Uhr schrieb Stephane Bortzmeyer:
We all know that user tags are imperfect and there is not a lot we can do (except pinging from time to time the hosts, like ICANN does with "Keep your social data up-to-date for your domain", with mixed success).
One of the problems is that people tag correctly (I hope so) but do not always tag when it would be useful. For instance, the tag "nat" is sometimes given to probes without NAT (see for instance probes 1000929, 1005290, 1008281 or 50663) but the opposite is much more common. When requesting a measurement withOUT tag "nat", 3/4 of the selected probes have a RFC 1918 IP address (see measurement #74862711) and are certainly NATted.
It seems that for many hosts, "nat" is the default.
At least for RFC1918 or ULA this could be a system tag that detects that. If no outgoing connection to the RIPE is possible via the non-global address, NAT won't be given.
-- Gruß Marco
Send unsolicited bulk mail to 1720016011muell@cartoonies.org
-- ripe-atlas mailing list ripe-atlas@ripe.net https://lists.ripe.net/mailman/listinfo/ripe-atlas
participants (3)
-
Johan ter Beest -
Marco Moock -
Stephane Bortzmeyer