Jerome, thank you! I had this same issue. Adding the APN for Verizon brought up LTE on my 67C. Wrote this up for my team and added to our Jira Bitbucket. Thanks all! ... View more

So, I think I found the "why" in this problem. In the GUI, these functions are on two different pages: Addressing & VLANs and DHCP. But, in the API, these two sections are one function: updateNetworkVlan:   { "id": 99, "networkId": "xxxxxxxxxxxxx", "name": "xxxxxxxxxxxxx", "applianceIp": "10.154.99.1", "subnet": "10.154.99.0/24", "fixedIpAssignments": {}, "reservedIpRanges": [ { "start": "10.154.99.1", "end": "10.154.99.49", "comment": "Reserved Range" } ], "dnsNameservers": "x.x.x.x\nx.x.x.x.x", "dhcpHandling": "Run a DHCP server", "dhcpLeaseTime": "1 day", "dhcpBootOptionsEnabled": false, "dhcpOptions": [] }   Updating via API works as expected as I can change all of the second octets. But is there a way to change these addresses in the portal without getting an error? Thank you. ... View more

I believe I've pinpointed the concern. The APN on the MX is modifiable in the portal, but the APN on the MG requires modification at the unit itself. Even if safe mode is enabled, the APN cannot be changed from the portal.    Our activated SIMs require a custom APN. So local configuration will be required. Thank you. ... View more