documentation - What IP addresses to use in public bug reports if the actual ones are confidential? -
i wondering best practice using ip addresses in publicly available reports, e.g. bug reports, if don't want use actual 1 privacy reasons , don't want confuse people want me.
i considered addresses test-nets, see rfc 5737:
192.0.2.0/24 - test-net-1 198.51.100.0/24 - test-net-2 203.0.113.0/24 - test-net-3
but not clear me paragraph means:
rfc 5737, section 4:
addresses within test-net-1, test-net-2, , test-net-3 blocks should not appear on public internet , used without coordination iana or internet registry [rfc2050].
does mean, 1 should use in-house documentation or no device should appear on internet claiming has 1 address test nets?
the other option use private ip addresses, e.g. 10.0.0.0/8.
anything else?
what considered best practice?
does mean, 1 should use in-house documentation or no device should appear on internet claiming has 1 address test nets?
the latter -- no device on internet should use 1 of ip addresses. documentation published internet , should use them.
i confused @ first, because thought talking rfc 1918. specifies private ip address ranges familiar with:
10.0.0.0 - 10.255.255.255 (10/8 prefix) 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
but rfc 5737 different, using ip address ranges have never heard of.
the blocks 192.0.2.0/24 (test-net-1), 198.51.100.0/24 (test-net-2), , 203.0.113.0/24 (test-net-3) provided use in documentation.
the purpose of setting aside these ip networks use in documentation, ensure documentation (such documentation showing how use nat software) never use ip address ever in use anywhere. is, not on internet , not on private networks. way, if accidentally ran 1 of example commands doing copy/paste documentation page, have no effect on real networks.
Comments
Post a Comment