Participant Info

  • Areas ServedBR
  • ASNs273556

Implementation of MANRS Actions

  • Action 1: Prevent propagation of incorrect routing information We also have filters blocking DDoS amplification ports destined for our customers and Port Management rule 25 blocking outbound to the Internet with destination 25/TCP.
  • Action 2: Prevent traffic with spoofed source IP addresses We have packet filter rules on our edge: - Blocking any source IP that is not from our AS273556 with destination to the Internet. - Blocking any packet originating from the Internet from BOGON sources. - Blocking any packet originating from the Internet from my own AS273556 IPs.In addition to the filters, in our BNG we apply uRPF (Unicast Reverse Path Forwarding).
  • Action 3: Facilitate global operational communication and coordination We have NOC and Abuse contacts duly registered in PeeringDB. https://www.peeringdb.com/net/36890
  • Action 4: Facilitate validation of routing information on a global scale We have IRR with person, mntner, aut-num, as-set, route6 objects duly registered with AS-SET defined in our PeeringDB https://www.peeringdb.com/net/36890. We do not have IPv4 prefixes in our ASN. We also have RPKI configured.

Why https://manrs.org/netops/join/ Supports MANRS