[routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Previous message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Next message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed May 5 12:31:34 CEST 2021
Hi, On Wed, May 05, 2021 at 12:23:15PM +0200, Job Snijders via routing-wg wrote: > In today's troubleshooting adventure, an operator experienced difficulty > pinpointing where exactly a connectivity issue between them and > rpki.ripe.net (193.0.6.138 + 2001:67c:2e8:22::c100:68a) resided. > > It would be helpful if RIPE NCC reverted disabling responding to ICMP > echo requests originating from the Internet. Would it be possible to > adjust the firewall settings to accomodate troubleshooting and > monitoring? Yes, please. Breaking ICMP(v6) troubleshooting is generally not a nice approach for network-relevant services... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20210505/908e4852/attachment.sig>
- Previous message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Next message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]