I have an issue with a deployed Pepwave BR1.
Essentially, our system as deployed has a Pepwave BR1 and an embedded controller. This controller has an alias set up for the Pepwave’s LAN gateway IP, and several on-board services use that alias. For example, “router” is set to “192.168.1.1”. Normally, I can access the Pepwave admin page by going to “http://router/” in a browser on the embedded controller. On this particular system, it complains that “this server could not prove that it is router, its security certificate is from captive-portal.peplink.com”. I have a copy of this set-up, with the same Pepwave firmware (8.0.2), and the same controller, and it works fine. Our application doesn’t actually use a browser, but this appears to be the root cause of why our services are failing. The date and time are correctly set on the embedded controller. Any clues appreciated!