11 Aug
2019
11 Aug
'19
12:10 p.m.
44.192.0.0/10 is no longer part of the AMPRnet allocation, and should be
treated like any other part of the broader Internet. If you firewall
traffic based on 44.0.0.0/8, update those rules to apply to 44.0.0.0/9 and
44.128.0.0/10.
We really don't need to discuss or concern ourselves with the 44.192.0.0/10
space at this point. It is a done deal and as such it just becomes noise.
On Sat, Aug 10, 2019 at 7:35 PM Matt Peterson via 44Net <
44net(a)mailman.ampr.org> wrote:
A good resource for AWS reachability testing is
available at
http://ec2-reachability.amazonaws.com/ Doesn't look like any of
44.192.0.0/10 is allocated to a region or is even being announced in the
DFZ, yet.
--Matt
------------------------------
John D. Hays - K7VE
Kingston, WA
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>