Thanks for your messages. I'm exactly looking for the RIPE controller infrastructure IP addresses, explaining my use case might be a bit tough, but consider a situation where I need to provide specific routes for my probes towards the controller nodes to ensure they have stable network connectivity. Regards, Milad On Mon, Aug 19, 2024 at 4:56 PM Nick Hilliard <nick@foobar.org> wrote:
Stephane Bortzmeyer wrote on 19/08/2024 14:00:
On Mon, Aug 19, 2024 at 03:55:03PM +0330, Milad Afshari < afshar.milad89@gmail.com> wrote a message of 82 lines which said:
Could you please provide the exact IP range(s) used by the RIPE Atlas infrastructure? This information is crucial for our ongoing network configuration.
% dig +short atlas.ripe.net A 193.0.6.158
% dig +short atlas.ripe.net AAAA 2001:67c:2e8:22::c100:69e
(whois or RDAP to get the complete prefix).
Or I don't understand the question?
if it's probes and anchors, then the address blocks are 0.0.0.0/0 and ::/0. If it's the RIPE controller infrastructure, then something inside the RIPE address blocks, which are available publicly.
For the OP, the RIPE NCC hasn't committed to keeping the Atlas infrastructure tied to any particular IP address ranges. I.e. if you're planning to configure any ACLs based on these IP addresses, that may break things in future.
Nick