Having an extremely odd issue here. I own multiple MAX Transit Minis (have used them for years so YES I know about having to turn the WAN port on) and all of a sudden the hardwired WAN line won’t show up in the WAN options - only cellular (see photo). And to make it even worse, the cell keeps spinning and waiting to Obtain IP Address. My vendor partner is West Networks and they are perplexed as well. Firmware is 8.3.0 Built 5256. I can’t check the cell firmware update because I can’t get online with the unit.
I will say this… I did just move to a new home. Last home had Spectrum internet on copper. I used my own modem there to hit my Dream Machine set up. No issues ever. The new home has ATT Fiber on a BGW320-500 modem. I have tried IP Passthrough etc with the Pepwave Mac address etc as well. No luck at all.
I have a lot of work with these starting Monday and need to get this resolved. Any help is appreciated.
Update :: I went to my warehouse and pulled out an older Max Transit Duo that we don’t use anymore. Popped some sims in, plugged it in and BOOM. Works just fine. So Max Transit Duo is good - all of my Minis (have 6 of them) - None are working. All having the same issue of not showing the hardwired WAN cable plugged in and Cell spins looking for IP.
I noticed these same issues on 8.3 RC2/3 a few months back, it took a couple of hours on the phone with the client to manually fix everything.
My temp fix - You have to physically log into to every Transit Mini with this issue, and reboot to 8.2.1 FW. Do not allow it to upgrade to 8.3, otherwise the issue will happen again.
I thought this might just be an issue I was only experiencing, as no one else has mentioned it up until this point, so I did not open a ticket at the time. Now that you are having the same issue, I would definitely recommend opening a ticket now.
Thank you - and thanks to the fine people at West Networks, we got the hardwired WAN working fine. The sim card / cellular issue is another question but might be an outdated SIM that sat for a while.
This was because of a momentary lapse in prime care coverage. When that happens, the WAN port gets disabled. WHO KNEW!