21 Jul
2019
21 Jul
'19
8:27 a.m.
On 19/07/19 22:11, Rob Janssen wrote:
W.r.t. the issue of /64 or smaller addresses, my plan
is as follows:
- we have a /16 network within AMPRnet (44.137.0.0/16)
- it is very easy to get a /48 network in IPv6 (every home customer at
my ISP gets one of them, I have one as well. it would be easy to get
a /48 assigned to our gateway where 44.137.0.0/16 is BGP routed now
- I want to make a 1:1 mapping of every assigned address in our IPv4
subnet to a /16 network within that /48 space.
E.g. when we get 1234:5678:abcd::/48 from our ISP, I would map
44.137.0.1 to 1234:5678:abcd:0001::/64, up to 44.137.255.255 mapped
to 1234:5678:abcd:ffff::/64
I'm a bit lost at what you're suggesting, and
the practical way it would
be implemented. At first glance, this looks like a recipe for
suboptimal routing to the outside world.
I have 2 AMPRnet IPv4 allocations - one BGP connected, one IPIP
connected. Both sites have IPv6 available. Here, where the IPIP mesh
terminates has a /56. I currently have a /64 on the VPS, but as there's
only one host, it wouldn't be difficult to carve that into AMPRnet and
non AMPRnet parts, because IPs are assigned by hand and are all on the
same interface.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com