I have an LHGG (Router OS 6x) which never fails to receive a WAN LTE IP from EE or Lyca (same provider) , however my LHGs (Router OS 7.x) (several of them) connect to the same mast/cell and once a SIM is swapped from Lyca to EE and appropriate APN changed (not using Quick Set) all fail to receive an LTE IP, even a reset to defaults fails to resolve.
I’m wondering if I’m triggering some type of data protection mechanism (suspicious activity) at EE, ie swapping sims/APNs quickly on the same IMEI, I’m struggling to think of any other reasons. I’ve triple checked the APNs and the SIM is an EE unlimited data so shouldn’t ‘run out’.
Then, (nuub should FTFM), realised one should update RouterBOARD/BOOT firmware to match RouterOS version
Also noted many fixes in v7.12 including some changes around APN management. Lyca sim fine, will change to EE sim in an attempt to repeat missing LTE IP , will report back.
Be curious if the RouterBOOT firmware fixes. Generally that helps when the modem isn’t found, not if it’s just not working with a carrier/SIM. Now just seems like a good idea for RouterBOOT and RouterOS to match, historically, that seems to fix some LTE modem issues.
You can set the auto-update checkbox in /system/routerboard so you avoid forgetting.
Spotted the RoyterBOARD auto update, but wouldn’t that lift the firmware revision ahead of RouterOS, is that an acceptable config and good practice? I’ve seen others enable thi,s but am unsure.
RouterOS or RouterBOARD updates did not resolve this, it was a PICNIC error (Problem In Chair Not in Computer).
It transpires after quite a few hours digging deep, that Lyca is happy with the APN IP Type being set to Auto, BUT EE is most certainly not. Changing the IP Type to IPv4 for all APNs resolved this, however I had spotted this setting quite some time ago and changed it to IPv4, but back again after it failed to correct the issue.
If only I knew the LTE needed an ‘AT + Reset’ command ie ‘resetting’ (can be forced by a manual band change), after an APN setting change to setup a completely new channel and correct the IP issue.
BOOM.
Chuffed to find root cause, even if it was a boo-boo!
