19 Jul
2019
19 Jul
'19
10:28 a.m.
No.
https://portal.ampr.org/networks.php <https://portal.ampr.org/networks.php>
44.224.0.0 / 15 GERMANY
..with currently ~9500 assignments.
But that's no unresolvable problem. Just answering
here to state that there is a large allocation and we do our best to move.
There's no direct bgp announcement for 44.224/15,
and connectivity is done ampr-internal via ipip-mesh. Thus except for the dns reverse
resolution, we expect no impact and can move step by step to 44.148/15.
The sold of the /10 netblock we are in is not a
showstepper, it just makes (a lot of) work. But we also see the chance to configure things
better during the renumbering.
That was already going on for a while, wasn't it?
Of course I saw this coming, by observing changes in the network assignments...
But I wonder if the 44.224.0.0 network wouldn't have been better renumbered to
10.224.0.0, that better reflects the nature of the internet connectivity of that network
and probably would solve some problems...
You could then setup the new 44.148 space with true routing.
Rob