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/address-policy-wg@ripe.net/
[address-policy-wg] IXP peering lan reachability
- Previous message (by thread): [address-policy-wg] IXP peering lan reachability
- Next message (by thread): [address-policy-wg] IXP peering lan reachability
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Tue Oct 24 12:34:29 CEST 2017
Hi, On Tue, Oct 24, 2017 at 10:41:49AM +0100, Nick Hilliard wrote: > As regards using this as a metric for determining whether an ixp address > assignment is being used for legitimate purposes, I'd suggest that this > is of only marginal use at best. By all means run a port scan to see if > there is any obvious mis-use (e.g. services listening on www/smtp/etc), > but the presence or absence of the route in the dfz doesn't mean > anything one way or another. The *absence* of the route is a very strong indicator that no other services than directly peering-related are sitting on that network, no? Gert -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard 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: </ripe/mail/archives/address-policy-wg/attachments/20171024/8d6d61a3/attachment.sig>
- Previous message (by thread): [address-policy-wg] IXP peering lan reachability
- Next message (by thread): [address-policy-wg] IXP peering lan reachability
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]