Thursday, February 13, 2020

What implications has CGNAT had on your environment/customer base?

Hi All - I'm going to be implementing what will be a fairly large-scale CGNAT deployment for the ISP I work for. We're a fairly new org in the UK thus IPv4 address space acquisition is a big issue for us. One /18 goes currently for around $300k+. This cost isn't sustainable with the subscriber numbers we're planning for. CGNAT is a must. I've read significant documentation on the matter and know of the majority of risks and features implementing this will break - so IPv6 and the ability to assign our customers static IPv4 addresses are an essential prerequisite to the deployment. That said documentation can only get me so far - I would like to ask people here what deploying CGNAT broke within your network, and what the majority of complaints you received were? What did you learn from your deployments?

Also I'm sure someone will say - "just deploy IPv6" - we are as mentioned, but customers still need the ability to get to the v4 internet, thus either some 6to4 conversion needs to take place (which is still CGNAT as multiple customers will be shared behind a single v4 address) or we do the NAT444 scenario we're currently moving forward with (due to CPE hardware support, and because we would like customers to be able to use their own CPE device, there is no way for us to do MAP-T/MAP-E or Lw4o6 currently - same goes for 464XLAT which is really only used by mobile carriers).



No comments:

Post a Comment