<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Job,<div class=""><br class=""></div><div class="">Our ops team just enabled<span style="color: rgba(0, 0, 0, 0.85); font-family: "Helvetica Neue";" class=""> ICMP echo-reply on <a href="http://rpki.ripe.net" class="">rpki.ripe.net</a>.</span></div><div class=""><font face="Helvetica Neue" class=""><span style="caret-color: rgba(0, 0, 0, 0.85); color: rgba(0, 0, 0, 0.85);" class=""><br class=""></span></font></div><div class=""><font face="Helvetica Neue" class=""><span style="caret-color: rgba(0, 0, 0, 0.85); color: rgba(0, 0, 0, 0.85);" class="">Kind regards,</span></font></div><div class=""><font face="Helvetica Neue" class=""><span style="caret-color: rgba(0, 0, 0, 0.85); color: rgba(0, 0, 0, 0.85);" class="">Nathalie Trenaman</span></font></div><div class=""><font face="Helvetica Neue" class=""><span style="caret-color: rgba(0, 0, 0, 0.85); color: rgba(0, 0, 0, 0.85);" class="">RIPE NCC<br class=""></span></font><div><br class=""><blockquote type="cite" class=""><div class="">Op 5 mei 2021, om 12:23 heeft Job Snijders via routing-wg <<a href="mailto:routing-wg@ripe.net" class="">routing-wg@ripe.net</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi RIPE NCC, hi all,<br class=""><br class="">In today's troubleshooting adventure, an operator experienced difficulty<br class="">pinpointing where exactly a connectivity issue between them and<br class=""><a href="http://rpki.ripe.net" class="">rpki.ripe.net</a> (193.0.6.138 + 2001:67c:2e8:22::c100:68a) resided.<br class=""><br class="">It would be helpful if RIPE NCC reverted disabling responding to ICMP<br class="">echo requests originating from the Internet. Would it be possible to<br class="">adjust the firewall settings to accomodate troubleshooting and<br class="">monitoring?<br class=""><br class="">Right now connectivity testing has to be performed directly against the<br class="">rsync daemon's internet-exposed TCP port (873) - but it would be much<br class="">cheaper and faster for both the tester and the service hoster if instead<br class="">ICMP echo requests could be used as an early warning system (rather than<br class="">the rsync service itself).<br class=""><br class=""> $ ping -c 6 <a href="http://rpki.ripe.net" class="">rpki.ripe.net</a><br class=""> PING <a href="http://rpki.ripe.net" class="">rpki.ripe.net</a> (193.0.6.138): 56 data bytes<br class=""><br class=""> --- <a href="http://rpki.ripe.net" class="">rpki.ripe.net</a> ping statistics ---<br class=""> 6 packets transmitted, 0 packets received, 100.0% packet loss<br class=""><br class="">The above test result differs compared to sending echo requests to<br class=""><a href="http://molamola.ripe.net" class="">molamola.ripe.net</a> or <a href="http://manus.authdns.ripe.net" class="">manus.authdns.ripe.net</a>.<br class=""><br class="">Kind regards,<br class=""><br class="">Job<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>