19 Jul
2019
19 Jul
'19
1:11 p.m.
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
- This means every single address allocated in IPv4 gets a /64 subnet
in IPv6, any /28 in IPv4 (common subnet size for hams) gets a /60
subnet, etc.
This way, standard practices for using IPv6 addresss can be used, and
the proposal of Daniel EA4GPZ can be followed to encode the callsign and
service in the lower 64 address bits as desired (for convenience only).
We would "just" have to add IPv6 addresses to all routers in our network,
but it can be done in an almost automated way because the IPv6 addresses
and subnets can be calculated from the IPv4 addresses already configured
using a simple tool.
Of course it still requires quite some work, and causes double maintenance
on things like firewalls and routing filters, so I have not done it yet.
But it sure would be possible.
Rob