[atlas] New V5 Probe with IPv4 Discovery issues

Hello Nate,

Sorry to hear you’ve been having problems with the V5 probe.

It seems that your probe is not able to contact the IP echo service at ip-echo.ripe.net to derive its IP address. Because of this, IPv4 is presumed to be non-functional and the probe will not execute IPv4 measurements.

Can you take a good look at the OPNSense configuration to see if any v4 traffic going towards the internet is being filtered?

Regards,

Michel

> On 28 Nov 2022, at 16:31, Nate Weibley <nweibley at gmail.com> wrote:
> 
> I received a shiny new V5 probe via post on Saturday and got it up and running yesterday on my dual-stack network.  The probe in question is: https://atlas.ripe.net/probes/62490/ 
> 
> It has been operational for about 18 hours and quickly indicated that IPv6 connectivity was functional, but it has only momentarily indicated IPv4 connectivity was established. I can see IPv4 ICMP and UDP traffic originating from the probe passing through my opnsense router on the IPv4 WAN interface so I know IPv4 traffic is flowing. I also see the correct IPv4 DHCP lease info for my LAN on the probe's network status page. 
> 
> Probe address discovery does not show a valid IPv4 connection address or IP Echo Service listed, only the Local IP of my probe. I've tried power cycling the probe but it doesn't seem to impact this issue. 
> 
> Are there any other troubleshooting steps I should try?
> -- 
> ripe-atlas mailing list
> ripe-atlas at ripe.net
> https://mailman.ripe.net/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20221130/36c9eae4/attachment.html>