In this article, we are going to look at a topic that, in my experience, is not well known. There are IP and MAC ranges that are reserved for documentation and can't be routed. There are many use cases for these ranges.
There are several reasons why you don't want to use real or accessible host addresses. Perhaps the biggest reasons are for Security & Privacy: you want to avoid sharing sensitive information or running scripts against 'real' host addresses.
There are more, but you know where I am going with this.
Important: Just to mention it again, please do not use the following address for anything else to avoid problems.
IPv4 has the following IP address ranges:
TEST-NET-1 - 192.0.2.0/24 (192.0.2.0–192.0.2.255)
TEST-NET-2 - 198.51.100.0/24 (198.51.100.0–198.51.100.255)
TEST-NET-3 - 203.0.113.0/24 (203.0.113.0–203.0.113.255)
Referenced in the RFC5737.
For Any-Source Multicast (ASM):
MCAST-TEST-NET - 233.252.0.0/24 (233.252.0.0–233.252.0.255)
Noted, that it is part of the normal multicast space and referenced in RFC6676.
You have two ranges in IPv6:
2001:db8::2001:db8:ffff:ffff:ffff:ffff:ffff:ffff3fff::3fff:fff:ffff:ffff:ffff:ffff:ffff:ffffFor Ethernet you have the following ranges for documentation purposes:
Unicast EUI-48:
00-00-5E-00-53-00 - 00-00-5E-00-53-FF
Multicast EUI-48:
01-00-5E-90-10-00 - 01-00-5E-90-10-FF
Both ranges are referenced in RFC7042.
I have rarely used the EUI-64 format, so I will just share the RFC7042 reference link rather than plastering half the article with it.
I hope you found this article helpful and apply what you have learned at some point.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。