RIPE Atlas Infra IP Rages
Dear Atlas Team, I hope this message finds you well. Could you please provide the exact IP range(s) used by the RIPE Atlas infrastructure? This information is crucial for our ongoing network configuration. Thank you for your assistance. Best regards, Milad
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?
On Mon, 19 Aug 2024 at 15:00, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
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).
This doesn't cover the actual controllers. Example ctr-hel10.atlas.ripe.net that my probe uses: $ dig +short ctr-hel10.atlas.ripe.net A 95.217.207.45 $ dig +short ctr-hel10.atlas.ripe.net AAAA 2a01:4f9:4a:4a23::2 $ I'm wondering what the point is though. Outgoing ACLs/firewalling pretty much defeats the purpose of an atlas probe. Lukas
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
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
Milad Afshari wrote on 19/08/2024 14:32:
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.
Hi Milad, the RIPE NCC uses AS3333, so the ip address blocks announced on this ASN can be looked up here: https://irrexplorer.nlnog.net/asn/AS3333 These address blocks haven't changed since the Atlas project started, so they're stable in practice. But the RIPE NCC have never committed to keeping the controllers on these IPs, so it's possible they could change in future. Nick
On 8/19/24 3:50 PM, Nick Hilliard wrote:
Milad Afshari wrote on 19/08/2024 14:32:
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.
the RIPE NCC uses AS3333, so the ip address blocks announced on this ASN can be looked up here:
https://irrexplorer.nlnog.net/asn/AS3333
These address blocks haven't changed since the Atlas project started, so they're stable in practice. But the RIPE NCC have never committed to keeping the controllers on these IPs, so it's possible they could change in future.
Probe connects to controller, which aren't always within AS3333. There was similar question ~2yrs back [1], and here we can deduce that controllers are in different AS, not only within AS3333. - Daniel [1] https://www.ripe.net/ripe/mail/archives/ripe-atlas/2022-January/004900.html
Dear all, It's nice to see the users' accumulated knowledge about this :-) Indeed a significant part of the visible infrastructure (controllers) are not in our own network, and over time ("soon") I expect the on-prem amount will all but disappear. Other components (e.g. the APIs and some more that are not exposed to the world) are on-prem at the moment, and are very likely to move out as well. This is modulated by us working on implementing the best cost/service level ratio, so while it is very likely, it's not set in stone yet. Regards, Robert On Mon, Aug 19, 2024 at 5:11 PM Daniel Suchy via ripe-atlas <ripe-atlas@ripe.net> wrote:
Probe connects to controller, which aren't always within AS3333.
There was similar question ~2yrs back [1], and here we can deduce that controllers are in different AS, not only within AS3333.
- Daniel
[1] https://www.ripe.net/ripe/mail/archives/ripe-atlas/2022-January/004900.html
participants (6)
-
Daniel Suchy -
Lukas Tribus -
Milad Afshari -
Nick Hilliard -
Robert Kisteleki -
Stephane Bortzmeyer