1 May
2013
1 May
'13
4:59 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yes I absolutely meant 44.128.0.0/16!
These networks are already defined by the community as test networks:
192.0.2.0/24 RFC5737
198.51.100.0/24 RFC5737
203.0.113.0/24 RFC5737
For benchmarking purposes and tests you may use 198.18.0.0/15 RFC2544.
For those trying to avoid RFC1918 collisions you may look into all of
these address spaces:
100.64.0.0/10 RFC6598
169.254.0.0/16 RFC3927
192.0.2.0/24 RFC5737
198.18.0.0/15 RFC2544
198.51.100.0/24 RFC5737
203.0.113.0/24 RFC5737
RFC6598, as already stated, is probably best suited as "private"
address space between 2 colliding RFC1918 networks.
Note that Amazon uses 169.254.0.0/16 for the direct connect service.
73 de Marc, LX1DUC
On 30/04/2013 12:04, Jann Traschewski wrote:
(Please trim inclusions from previous messages)
_______________________________________________ I guess you are
talking about 44.128/16 rather than 44.161/16...
I don't agree on this. I don't want to migrate to RFC1918
addresses. I want to keep 44.128/16 for testing purpose.
73, Jann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRgOdzAAoJEHFIN1T8ZA8vJxgP+gNrUy9Immry0WJt6yrYrJq4
2MgXL+u0U0oOAcTOO4bwAiUvNZUJ7wOBf9srog6zyvhGIKF23D/VhG38FxaJHAbr
5Z3HBIvAS828+q/Gf2qzWcCN6ZGReozrg79S4ryTEc4K0FrqoI2MNihBoeg7C5T7
dkrqPEb7/7+ymM1ZX6mME3iqmkULVW3WCus9gY1SC0iG+FaBGGfT6P+jUdoS2JrF
Tleo71mNl5fxyD2ldJ179Pq724PwRhZOeeO5T6GXK/Iux3+XqP1WKeh6epGCEE9h
+8EI9eC9M2uyot9MwI+vWanLGkkugBz3Zz8icad+mgStRl6adDOvgDYKVhL0Bi0C
LVvk0NVE9AyZszj2fohLeLgTpDo1Rn1g7ZbEJwJ3xNIHwLsM3abXF/9ILsSfjF9T
SxTKxynCMboAdRjzP9rrQ+O3Pk7G3TmcLZBuW0tmwKebiD9yuI/i6C6g/lxlhjVu
+FZYxVC1fWFTsXqklaS/jRVIcdLaJgaHGuvbXC2nWPd2/iTsHJHgBvg/Mx+asGsr
Pkw/s83aVwvgcZEO/mekLtwPuFniVPG+PTAP0CBqE0HEZDuF/gqqvcqc1vnQADak
f7HK9I5PXJTmeMo8mR4n58Jt2kF6goQZxVNvsFBQYUz1RHWO78saOJS5TecSg0tZ
2HNRbYe8yg0pODE+aB0B
=ed0P
-----END PGP SIGNATURE-----