In the past ampr gateway would only forward packets to the general internet from 44-net address space and not from 44 net to other 44 net addresses. Will the ampr gateway now forward packets for addresses from 44-net to 44.192.0.0/10?
Philip KC3IPF
In the past, amprgw would not forward packets from one tunnel-connected 44 subnet to another. It WOULD forward to/from tunnel-connected subnets to all directly connected (BGP announced) subnets, 44 or not, so it should continue to do so with 44.192.0.0/10. We'll have to try it when there's something in that space to try to connect to. - Brian
On Sun, Aug 11, 2019 at 12:10:47AM +0000, Martinez, Philip via 44Net wrote:
In the past ampr gateway would only forward packets to the general internet from 44-net address space and not from 44 net to other 44 net addresses. Will the ampr gateway now forward packets for addresses from 44-net to 44.192.0.0/10?
Philip KC3IPF _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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
On Sat, Aug 10, 2019 at 5:30 PM Brian Kantor via 44Net < 44net@mailman.ampr.org> wrote:
In the past, amprgw would not forward packets from one tunnel-connected 44 subnet to another. It WOULD forward to/from tunnel-connected subnets to all directly connected (BGP announced) subnets, 44 or not, so it should continue to do so with 44.192.0.0/10. We'll have to try it when there's something in that space to try to connect to. - Brian
On Sun, Aug 11, 2019 at 12:10:47AM +0000, Martinez, Philip via 44Net wrote:
In the past ampr gateway would only forward packets to the general
internet from 44-net address space and not from 44 net to other 44 net addresses. Will the ampr gateway now forward packets for addresses from 44-net to 44.192.0.0/10?
Philip KC3IPF _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@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
-
Brian Kantor -
K7VE - John -
Martinez, Philip -
Matt Peterson