29 Jul
2021
29 Jul
'21
4:32 a.m.
On 28/7/21 10:54 pm, Antonios Chariton (daknob) via 44Net wrote:
Yes, it will be difficult, and there are some hotspots
for some people that single-handedly manage a lot of addresses, but if there’s anything we
can do, we’re happy to help.
Unfortunately, I can't see a lot of scope there,
beyond being able to
get the new address block early (which has been covered). And of
course, unlike a commercial network (who surely have the same issue
occasionally), I don't have a dedicate team of network admins to do the
legwork - that's me. ;)
Yes, indeed. We would like to see more, but we
requested “at least 5 years”. We’d like to see all future allocations based on this
scheme. Keep in mind that the current Direct BGP allocations, no matter the size, are also
time limited, in the current state of things, with no guarantee of renewal. So technically
this was also a problem before, but realistically it did not affect anyone. I think we
just have some more renumbering than usual to do now because this proposal is the largest
change to IPv4 Allocation Policy in 44/8 since the original once with the States and
Countries.
Yeah, I knew there was a limited timeframe on the "lease", but
I didn't
see any issue with that. A lot of those contracts are renewed, unless
there's compelling reasons not to.
It is configured in the iptables so it’s within the
firewall of the Linux kernel. You don’t need to install additional software. Any Linux
server or MikroTik Router (since it runs on Linux) can do it and all the traffic going
through this host (e.g. the VPS in this case) can be modified. So you can route your new
prefix, and add a rule to your firewall to check if the “Destination IP” is the new
prefix, to perform the action “netmap” (instead of “accept” or “drop” or “reject”) to the
old prefix. And similarly for outgoing traffic (if the Source is the old, “netmap” to the
new).
Well, that's not an issue then, beyond RTFM. ;)
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com