Pantech UML 290 drops after 48 hours
We have a 4G Pantech UML 290 via Verizon. It works great for about 48 hours, but then drops and is unable to reconnect. The only way I can get it working again is to unplug it and connect to WWAN with a Windows machine. After that, we can get another 48 hours of use from the device before we have to start again. Anybody else had this issue, or anything similar? The speeds are pretty good while it's working, but the unreliability makes it a no go.
Can you post your dmesg after this happens? I've seen some sticks that restart into "memory stick mode".
jimp Rebel Alliance Developer Netgate
I haven't heard of anyone having them disconnect in the middle of use like that and needing a trip through a windows machine.
I have heard of some people who had disconnects with certain devices after some time, but ultimately most of that turned out to be a flaky USB and/or 3G device. In one case, the person connected the 3G device into a powered hub and it behaved much better after that. In another, they ended up swapping it out for a different device from the telco.
Because our pfSense is in a basement, we had to use a USB extender. USB over ethernet, if you've ever seen it. Up front, it worked great, but I suspect this was the cause of our problems. For the same amount of $, we were able to get a 4G router from CradlePoint and that's been purring along nicely. Because it's a router, we're getting a bit of double NATing putting some unexpected IP addresses in our logs, but it's no big deal for the reliability we're seeing.
Thanks for your input!
Try getting a hold of the Pantech (UML 290) Extended AT commands document and look into setting the frequency bands properly.
In many cases these are not properly configured so when a dissociation happens it could fail over to another frequency band which might not be supported by the wireless provider.
Also look into the reset commands, they could potentially bring back the modem to the initial connection state.
You can also try getting an usb sniffer for windows and check the AT commands upon a successful connection, if you're lucky you might be able to see some useful information. (in case the connection is not done through QMI, depending on QMI support and implementation)