<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hello Nate,<div><br></div><div>Sorry to hear you’ve been having problems with the V5 probe.</div><div><br></div><div>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.</div><div><br></div><div>Can you take a good look at the OPNSense configuration to see if any v4 traffic going towards the internet is being filtered?</div><div><br></div><div>Regards,</div><div><br></div><div>Michel<br><div><br><blockquote type="cite"><div>On 28 Nov 2022, at 16:31, Nate Weibley <nweibley@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><div dir="ltr">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: <a href="https://atlas.ripe.net/probes/62490/">https://atlas.ripe.net/probes/62490/</a> <div><br></div><div>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. </div><div><br></div><div>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. </div><div><br></div><div>Are there any other troubleshooting steps I should try?</div></div>
-- <br>ripe-atlas mailing list<br>ripe-atlas@ripe.net<br>https://mailman.ripe.net/<br></div></blockquote></div><br></div></body></html>