WAN IP Invalid after reboot

RouterOS General
1

I am using a LtAP LTE6 unit with a Re11-4G PCIe chip installed along with the native LTE6 chip. If I factory reset the device, enable the 4G chip it will connect to my B43 network once the second LTE interface is added to the WAN. The problem happens if I reboot the board. When it comes back up the configuration remains unchanged but the IP on the B43 interface (that is acquired dynamically) is now listed as invalid. The only way I have been able to restore functionality to the board for B43 internet connections is to do a factory reset.

Has anyone experienced this or a similar problem? If so, any ideas on a resolution?

Cheers

2

Upgrade ROS to latest stable.
Upgrade modem firmware to latest.

My list is like this:

  • R11e-lte6 v025 (31.03.2020)
  • R11e-lte MikroTik_CP_2.160.000_v015
  • R11e-lte-4g v9
  • R11e-lte-us v16.02.183961
  • SXT LTE 3-7 |-> chip:2.0 fw:0.1.2.4

Remember that ROS do at+reset to module with specific bands and you must wait longer to be running.

3

Thank you for posting a reply so quickly. I was already on the latest stable ROS build, but I was not on the latest modem FW. I have upgraded that via SSH from V005 to V007 which was the latest it found automatically. I am still having the invalid IP issue after a simple reboot of the board. I can’t find any configuration changes between pre and post reboot. The only thing I can find is that the IP address it is pulling via DHCP from my B43 network is now listed in red and says it is invalid. The IP doesn’t change after the reboot as my B43 network assigns IPs via IMSI number. I can see in my EPC that the IMSI is checking in and being assigned an IP and is in a good active status. My guess is there is some issue in the WAN/Gateway settings that changes after the reboot and I just can’t see it.

4

Then next step is just do logging topic=lte and watch results.
Maybe you can disable one lte interface to have more clear logs or just filter logs (new feature in new WinBox).