The terminologies Martians and bogons apply to certain IP addresses that should not be public. Martians refer to private and reserved addresses as defined by RFCs, while bogons are the prefixes unallocated to any regional Internet registry (RIR) by the Internet Assigned Numbers Authority (IANA).
Comprehensive Bogons
These include traditional bogon prefixes as well as the IP space assigned to the RIRs but not yet allocated by them to Local Internet Registries (LIRs) for both IPv4 and IPv6.
IPv4 Martians
Below are the known IPv4 Martians:
0.0.0.0/8
# RFC 791 & RFC 112210.0.0.0/8
# RFC 1918 Private-Use100.64.0.0/10
# RFC 6598 Shared Ad. Space127.0.0.0/8
# RFC 1122 Loopback169.254.0.0/16
# RFC 3927 Link Local172.16.0.0/12
# RFC 1918 Private-Use192.0.2.0/24
# RFC 5737 (TEST-NET-1)192.88.99.0/24
# RFC 7526192.168.0.0/16
# RFC 1918 Private-Use198.18.0.0/15
# RFC 2544 Benchmarking198.51.100.0/24
# RFC 5737 (TEST-NET-2)203.0.113.0/24
# RFC 5737 (TEST-NET-3)240.0.0.0/4
# RFC 1112 Reserved References: [NLNOG, IANA_v4]
IPv6 Martians
Here are the established IPv6 Martians:
::/8
# RFC 3513 and RFC 42910100::/64
# RFC 6666 Discard-Only2001:2::/48
# RFC 5180 BMWG2001:10::/28
# RFC 4843 ORCHID2001:db8::/32
# RFC 3849 documentation2002::/16
# RFC 7526 6to4 anycast relayffe::/16
# RFC 3701 old 6bonefc00::/7
# RFC 4193 unique local unicastfe80::/10
# RFC 4291 link local unicastfec0::/10
# RFC 3879 old site local unicastff00::/8
# RFC 4291 multicast References: [NLNOG, IANA_v6]
Bogon Autonomous System Numbers (ASNs)
An ASN is considered as a bogon under the following circumstances:
- It is reserved for special use by an RFC.
- It does not fall under the block assigned to an RIR by IANA.
- It is unassigned to an LIR by any RIR.
Reserved & Unassigned ASNs
These are the known reserved and unassigned ASNs:
0
# RFC 760723456
# RFC 6793 AS_TRANS64496 - 65551
# RFCs 6996, 7300 & 539865552 - 131071
# IANA reserved ASNs213404 - 262143
# Unallocated273821 - 327679
# Unallocated329728 - 393215
#Unallocated151866 - 196607
#Unallocated401309 - 4199999999
#Unallocated4200000000 - 4294967294
# RFC 69964294967295
# RFC 7300 Last 32 bit ASN
The Importance of Understanding Bogons
Bogons often originate from configuration errors, and are associated with different types of misconduct.
Misconduct Involving Bogons
These include:
- Source addresses of DDoS attacks
- BGP security incidents such as hijacks and route leaks
- Other nefarious Internet activities
Final Remarks
The comprehension of Martians and bogons is critical for anyone working with IP addresses. This knowledge helps in identifying potential misuse and thus, protecting your network from harmful actions.