A customer with T-Mobile business Internet wanted ability to do port forwarding to enable remote access to various devices and services. Regular T-Mobile business Internet uses CGNAT — Carrier Grade Network Translation — that prevents remote access to devices and prevents port forwarding from the Internet (WAN side).


The customer was advised that adding a static IP number to the T-Mobile business Internet would remove the device from CGNAT and allow port forwarding, in turn allowing for remote access to devices and services. Taking charge of the transition became a hassle because of T-Mobile. Through the process of adding the static IP number to the business Interent T-Mobile mis-configured a back-end system that caused the Inseego FX-2000 gateway to no longer work, meaning no connection could be made to the T-Mobile network. T-Mobile then decided that another Inseego gateway needed to be provided that was provisioned with the static IP number from the start. The new Inseego device was sent via next-day delivery. For the second Inseego T-Mobile gave wrong advice on how to configure the Inseego device for the static IP number. With the correct Inseego settings, the static IP number was working on a solid Internet connection. Port forwarding to devices was then implemented in the Inseego device. One of the services the customer wanted was a Wireguard VPN server set up so remote use of the static IP number could be used (for services that require the WAN IP number to be whitelisted). To create the Wireguard VPN server a special router with Wireguard VPN server was obtained and configured.