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] Probe does not request IPv4 address via DHCP
- Previous message (by thread): [atlas] Probe does not request IPv4 address via DHCP
- Next message (by thread): [atlas] Probe does not request IPv4 address via DHCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Jun 14 09:10:34 CEST 2017
On 2017/06/13 14:07 , Stanish Stanishev wrote: > Ah, Thank you so much for the support. > May I ask you to share what did you do in order to make the probe connect again to the Atlas ? Normally the probe receives the name of a controller to connect to. If the probe doesn't have access to DNS resolvers then it cannot connect. We have a trick to provide the probe with either an IPv4 or an IPv6 literal. In theory the system will detect that the probe has troubles resolving DNS and will switch to that automatically. We have to figure out why that didn't happen for your probe. But it can also be activated manually. Philip
- Previous message (by thread): [atlas] Probe does not request IPv4 address via DHCP
- Next message (by thread): [atlas] Probe does not request IPv4 address via DHCP
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]